You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:50:15 UTC
[jira] (MECLIPSE-566) The plugin fails to exclude certain
dependencies.
[ https://jira.codehaus.org/browse/MECLIPSE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MECLIPSE-566.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> The plugin fails to exclude certain dependencies.
> -------------------------------------------------
>
> Key: MECLIPSE-566
> URL: https://jira.codehaus.org/browse/MECLIPSE-566
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: ARCH: x86
> ECLIPSE_HOME: E:\Programme\eclipse-SDK-3.5M7-win32\eclipse
> NL: de_DE
> OS: win32
> WS: win32
> eclipse.product: org.eclipse.sdk.ide
> eclipse.vm: h:/jdk1.6.0/bin/javaw.exe
> java.runtime.name: Java(TM) SE Runtime Environment
> java.runtime.version: 1.6.0_13-b03
> settings.localRepository: H:\.homedir\.m2\repository
> Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
> Java version: 1.6.0_13
> Java home: h:\jdk1.6.0\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Daniel Kahlenberg
> Priority: Blocker
>
> I have a project, which uses dependencies provided by some CLASSPATH container on one hand and on the other hand dependencies as coded in a pom.xml file. The latter are shown as usual as their own CLASSPATH container ("Maven Dependencies")
> When running the built application finally I need to filter away duplicate entries from the runtime classpath (which are though needed at the compile classpath, so have them in the pom.xml as dependencies as well as in the first mentioned classpath container).
> The relevant parts of my pom.xml look like:
> <project>
> ...
> <dependencies>
> <dependency>
> <groupId>anl.gov</groupId>
> <artifactId>repast.simphony.bin_and_src </artifactId>
> <version>1.2.0</version>
> <scope>compile</scope>
> </dependency>
> <dependency>
> <groupId>anl.gov</groupId>
> <artifactId>saf.core.runtime</artifactId>
> <version>UNKNOWN</version>
> <scope>compile</scope>
> </dependency>
> </dependencies>
> ...
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <version>2.6</version>
> <configuration>
> <excludes>
> <exclude>anl.gov:repast.simphony.bin_and_src</exclude>
> <exclude>anl.gov:saf.core.runtime</exclude>
> </excludes>
> </configuration>
> </plugin>
> ...
> </plugins>
> </pluginManagement>
> </build>
> </project>
> The above configuration is well interpreted, if I run `mvn eclipse:clean eclipse:eclipse`. In that case exactly the dependency tree I want is prepared in the workspace node of my project. BUT if I run `mvn eclipse:clean eclipse:eclipse eclipse:m2eclipse` to get the `Maven Dependencies` node there (need it for the "Run Configuration") and the other m2eclipse features, this dependency tree again contains the yet excluded artifacts. I tried every combination of exclusion, excludes and so on, but didn't get the hint to manage it.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)