-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[Maven 4] Get rid of ${maven.multiModuleProjectDirectory}
#42430
Comments
/cc @quarkusio/devtools (maven) |
this just affects quarkus own build, right ? as this would mean mvn as found on rhel/ubi 8 wouldn't be able to build I reckon. |
Yes. |
Actually, the situation is a bit more complex than that, I should have read the fine prints of the 3.9.2 release notes. While these properties are available across the board in Maven 4, in Maven 3.9, they are restricted to the Maven config, they are not usable in a POM file:
We will have to wait for Maven 4 before cleaning this up. |
${maven.multiModuleProjectDirectory}
${maven.multiModuleProjectDirectory}
Yes, this is why we went with the hack in the current solution, and not simply doing the "replace all" |
This was apparently an internal property and it got removed from mvnd.
We put a hack in place here: #41648 but we should get rid of it and use
${session.rootDirectory}
instead.This property was introduced in https://issues.apache.org/jira/browse/MNG-7038 and has been backported to 3.9.2: https://maven.apache.org/docs/3.9.2/release-notes.html .
The text was updated successfully, but these errors were encountered: