[
https://issues.jboss.org/browse/SHRINKWRAP-401?page=com.atlassian.jira.pl...
]
Aslak Knutsen commented on SHRINKWRAP-401:
------------------------------------------
Noticed this as well.. removing <scope>import</scope> from the Arq bom seems
to fix it as well..
We're mixing some use cases here. While via Arq-BOM you in 99% of the cases want test
scope, but via SW BOMs, you might want runtime.
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