jira-importer commented on issue #190: URL: https://github.com/apache/maven-war-plugin/issues/190#issuecomment-2967849115
**[David Boden](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=daveboden)** commented > It looks like there is a missing dependency scope. The one that is required for compilation but not in the runtime. I strongly agree with this comment. However, I fundamentaly don't understand why "provided" scope doesn't declare transitive dependencies (which would make it exactly fit the bill of a scope that was required for compilation but not for runtime) Reasoning: If a subproject is dependent at runtime on a particular product then surely the superproject will, at the end of the day, need that product on its runtime classpath. This is the normal use-case. On the odd occasion that we don't want this behaviour, the developer can "exclude" unwanted dependencies and then have a talk with the person who manages the subproject and say "do you really need this dependency at runtime?". Speaking of use cases, it worries me that Maven doesn't have a simple description of expected use cases for each plugin right at the top of the documentation. An example that relates to this Jira issue is: Use Case: Developer packages multiple war files in an ear and wants to consolidate the dependencies onto the ear classpath. This involves: 1. Excluding the dependency jar files from the war files. 2. Marking the war files in a way that the ear file generation process will know to include them. 3. Changing the ear plugin behaviour so that when it sees that jars are excluded from the war they are ear. 4. Create entries in the war manifest so that the dependent jars can be loaded from the ear classloader. Not an easy use case, by any means, but a very, very common one and one that Maven 2 does not currently support. -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
