added backward compatibility mode if the new relocatedClasses parameter is missing #2609
+13
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a project depends on the Rascal project version with the new packager, which copies to a fresh folder instead of rewriting in-place in target/classes, and does not depend on rascal-maven-plugin which provides the fresh folder parameter
relocatedClasses, then the maven plugin fails with a stack trace.This fix runs the old in-place tpl rewriting in target/classes such that projects that do have the new rascal but not yet the new maven plugin, just keep working. Idea by @DavyLandman
Eventually switching to the new maven plugin has major benefits for the quality of the error messages in the IDE after you've types
mvn installormvn packageonce.