You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Trenton (JIRA)" <ji...@codehaus.org> on 2008/04/28 19:33:46 UTC
[jira] Commented: (MNG-3555) transitive dependency exclusion fails
when classifier specified
[ http://jira.codehaus.org/browse/MNG-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132883#action_132883 ]
Trenton commented on MNG-3555:
------------------------------
Oh, one other thing. I think this MAY be related to this other bug, but perhaps not quite the same?
http://jira.codehaus.org/browse/MNG-1823
> transitive dependency exclusion fails when classifier specified
> ---------------------------------------------------------------
>
> Key: MNG-3555
> URL: http://jira.codehaus.org/browse/MNG-3555
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.9
> Environment: Gentoo linux
> Reporter: Trenton
> Priority: Blocker
>
> I have a profile like the one below. When I enable that profile, maven refuses to exclude the dependencies as specified, unless I remove the classifier. This is basically preventing us from using maven. We will have to stick with ant until this is resolved.
> A little bit of background. We have an rmi module and a web module. This profile is in the web module pom. The rmi project creates two different types of jars. One is the rmi server jar, the other the rmi client jar. In the case of the rmi server jar, all the dependencies would be required. And, we allow the rmi server to be run in process (under tomcat). In a case like that, we require all the dependencies. But, when running in standard RMI mode, and using the client jar, we do not need all those dependencies, nor do we want them to be there.
> <profile>
> <!-- use full rmi when doing development, even if inproc server -->
> <id>client</id>
> <build>
> <resources>
> <!-- Copy configurations over to webapp folder -->
> <resource>
> <filtering>true</filtering>
> <directory>${basedir}/src/main/resources</directory>
> <excludes> <!-- Don't need these in production -->
> <exclude>server.properties</exclude>
> <exclude>response_codes.properties</exclude>
> </excludes>
> </resource>
> </resources>
> </build>
> <dependencies>
> <dependency>
> <groupId>ca.athabascau.banner.oros</groupId>
> <artifactId>rmi</artifactId>
> <version>1.1.23-SNAPSHOT</version>
> <scope>compile</scope>
> <classifier>client</classifier>
> <exclusions>
> <exclusion>
> <groupId>ca.athabascau</groupId>
> <artifactId>moneris-test</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.oracle.ojdbc</groupId>
> <artifactId>ojdbc14</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.novell</groupId>
> <artifactId>java-ldap</artifactId>
> </exclusion>
> <exclusion>
> <groupId>commons-dbcp</groupId>
> <artifactId>commons-dbcp</artifactId>
> </exclusion>
> <exclusion>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> </exclusion>
> <exclusion>
> <groupId>commons-pool</groupId>
> <artifactId>commons-pool</artifactId>
> </exclusion>
> <exclusion>
> <groupId>cas</groupId>
> <artifactId>casclient</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> </exclusion>
> <exclusion>
> <groupId>oro</groupId>
> <artifactId>oro</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xml-apis</groupId>
> <artifactId>xml-apis</artifactId>
> </exclusion>
> <exclusion>
> <groupId>javax.activation</groupId>
> <artifactId>activation</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> </dependencies>
> </profile>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira