mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current
build dependency
--------------------------------------------------------------------------------------------
Key: MINVOKER-107
URL: http://jira.codehaus.org/browse/MINVOKER-107
Project: Maven 2.x Invoker Plugin
Issue Type: Bug
Affects Versions: 1.5
Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-25-generic-pae" arch: "i386" Family: "unix"
Reporter: ludovic
When I build
http://code.google.com/p/mycila/source/browse/mycila-testing/trunk?r=1448 on
revision 1448, the build failed. r1449 is a workaround.
the maven command is : mvn clean deploy
the build failed when running plugin invoker:run with maven3 BUT succeed with
maven2
the failure is due of a missing artifact in the its local repository, the
searched version is a SNAPSHOT, the present version is a timestamped SNAPSHOT
the dependency com.mycila.testing:mycila-testing-api:jar:2.6-SNAPSHOT is not
found because the invoker:install copy the SNAPSHOT with the timestamp during
deploy. And then after during the test, the dependency could not be found. The
reason is because maven3 always deploy using a timestamped version.
@see
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
! workaround
remove
<localRepositoryPath>${project.build.directory}/local-repo</localRepositoryPath>
from the invoker configuration
--
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
