Maven › Maven - Issues

[jira] Created: (MRELEASE-285) Unresolved test-jar dependency during release

Classic

List

Threaded

21 messages Options

JIRA jira@codehaus.org

[jira] Created: (MRELEASE-285) Unresolved test-jar dependency during release

Unresolved test-jar dependency during release
---------------------------------------------

Key: MRELEASE-285
URL: http://jira.codehaus.org/browse/MRELEASE-285
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-4
Environment: Maven version: 2.0.7
Java version: 1.5.0_07
OS name: "mac os x" version: "10.4.10" arch: "i386"
Reporter: Rod Coffin
Attachments: example.jar

I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:

release-test-jar (parent project)
project-with-test-jar (submodule)
=> project-with-test-jar-1.0.jar
=> project-with-test-jar-1.0-tests.jar
project-using-test-jar (submodule)
=> project-user-test-jar-1.0.jar

When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:

1 required artifact is missing.

for artifact:
com.rfc:project-using-test-jar:jar:1.1

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
----------
1) com.rfc:project-with-test-jar:test-jar:tests:1.1

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
-Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
-Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) com.rfc:project-using-test-jar:jar:1.1
2) com.rfc:project-with-test-jar:test-jar:tests:1.1

----------
1 required artifact is missing.

for artifact:
com.rfc:project-using-test-jar:jar:1.1

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

--
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

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117275 ]

Kevin Wilson commented on MRELEASE-285:
---------------------------------------

found that running the following sequence works around the dependency:
mvn release:prepare
# results in failure
mvn install
mvn release:prepare
# This time the prepare finishes and checks in the modified pom.xml.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

--
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

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119031 ]

Jim Cushing commented on MRELEASE-285:
--------------------------------------

I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MJAR-95 ( http://jira.codehaus.org/browse/MJAR-95 ), which might be related.

JIRA jira@codehaus.org

[jira] Issue Comment Edited: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119031 ]

jimothy edited comment on MRELEASE-285 at 1/7/08 4:02 PM:
--------------------------------------------------------------

I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MNG-3350 ( http://jira.codehaus.org/browse/MNG-3350 ), which might be related.

was (Author: jimothy):
I think the documentation at http://maven.apache.org/guides/mini/guide-attached-tests.html is incorrect with regards to the classifier. See MJAR-95 ( http://jira.codehaus.org/browse/MJAR-95 ), which might be related.

JIRA jira@codehaus.org

[jira] Updated: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MRELEASE-285:
-------------------------------

Fix Version/s: 2.0-beta-8

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0-beta-8
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Closed: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MRELEASE-285.
------------------------------

Resolution: Fixed
Fix Version/s: (was: 2.0-beta-8)
2.0

I believe this issue is now fixed with the release of the maven jar plugin 2.2.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135812#action_135812 ]

Krasimir Chobantonov commented on MRELEASE-285:
-----------------------------------------------

The issue is still present and this only happens when I'm trying to release the project - the building of the project is fine.

Maven : version 2.0.8
maven jar plugin : version 2.2
maven release plugin : version 2.0-beta-7

java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing)

The workaround using mvn clean install works but this can't be performed by continuum server automatically.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Reopened: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier reopened MRELEASE-285:
--------------------------------

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142862#action_142862 ]

Valerio Schiavoni commented on MRELEASE-285:
--------------------------------------------

I get the same problema s Krasmir. The workaround proposed works fine, but with inhibits CI.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147997#action_147997 ]

Damir Malenicic commented on MRELEASE-285:
------------------------------------------

I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Issue Comment Edited: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147997#action_147997 ]

dmalenic edited comment on MRELEASE-285 at 9/15/08 8:40 AM:
-------------------------------------------------------------------

I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

Maven version 2.0.9
Maven release plug-in version : 2.0-beta

was (Author: dmalenic):
I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

Maven version 2.0.9
Maven release plug-in version : 2.0.7-beta

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Issue Comment Edited: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147997#action_147997 ]

dmalenic edited comment on MRELEASE-285 at 9/15/08 8:39 AM:
-------------------------------------------------------------------

I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

Maven version 2.0.9
Maven release plug-in version : 2.0.7-beta

was (Author: dmalenic):
I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Issue Comment Edited: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147997#action_147997 ]

dmalenic edited comment on MRELEASE-285 at 9/15/08 8:40 AM:
-------------------------------------------------------------------

I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

Maven version 2.0.9
Maven release plug-in version : 2.0-beta-7

was (Author: dmalenic):
I've got the same problem with <classifier>sources</classifier> so it might be the generic classifier handling problem within the release plug-in

Maven version 2.0.9
Maven release plug-in version : 2.0-beta

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149283#action_149283 ]

Basil James Whitehouse III commented on MRELEASE-285:
-----------------------------------------------------

I found a workaround to this based on an unrelated [hint in this thread|http://www.mail-archive.com/users@.../msg79498.html]: instead of using a classifier use a type of {{test-jar}} in the dependency declaration. E.g:
{noformat}
<dependency>
<groupId>com.company.project</groupId>
<artifactId>core</artifactId>

<type>test-jar</type>
<scope>test</scope>
</dependency>
{noformat}

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149287#action_149287 ]

Basil James Whitehouse III commented on MRELEASE-285:
-----------------------------------------------------

Oddly this issue doesn't happen when running a dry run of release:perform (e.g. mvn release:perform -DdryRun=true). This makes it awkward to verify fixes since a real release:prepare has to be performed and that will modify your poms which have to be reverted if there was a failure.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149293#action_149293 ]

Basil James Whitehouse III commented on MRELEASE-285:
-----------------------------------------------------

Actually I think this problem runs deeper than just test-jar classifiers. Other classifiers are broken as well. I've tried this with a project where there's an EJB client jar (with a classifier of 'client') and that doesn't work. Using a type of {{ejb-client}} fixed this as well. I'm guessing that any dependency with a classifier is probably broken.

FYI: the ejb-client issue seems to be different from MRELEASE-129.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Updated: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Heritier updated MRELEASE-285:
-------------------------------------

Component/s: prepare

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

[jira] Commented: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174613#action_174613 ]

Florian Müller commented on MRELEASE-285:
-----------------------------------------

I've found an another workaround.
You could add a <optional>true</optional> to your dependency, like this:
<dependency>
<groupId>ch.swisscompagny.project</groupId>
<artifactId>web</artifactId>
<version>${project.parent.version}</version>
<classifier>classes</classifier>
<optional>true</optional>
</dependency>

It's very useful with the maven-war-plugin and the overlay feature.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Fix For: 2.0
>
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

Updated: (MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ http://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRELEASE-285:
----------------------------------

Fix Version/s: (was: 2.1)

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: http://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

JIRA jira@codehaus.org

(MRELEASE-285) Unresolved test-jar dependency during release

In reply to this post by JIRA jira@codehaus.org

[ https://jira.codehaus.org/browse/MRELEASE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295131#comment-295131 ]

Israel E. Bethencourt commented on MRELEASE-285:
------------------------------------------------

Maybe this bug is related to the same issue:

http://jira.codehaus.org/browse/MRELEASE-567

But seems nothing is moving about this.

> Unresolved test-jar dependency during release
> ---------------------------------------------
>
> Key: MRELEASE-285
> URL: https://jira.codehaus.org/browse/MRELEASE-285
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-4
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_07
> OS name: "mac os x" version: "10.4.10" arch: "i386"
> Reporter: Rod Coffin
> Attachments: example.jar
>
>
> I have a multi-module project where one project produces a normal jar and a test-jar (http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html). Another submodule has a test scoped dependency on the test-jar from the first submodule. For example, this is the structure and produced artifacts for a small sample (attached) I built to reproduce this behavior:
> release-test-jar (parent project)
> project-with-test-jar (submodule)
> => project-with-test-jar-1.0.jar
> => project-with-test-jar-1.0-tests.jar
> project-using-test-jar (submodule)
> => project-user-test-jar-1.0.jar
> When I run a 'clean install' the build succeeds. However, when I run a 'release:prepare' the build fails with the following error:
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
> ----------
> 1) com.rfc:project-with-test-jar:test-jar:tests:1.1
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.rfc -DartifactId=project-with-test-jar \
> -Dversion=1.1 -Dclassifier=tests -Dpackaging=test-jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
> Path to dependency:
> 1) com.rfc:project-using-test-jar:jar:1.1
> 2) com.rfc:project-with-test-jar:test-jar:tests:1.1
> ----------
> 1 required artifact is missing.
> for artifact:
> com.rfc:project-using-test-jar:jar:1.1
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> Judging from the stack trace this problem seems to occur during dependency resolution as is declared PrepareReleaseMojo with the annotation "@requiresDependencyResolution test".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira