| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The root project (worktree) must have a valid package.json,
.yarnrc.yaml, and have the gradle precompiled script plugin
refinery-frontend-worktree applied to it.
All frontend modules (workspaces) must have a valid package.json, be
referenced in the worktree project.json, and be a valid gradle
subproject with the gradle precompiled script plugin
refinery-frontend-workspace applied to it.
To reduce unnecessary downloads, we do the following workarounds:
* The node version is pinned in gradle.properties and the installed node
version is stored in .node/frontend.properties. A new node version is
only downloaded if it differs from the installed one (or none is
installed). This improves on the default gradle behavior, which would
download a new node version if the classpath of the installNode task
was changed.
* The yarn classic version is pinned in gradle.properties and the
installed yarn classic version is stored in .node/frontend.properties.
This improves on the default gradle behavior, which would reinstall
the yarn npm package at every build.
* We disable the enableYarnBerry task, since a yarn berry version is
already committed into the repository at .yarn/versions as it is
recommended in http://yarnpkg.com/getting-started/qa/
* We use yarn set version --only-if-needed in the installYarn task.
* The installFrontend task takes package.json and yarn.lock as inputs
and produces .pnp.cjs and .pnp.loader.mjs as outputs. Whether this
task is up-to-date can be checked by gradle quickly, since it doesn't
have to traverse the node_module folder due to pnp resoltion:
https://yarnpkg.com/features/pnp/
All workspaces have the installNode, installYarnGlobally, installYarn
and installFrontend tasks disabled. However, these tasks depend on the
task with the same name in the worktree project, so installation is
still triggered globally. Moreover, the installFrontend task in the
worktree has the package.json of the workspaces as inputs, so
reinstallation is triggered when the workspace package.json changes.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Script plugins allow applying other plugins from plugins { } blocks,
which simplifies the build script.
|
|
|
|
|
|
|
|
|
|
|
| |
Gradle version catalogs allow centralized management of dependency
artifact coordinates using a toml file.
Previously, we use the gradle.properties file, which cannot manage group
and name coordinates, only versions.
Node and yarn versions still have to be in gradle.properties, because
they do not correspond to any coordiates of a maven artifact.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Xtext fails to serialize non-transient references that have no
corresponding assignment in the grammar. Therefore, we mark
* Problem.nodes
* ClassDeclaration.newNode
* ExistentialQualifier.implicitVariables
* VariableOrNodeArgument.singletonVariable
as transient.
This will allow serializing Problem instances using the textual concrete
syntax for display.
|
|
|
|
| |
Suggestion by @vincemolnar to match SysML V2 terminology more closely.
|
|
|
|
|
|
|
| |
Content assist proposals should not display the object that is only
added to the model because the current context assist input refers to
it (e.g., an implicit node or variable that is only referenced in the
currently edited context).
|
| |
|
|
|
|
| |
Xtext and Class diagram extended.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If the project does not have the Xtext nature, the Problem.xtext file
will not be able to load problem.ecore
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
They can be re-generated by the BuildShip plugin anyways.
|
|
|