[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-136) System scoped dependencies shouldn't be added to WAR

Karel Piwko (JIRA) jira-events at lists.jboss.org
Tue Nov 12 03:27:07 EST 2013


     [ https://issues.jboss.org/browse/SHRINKRES-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karel Piwko closed SHRINKRES-136.
---------------------------------



Closing issues. Released as a part of 2.0.0-beta-4 release.
                
> System scoped dependencies shouldn't be added to WAR
> ----------------------------------------------------
>
>                 Key: SHRINKRES-136
>                 URL: https://issues.jboss.org/browse/SHRINKRES-136
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>          Components: impl-maven
>    Affects Versions: 2.0.0-beta-3
>            Reporter: Ron Šmeral
>            Assignee: Karel Piwko
>             Fix For: 2.0.0-beta-4
>
>
> When resolving dependencies with {{importRuntimeDependencies}} and adding them to an archive as in
> {code}
> File[] libs = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().asFile();
> ShrinkWrap.create(WebArchive.class, "seam-blog.war").addAsLibraries(libs);
> {code}
> system-scoped dependencies are resolved and added to the archive as well.
> This should not happen and should be aligned with the behaviour of the maven war plugin, as described in this issue: https://jira.codehaus.org/browse/MWAR-23.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the shrinkwrap-issues mailing list