| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also bumps other dependencies.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Rename VIATRA subprojects to Refinery Interpreter to avoid interfering with
Eclipse Foundation trademarks.
Uses refering to a specific (historical) version of VIATRA were kept to avoid
ambiguity.
|
| | |
|
| | |
|
| |
|
|
|
| |
Also increases timeout in WebSocket integration test to avoid failures due to
increased CPU usage during build.
|
| | |
|
| |
|
|
| |
Also make sure Sonar can process TypeScript files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make sure we obey the REUSE (https://reuse.software) specification and the
origin, copyright owner, and license of all files are clearly marked.
The whole project is under the EPL-2.0, except for trivial files where copyright
is not applicable that are marked with the CC0-1.0 license. Moreover, code
included from third parties is also available under the respective license.
chore: add CONTRIBUTORS.md
List all authors and supporting organizations in accordance with the REUSE
specification.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Support for typescript@4.9.4 available in yarn 4.0.0-rc.33 according to
https://github.com/yarnpkg/berry/pull/5127#issuecomment-1345664949
Also updates other frontend dependencies.
|
| | |
|
| |
|
|
|
|
|
|
| |
Use a HMR acceptor as in
https://github.com/vitejs/vite/issues/10227#issuecomment-1256969751
Also updates frontend tooling to the latest version
(yarn now support typescript 4.8.4)
|
| | |
|
| | |
|
| |
|
|
| |
See https://github.com/gradle/gradle/issues/898
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also requires yarn 3.2.0-rc.5 due to
https://github.com/yarnpkg/berry/issues/3722
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Also upgrades various frontend dependencies.
We can't upgrade to typescript 4.5 yet, because
https://github.com/yarnpkg/berry/pull/3760 is not released yet.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Requred vendoring org.eclipse.xtext.web.servlet as
tools.refinery.language.web.xtext due to the javax -> jakarta package
name change:
https://www.eclipse.org/lists/jetty-announce/msg00149.html
|
| |
|
|
|
| |
Xtext 2.26.0.M2 might finally have Java 17 support:
https://github.com/eclipse/xtext/issues/1982#issuecomment-931958311
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
Kristóf Marussy
Kristóf Marussy