rmannibucau commented on PR #1299: URL: https://github.com/apache/maven/pull/1299#issuecomment-1803682292
I fully understand that and this is exactly why I'd like we stop doing that. > We could add "flags" to dependencies, but that would make Maven very very "low level", and would trigger a huge cognitive load on end users IMHO. Rather move "baby steps" with improvements, and we will see where it gets us. IMHO it is where we are today, almost no user or plugin writer fully understand the implications of a type and it is often misused. The design of this PR opens the flags which are exactly the proper design and solution to handle the "context" you need and avoid to workaround the lack of flags with an existing marker, aka type today. See it as it is, would you use `org.superbiz-classpath` in `groupid` to say that `org.superbiz` is in the classpath? Probably not but it is what we do in `type` cause of the lack of alternative. With your PR we can assume it and move it to flags and I think it is what would serve the best users and us. The only challenge will be to solve this in pom v4.0.0 (mvn 3) but ultimately since it is build flags it would just be a matter of sticking to type=extension rule so I think we would be good and help our community rather than promoting more a workaround. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
