| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
* New default file extension: .refinery (.problem is also supported).
* Add module keyword for self-contained modules.
* Rename indiv declarations to atom declaration.
* Add node and multi declarations for explicitly declared nodes and
multi-objects, respectively.
|
|
|
|
|
| |
We use a palette-based coloring strategy, where each class and enum gets a color
from
|
| |
|
|
|
|
|
| |
Also moves model metadata into language-web, since we only use it on the
frontent.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Model generation only has to extract the candidate interpretaion, partial
intepretation queries are only needed if they appear in a rule, constraint, or
objective.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Prefix each variable with REFINERY_
* If not public host is specified, allow all origings and compute the WebSocket
address on the client from the origin.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also makes model seeds cancellable to reduce server load during semantic
analysis.
|
|
|
|
| |
Reduce server load by introducing a timeout for semantics analysis.
|
|
|
|
| |
Avoid creating interpretations not needed for the graph analysis task.
|
| |
|
|
|
|
|
| |
A new object should not be an instance of any subclasses.
Also, it should be possible cleare a node without any other type.
|
| |
|
|
|
|
|
| |
Improper equality implementation of representative election literals merged weak
and strong connected components during query canonicalization.
|
| |
|
| |
|
|
|
|
|
|
| |
* Avoid writing generated source files directly into sibling projects.
* Full project isolation cannot be enabled yet, because the frontend plugin
still requires cross-projects task dependencies for Node.js installation.
|
|
|
|
|
| |
Also increases timeout in WebSocket integration test to avoid failures due to
increased CPU usage during build.
|
|
|
|
|
|
|
|
|
|
|
| |
Java 19 is out of support, but Gradle current does not run on Java 20:
https://github.com/gradle/gradle/issues/23488
To avoid the complexity of running the build tool on a different JDK than the
application, we temporarily remove code that depends on experimental Java 19 or
Java 20 features.
Revert once the build can run on Java 20.
|
|
|
|
|
|
|
|
|
|
|
| |
Java 19 is out of support, but Gradle current does not run on Java 20:
https://github.com/gradle/gradle/issues/23488
To avoid the complexity of running the build tool on a different JDK than the
application, we temporarily remove code that depends on experimental Java 19 or
Java 20 features.
Revert once the build can run on Java 20.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
Also take advantage of precompiled Kotlin scripts to write build scripts in a
more straightforward manner through generated accessors.
Might increase memory usage of Gradle.
|
| |
|
| |
|
|
|
|
|
|
| |
Make sure we get slf4j in every test source set and every application by
default. Saves configuration effort when creating a new library that tests
VIATRA or other dependencies that require log4j.
|
|
|
|
|
|
|
| |
Improves IDE support build scripts in IntelliJ.
There is no Eclipse IDE support, but Eclipse didn't have support for Groovy
either, so there is no degradation of functionality.
|
|
|
|
|
| |
Also refactor virtual thread ExecutorService handling and integration
tests.
|
|
|
|
| |
Also test with virtual threads in we are using them in production.
|
| |
|
|
|
|
|
| |
Use Java 19 and Jetty 12 to take advantage of Project Loom preview
features to reduce CPU usage due to XtextWebDocumentAccess thread pools.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
To point the frontend to a backend server, update the config.json
file in the website root.
The config.json is generated automatically in debug mode and when
running from a standalone jar.
|
| |
|
| |
|
| |
|
|
|
|
| |
Also overhaulds the building and linting for frontend assets.
|