-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
accidental variable replacements in maven filtering #128
Comments
IMHO the safest way to fix this is to change the delimiter for the filtering and replace the variable syntax in those places where the filtering (replacement of variables) is actually intendet and desired.
Therefore the configurator JAR can still be resolved from here: This will stop working after the fix... |
Maybe we can even add a wildcard for the java version instead of the exact number. |
BTW: Same error here: |
Fixed with PR #129 |
In devon-ide we are using maven filtering to replace variables for the release-process within our scripts. However as we are using the default delimiters we also replace variables like
${project.version}
accidentally resulting in this script line:https://github.com/devonfw/devon-ide/blob/5d4f2cd0d540a63339520fce4c2c8873026cfb12/scripts/src/main/resources/scripts/command/mvn#L47
being replaced as following in our (beta) releases:
The text was updated successfully, but these errors were encountered: