[ http://jira.codehaus.org/browse/MNG-2317?page=comments#action_75572 ] Jason van Zyl commented on MNG-2317: ------------------------------------
We should probably get Vincent to look at this and see if he has done anything like this in Cargo. But basically this looks like ApplicationServerToolChain and ApplicationServerToolChainAware. > Provided scope dependencies are based in target app server, current approach > doesn't work very well > --------------------------------------------------------------------------------------------------- > > Key: MNG-2317 > URL: http://jira.codehaus.org/browse/MNG-2317 > Project: Maven 2 > Issue Type: New Feature > Components: Dependencies > Affects Versions: 2.0.4 > Reporter: Carlos Sanchez > Fix For: 2.1 > > > We'd need a mechanism for the user to set the target app server for stuff > like wars, ears,... > Maybe a plugin, maybe a core feature, that would iterate through dependencies > and set scope as "provided" depending on the filter > A filter can be an xml file listing the dependencies that have to be provided > (grop+artifact ?+version?) > we can provide a set of predefined filters like tomcat4, tomcat5, > geronimo,... and the user would be able to add new ones -- 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
