[
http://jira.codehaus.org/browse/MNG-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4766.
----------------------------------
Resolution: Duplicate
Assignee: Benjamin Bentmann
> optional dependencies
> ---------------------
>
> Key: MNG-4766
> URL: http://jira.codehaus.org/browse/MNG-4766
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Dependencies
> Environment: not relevant
> Reporter: Tom Eugelink
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> Optional dependencies are (a group of) transitive dependencies that must be
> enabled to be resolved.
> Use case:
> I have a big Swing util & component library that uses all kinds of 3rd party
> libraries. These libraries are not required in each project, so all these
> dependencies are set to "provided". If I want a project to use the component,
> I must include some version of the correct 3rd party libraries libraries and
> hope that version is compatible with the one specified as provided. Would it
> be practical to be able to enable a certain dependency group on the lib's
> dependencies.
> So for example in a project using the swing lib (typing square brackets
> because pointy ones may cause problems):
> [dependency]
> [groupId]...[/groupId]
> [artifactId]BigSwingLib[/artifactId]
> [version]1.0[/version]
> [resolve]jpa[/resolve]
> [resolve]substance[/resolve]
> [/dependency]
> The last two lines may cause multiple "optional" dependencies to be resolved;
> e.g. "jpa" would include jpa-api-1.0.jar and eclipselink-1.2.jar, "substance"
> would include substance-6.0.jar and trident-1.1.jar.
> Naturally in the big swing pom these dependencies should be marked with
> scope="optional" and group="jpa" (group is a comma separated list of id's)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
