[ http://jira.codehaus.org/browse/MDEP-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243508#action_243508 ]
Sourajit Basak commented on MDEP-293: ------------------------------------- Attaching a test case to demonstrate this behavior. To reproduce - 1) Unzip the attached zip (I used WinZip for packing) 2) It should create a project structure like pom.xml project1 +-- pom.xml +-- src/main/java/Project1.java project2 +-- pom.xml +-- src/main/... 3) Go to the top level directory and execute - C:\SRC\bug>mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:go-offline -DexcludeArtifactIds=project1 It will fail with the following Missing: ---------- 1) com.ibm.websphere.bpm:project1:jar:1.0.0 Try downloading the file manually from the project website. Why is it trying to download this artifact ? Even -DexcludeGroupIds=com.ibm.... doesn't work. > excludeArtifactIds parameter not processed in go-offline mojo for previous > projects > ----------------------------------------------------------------------------------- > > Key: MDEP-293 > URL: http://jira.codehaus.org/browse/MDEP-293 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: go-offline > Affects Versions: 2.0 > Environment: Windows XP > Reporter: Sourajit Basak > Assignee: Brian Fox > > go-offline mojo is overlooking the excluded artifacts specified like > >>mvn dependency:2.1:go-offline -DexcludeArtifactIds=<artifact-id> > This happens if the <artifact-id> is the output of a preceding project. -- 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