[
https://jira.codehaus.org/browse/MNG-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-2984:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Allow more control around the configuration and use of optional dependencies
> ----------------------------------------------------------------------------
>
> Key: MNG-2984
> URL: https://jira.codehaus.org/browse/MNG-2984
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 2.0.6
> Reporter: Paul Spencer
>
> This request is based on the following posting to the users mailing list.
> How can I include a dependency's optional dependency without
> adding the optional dependency to the pom?
> As an example, shale-test has an optional dependency on commons-digester.
> Since
> my application does not use commons-digester, I do not have it defined as
> a dependency in the pom. When the test that used shale-test failed I had to
> determine the failure was due to a missing dependency that was defined in
> shale-test's
> pom. Thus the following questions.
> 1) Is their a way I can include all of a dependencies optional dependencies
> without knowing what they are?
> <dependency>
> <groupId>org.apache.shale</groupId>
> <artifactId>shale-test</artifactId>
> <version>1.1.0-SNAPSHOT</version>
> <scope>test</scope>
> <includeOptionalDependencies all="true"/> <!-- Just a guess to
> illustrate the intent -->
> <dependency>
> 2) Is their a way I can include selected optional dependencies for a
> dependency?
> <dependency>
> <groupId>org.apache.shale</groupId>
> <artifactId>shale-test</artifactId>
> <version>1.1.0-SNAPSHOT</version>
> <scope>test</scope>
> <includeOptionalDependencies> <!-- Just a guess to illustrate
> the intent -->
> <dependency>
> <groupId>commons-digester</groupId>
> <artifactId>commons-digester</artifactId>
> </dependency>
> </includeOptionalDependencies>
> <dependency>
> 3) Can optional dependencies be grouped to allow for the inclusion of a
> named group of optional dependencies, thus freeing the user from
> having to know and maintain a list of optional dependencies to
> include?
> <dependency>
> <groupId>org.apache.shale</groupId>
> <artifactId>shale-test</artifactId>
> <version>1.1.0-SNAPSHOT</version>
> <scope>test</scope>
> <includeOptionalDependencies group="FunctionalGroup1"/> <!--
> Just a guess to illustrate the intent -->
> <dependency>
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
