[
http://jira.codehaus.org/browse/MNG-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-3065.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
kind of surprised I can't find a duplicate for this - to my knowledge we are
sticking with not adding these in favour of plugins supporting filtering instead
> Add a <properties> element to the schema for dependencies a la M1
> -----------------------------------------------------------------
>
> Key: MNG-3065
> URL: http://jira.codehaus.org/browse/MNG-3065
> Project: Maven 2
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 2.0.x
> Reporter: Jason Melnick
> Assignee: Brett Porter
> Priority: Minor
>
> Adding the optional <properties> element to the dependency element graph will
> allow more control for plug-in developers, as well as making things like WAR
> packaging much more straightforward.
> Why would I want to have to mess around with declaring dependencies of a WAR
> project that uses it's EARs deps <optional> so that they aren't included in
> WEB-INF/lib? These deps are NOT optional - it's just a workaround to get it
> to work because a clear facility isn't provided.
> Specifying <properties><war.bundle>true</war.bundle></properties> is much
> more clear for all parties.
--
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
