[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3311) Maven overrides dependencyManagement with transitive dependencies
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Aug 25 10:30:38 EDT 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12426466#action_12426466 ]
Pete Muir commented on JBSEAM-3311:
-----------------------------------
### Eclipse Workspace Patch 1.0
#P seam_2_0
Index: build/ui.pom.xml
===================================================================
--- build/ui.pom.xml (revision 8785)
+++ build/ui.pom.xml (working copy)
@@ -97,6 +97,18 @@
<artifactId>richfaces-ui</artifactId>
<optional>true</optional>
</dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-collections</groupId>
+ <artifactId>commons-collections</artifactId>
+ </dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-digester</groupId>
+ <artifactId>commons-digester</artifactId>
+ </dependency>
<dependency>
<groupId>javax.faces</groupId>
Index: build/core.pom.xml
===================================================================
--- build/core.pom.xml (revision 8785)
+++ build/core.pom.xml (working copy)
@@ -20,6 +20,12 @@
<artifactId>hibernate</artifactId>
<optional>true</optional>
</dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-logging</groupId>
+ <artifactId>commons-logging</artifactId>
+ </dependency>
<dependency>
<groupId>org.hibernate</groupId>
#P seam
Index: build/ui.pom.xml
===================================================================
--- build/ui.pom.xml (revision 8799)
+++ build/ui.pom.xml (working copy)
@@ -103,6 +103,18 @@
<artifactId>richfaces-ui</artifactId>
<optional>true</optional>
</dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-collections</groupId>
+ <artifactId>commons-collections</artifactId>
+ </dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-digester</groupId>
+ <artifactId>commons-digester</artifactId>
+ </dependency>
<dependency>
<groupId>javax.faces</groupId>
Index: build/core.pom.xml
===================================================================
--- build/core.pom.xml (revision 8799)
+++ build/core.pom.xml (working copy)
@@ -20,6 +20,12 @@
<artifactId>hibernate</artifactId>
<optional>true</optional>
</dependency>
+
+ <!-- Maven's "nearest" dependency resolution doesn't take into account parent dependency management! -->
+ <dependency>
+ <groupId>commons-logging</groupId>
+ <artifactId>commons-logging</artifactId>
+ </dependency>
<dependency>
<groupId>org.hibernate</groupId>
> Maven overrides dependencyManagement with transitive dependencies
> -----------------------------------------------------------------
>
> Key: JBSEAM-3311
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3311
> Project: Seam
> Issue Type: Task
> Components: Build
> Reporter: Pete Muir
> Fix For: 2.0.3.CR2, 2.1.0.BETA2
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list