[ http://jira.codehaus.org/browse/MNG-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3277. ----------------------------- Assignee: Brett Porter Resolution: Won't Fix including doesn't make sense for all packaging types, so blending this into the resolution mechanism doesn't make much sense. I think it is best to handle this at a plugin level > Add new dependency scope: include > --------------------------------- > > Key: MNG-3277 > URL: http://jira.codehaus.org/browse/MNG-3277 > Project: Maven 2 > Issue Type: Improvement > Components: Dependencies > Reporter: Francois Fernandes > Assignee: Brett Porter > > It should be possible to specify a included scope for dependencies. They have > the same meaning as runtime but with the little difference that they will be > included into the resulting artifact. > This could be achieved by using the jar-with-dependencies descriptor of the > assembly plugin. > Anyway, it would be nice to specify a dependency, which includes some or all > of its artiacts and the missing (not included) are resolved transitively. -- 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