You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fetch old repository into temporary branch (without tags, --no-tags).
Merge temporary branch into integration branch (with history, --allow-unrelated-histories).
Combine common files (README.md, build.gradle, etc.), preserve current subprojects (metafix*) and namespace (org.metafacture.metafix).
Integrate into metafacture-runner.
Verify working state (esp. w.r.t. dependencies) for both old and new subprojects (unit tests, integration tests, distribution; branch: 577-merge-metafacture-fix).
Enforce Javadoc comments for methods (MissingJavadocMethod). 2f57d06
Find a way to run metafix integration tests only when necessary (would otherwise slow down all workflows, including pull request checks). This doesn't seem feasible; it's impossible to determine an integration test's up-to-dateness. Instead, they have been changed to run directly from the distribution instead of via Gradle (2661ab8), which reduces the test runtime by about 40-50 %, GitHub Actions runtime by about 30 %. Another option would be to let them run in parallel; but this would be considerably more complicated.
Merge metafacture-fix repository to ease maintenance and support burden as well as simplify development and use. See metafacture/metafacture-fix#298 for previous discussion.
Preconditions:
Course of action:
--no-tags).--allow-unrelated-histories).README.md,build.gradle, etc.), preserve current subprojects (metafix*) and namespace (org.metafacture.metafix).metafacture-runner.577-merge-metafacture-fix).Post-migration steps:
org.metafacture.metafixpackage versions in new repository.577-merge-metafacture-fix-rc1-SNAPSHOT).README.mdand description to point to new repository. metafacture/metafacture-fix@6fa7faaCleanup:
metafix-runner(already done during merge)..gitignorefile (remove obsolete patterns, structure metafacture-fix patterns). 402ee3ctoolVersion). a6b3d14checkstyleTest.enabled). 01a7351StaticVariableName). 1a5e003MissingJavadocMethod). 2f57d06Find a way to runThis doesn't seem feasible; it's impossible to determine an integration test's up-to-dateness. Instead, they have been changed to run directly from the distribution instead of via Gradle (2661ab8), which reduces the test runtime by about 40-50 %, GitHub Actions runtime by about 30 %. Another option would be to let them run in parallel; but this would be considerably more complicated.metafixintegration tests only when necessary (would otherwise slow down all workflows, including pull request checks).