[shrinkwrap-issues] [JBoss JIRA] (SHRINKWRAP-401) Scoped artifacts in ShrinkWrap BOM

Karel Piwko (JIRA) jira-events at lists.jboss.org
Mon Apr 16 08:14:17 EDT 2012


    [ https://issues.jboss.org/browse/SHRINKWRAP-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684460#comment-12684460 ] 

Karel Piwko commented on SHRINKWRAP-401:
----------------------------------------

And yes, removing "import" scope will actually fix that, however it would change what dependencies will be available from dependencyManagement as well.
                
> Scoped artifacts in ShrinkWrap BOM 
> -----------------------------------
>
>                 Key: SHRINKWRAP-401
>                 URL: https://issues.jboss.org/browse/SHRINKWRAP-401
>             Project: ShrinkWrap
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.0
>            Reporter: Karel Piwko
>            Assignee: Andrew Rubinger
>            Priority: Blocker
>         Attachments: pom.xml, pom.xml, Screenshot-Java EE - kitchensink-search-ispn-slave-pom.xml - Eclipse .png
>
>
> ShrinkWrap BOM contains scoped artifacts. 
> When bom is imported into <dependencyManagement> that scope is activated and overrides test scope, 
> resulting with "runtime" dependencies being included as a part of resulting JAR/WAR/EAR archive.
> This is a serious usability flaw and therefore marking as Blocker.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the shrinkwrap-issues mailing list