]
Shane Bryzak resolved SEAMSECURITY-48.
--------------------------------------
Assignee: Shane Bryzak
Fix Version/s: 3.0.0.Final
Resolution: Done
Fixed seam-security-external scope in seam-bom.
mvn dep scope wrong with seam-security-external + seam-bom
----------------------------------------------------------
Key: SEAMSECURITY-48
URL:
https://issues.jboss.org/browse/SEAMSECURITY-48
Project: Seam Security
Issue Type: Bug
Reporter: Patrick McFarland
Assignee: Shane Bryzak
Fix For: 3.0.0.Final
The following mvn pom snipet
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>seam-bom</artifactId>
<version>3.0.0-CR9</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.seam.security</groupId>
<artifactId>seam-security-external</artifactId>
</dependency>
</dependencies>
Does not work the way it should, even though all the poms look fine.
It needs to be
<dependency>
<groupId>org.jboss.seam.security</groupId>
<artifactId>seam-security</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.seam.security</groupId>
<artifactId>seam-security-external</artifactId>
<scope>compile</scope>
</dependency>
which makes no sense, as seam-security-external deps seam-security, and I can't see
in seam-bom where its screwing seam-security-external scope up
--
This message is automatically generated by JIRA.
For more information on JIRA, see: