Re: [PR] [MNG-7255] Infer groupId for dependencies [maven]

["gnodet (via GitHub)" <gi...@apache.org>]

gnodet commented on PR #1696:
URL: https://github.com/apache/maven/pull/1696#issuecomment-2343492234

   > Simple as that.
   > 
   > But a "minority report": I personally disagree with this, as it will encourage using A only for dependencies (as G and V are inferred), thus, will make depMgt less compelling. Not to mention how will this plus BOMs behave?
   
   Not sure to understand.  We now warn when using BOMs inside a reactor for dependency management and the only point in using dependency management for dependencies coming from the reactor is exactly to avoid writing the version. I don't really see how this is different.  Note that this only applies to dependencies that are part of the reactor.  Projects that have multiple subprojects usually define in their dependency management section the list of artifacts actually produced during the build to avoid having to specify the version everywhere.  That's what we have in [maven](https://github.com/apache/maven/blob/master/pom.xml#L201-L353), [maven-resolver](https://github.com/jline/jline3/blob/4ccf282c91daa0fc96ed6030e053dd28a4aba342/builtins/src/test/java/org/jline/example/Example.java#L328-L335) and almost all projects I've seen.  I don't see any benefit in having to maintain this section manually, since there's absolutely no value there.  What am I missing ? @cstamas 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org