-
Notifications
You must be signed in to change notification settings - Fork 997
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
[pom] Replaces the maven property with project property. #3919
[pom] Replaces the maven property with project property. #3919
Conversation
c03b607
to
6ca2a27
Compare
The reason why introduce A better way is to replace it with |
In this scenario, we should recommend using |
Agree, #3063 is just added for users who don't know how to use it (see my comment in it). Actually it can be reverted. |
Can you give more details, is maven 3.3.1- or a very high version? |
My case is maven 3.2.5, this forced me to modify my pom. |
I think production stability is more important than this feature #3063, because production failure has already happened to me , WDYT. |
…ng modules in child dirs (apache#3063)" This reverts commit 617bff2.
6ca2a27
to
bae4213
Compare
Revert #3063 |
What are the current issue? Why is your compilation errors? @LinMingQiang (In my env, it is fine) |
I think better choice is upgrade your maven version. |
Purpose
In my production environment I get compilation errors :
Parameter ${maven.multiModuleProjectDirectory} is not a recommended parameter. Use ${project.basedir} instead of it.
References :
https://stackoverflow.com/questions/29778262/what-is-maven-multimoduleprojectdirectory-used-for
apache/iotdb#12982
Linked issue: close #xxx
Tests
API and Format
Documentation