[
https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306136#comment-306136
]
Tamás Cservenák edited comment on MINVOKER-107 at 8/14/12 6:33 AM:
-------------------------------------------------------------------
Just for the record: I am able to regularly reproduce this bug in combination
of Maven 3.0.3 and invoking {{deploy}} goal (I was baffled why it passes on me
locally, and failing on CI: simply, I was doing as usual {{mvn clean install}}
and CI was doing {{mvn clean deploy}}). This was stated above too by David.
OTOH, Maven 3.0.4 for me locally, does NOT triggers this bug, and the
{{invoker:install}} step goes just fine with {{deploy}} goal invoked on CLI.
So for me, workaround is to upgrade CI to Maven 3.0.4 (as for me locally {{mvn
clean deploy}} + Maven 3.0.4 does not fails, in contrary as doing same with
Maven 3.0.3, which does).
was (Author: cstamas):
Just for the record: I am able to regularly reproduce this bug in
combination of Maven 3.0.3 and invoking {{deploy}} goal (I was baffled why it
passes on me locally, and failing on CI: simply, I was doing as usual {{mvn
clean install}} and CI was doing {{mvn clean deploy}}). This was stated above
too by David.
OTOH, Maven 3.0.4 for me locally, does NOT triggers this bug, and the
{{invoker:install} step goes just fine.
So for me, workaround is to upgrade CI to Maven 3.0.4 (as for me locally {{mvn
clean deploy}} + Maven 3.0.4 does not fails as doing same with Maven 3.0.3
does).
> mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current
> build dependency
> --------------------------------------------------------------------------------------------
>
> Key: MINVOKER-107
> URL: https://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
> Attachments: MINVOKER-107.diff
>
>
> 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, 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
