-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[MNG-8210] Replace Maven "module" term by "subproject" #1651
Conversation
@@ -708,6 +708,9 @@ public List<Plugin> getBuildPlugins() { | |||
} | |||
|
|||
public List<String> getModules() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deprecate it? Or maybe does not matter, as in API 4 plugins have no reach to this class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I was assuming this change targets 4.x api and plugins, so I would not care about the v3 api.
api/maven-api-core/src/main/java/org/apache/maven/api/services/ModelBuilder.java
Outdated
Show resolved
Hide resolved
Shouldn't the subprojects be transformed to modules in the consumer pom? |
Actually, the modules/subprojects are build information, so not available in the consumer POM. |
…deprecated to modules field in model
Based on @desruisseaux initial commit to rename subproject #1649.
This PR adds
subprojects
to 4.1.0 POM, deprecatemodules
, and add a discovery mechanism which kicks in when: