Extend export tests

[dslmeinte]

Also: reorganize the directory structure a little bit for clarity, and add documentation.

[dslmeinte]

Also: I think it'd be good to implement Gradle builds of the test projects, if only to show how that's done (in the same way as for T.).

[github-actions]

Test Results

0 tests   - 804   0 ✅  - 804   0s ⏱️ -11s
0 suites  -   1   0 💤 ±  0 
0 files    -   1   0 ❌ ±  0 

Results for commit 230ef54. ± Comparison against base commit c56025e.

♻️ This comment has been updated with latest results.

[dslmeinte]

Also also: we should be able to switch on this one now: /~https://github.com/LionWeb-io/lionweb-mps/blob/meinte/extend-export-tests-2021.1/.github/workflows/build.yml#L42

(Addendum:) It does mean we have to point (from gradle.properties etc.) to published versions of the LionWeb MPS plugin, not 0.2.9-SNAPSHOT. It also means we first have to publish newer versions with the fixes you did, so maybe we only switch the build on after we've done that?

[enikao]

Also: I think it'd be good to implement Gradle builds of the test projects, if only to show how that's done (in the same way as for T.).

We'd need to figure out how to run them as tests. But maybe in a first step it would be sufficient to just run them, and fail the build if they fail.

[enikao]

Do these work (on unix machines)? I think I never tried ...

[dslmeinte]

They do run. In CI not to completion, though — see /~https://github.com/LionWeb-io/lionweb-mps/actions/runs/11139777271/job/30957126805?pr=106 —, but that's another problem. (Locally, they run — at least, for me.)

[enikao]

It also means we first have to publish newer versions with the fixes you did, so maybe we only switch the build on after we've done that?

Ideally, we would run them always with SNAPSHOT, so we check changes don't break anything. Maybe we can first run publishToMavenLocal within the same container?

[dslmeinte]

Ideally, we would run them always with SNAPSHOT, so we check changes don't break anything. Maybe we can first run publishToMavenLocal within the same container?

True, and it seems we can: gradle/gradle#13337

It stands to reason that ./gradlew publishToMavenLocal just publishes to ~/.m2/ on the virtual CI machine, after which the published package should be available. (It's also not the reason that running those tasks is currently failing in their GitHub Action.)

[dslmeinte]

I guess this should also be fixed.