Bug 812835 - Arquillian BOM set ShrinkWrap dependencies into runtime scope
Arquillian BOM set ShrinkWrap dependencies into runtime scope
Status: CLOSED NEXTRELEASE
Product: JBoss Enterprise WFK Platform 2
Classification: JBoss
Component: Arquillian (Show other bugs)
2.0.0.ER3
Unspecified Unspecified
unspecified Severity urgent
: ---
: 2.0.0.ER5
Assigned To: Aslak Knutsen
Karel Piwko
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-16 07:50 EDT by Karel Piwko
Modified: 2012-06-22 07:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-22 07:47:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karel Piwko 2012-04-16 07:50:46 EDT
Description of problem:

When Arquillian BOM is used in den

Version-Release number of selected component (if applicable):

1.0.0.Final

How reproducible:

Always.

Steps to Reproduce:
1. Import arquillian-bom in <dependencyManagement>
2. Add Arquillian-junit-standalone into <dependencies>
  
Actual results:

ShrinkWrap artifact are in runtime scope, thus packaged with application WAR/EAR/JAR.

Expected results:

Everything is test-scoped.

Additional info:

Usability blocker. See following JIRAs for further information.

https://issues.jboss.org/browse/SHRINKWRAP-401
https://issues.jboss.org/browse/SHRINKDESC-117
https://issues.jboss.org/browse/SHRINKRES-33
Comment 1 Karel Piwko 2012-04-16 08:14:04 EDT
Note that SHRINKDESC and SHRINKRES are not a part of Arquillian WFK BOM.
Comment 2 Karel Piwko 2012-04-16 09:00:07 EDT
Description of problem:

When Arquillian BOM is used in <dependencyManagement> section, scope for ShrinkWrap dependecies is overridden to "runtime"
Comment 3 Karel Piwko 2012-04-23 09:00:48 EDT
Fixed in https://issues.jboss.org/browse/JBPAPP-8534.
Comment 4 Karel Piwko 2012-05-16 11:09:24 EDT
Verified.

Note that community version is still affected, however in WFK we have a special BOM file where this is fixed.
Comment 5 Karel Piwko 2012-06-22 07:47:45 EDT
This issue is fixed in WFK 2.0.0. WFK 2.0.0 has it's own BOM file.

Note You need to log in before you can comment on or make changes to this bug.