[jira] (MRELEASE-729) release:branch makes pom changes for branch in 'master' before branching
Joseph Walton created MRELEASE-729:
--
Summary: release:branch makes pom changes for branch in 'master'
before branching
Key: MRELEASE-729
URL: https://jira.codehaus.org/browse/MRELEASE-729
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: Git
Affects Versions: 2.2.2
Reporter: Joseph Walton
{{release:branch}} makes the change for the branch version before branching.
This means the version change is seen in the trunk's history.
If master is currently '1-SNAPSHOT':
{code}
* 1-SNAPSHOT [master]
{code}
and I create a new 'branch-with-hacks' branch as '1.hacks-SNAPSHOT' then I'll
see this in my log:
{code}
* 1-SNAPSHOT [master]
|
* 1.hacks-SNAPSHOT [branch-with-hacks]
|
* 1-SNAPSHOT
{code}
with a commit and a revert on master where I would expect:
{code}
* 1.hacks-SNAPSHOT [branch-with-hacks]
|
* 1-SNAPSHOT [master]
{code}
with 'master' remaining unaffected.
--
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
[jira] (MRELEASE-728) The commit message for release:branch is wrong
[ https://jira.codehaus.org/browse/MRELEASE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289107#comment-289107 ] Joseph Walton commented on MRELEASE-728: It looks like svn uses 'prepare for next development iteration' for the commit that bumps the trunk version; git refers to it as a release. > The commit message for release:branch is wrong > -- > > Key: MRELEASE-728 > URL: https://jira.codehaus.org/browse/MRELEASE-728 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.2.1 > Environment: git 1.7.5.4 >Reporter: Adrien Ragot > > Using Git, when you do mvn release:branch -DbranchName=xxx, > the commit message for master is "[maven-release-plugin] prepare release xxx". > The right commit message should be "[maven-release-plugin] prepare branch > xxx", like for Svn. -- 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
[jira] (MRELEASE-728) The commit message for release:branch is wrong
Adrien Ragot created MRELEASE-728: - Summary: The commit message for release:branch is wrong Key: MRELEASE-728 URL: https://jira.codehaus.org/browse/MRELEASE-728 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.2.1 Environment: git 1.7.5.4 Reporter: Adrien Ragot Using Git, when you do mvn release:branch -DbranchName=xxx, the commit message for master is "[maven-release-plugin] prepare release xxx". The right commit message should be "[maven-release-plugin] prepare branch xxx", like for Svn. -- 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
[jira] (MASSEMBLY-595) Tar file contains world-writeable files when fileSets with and without fileMode are mixed
[
https://jira.codehaus.org/browse/MASSEMBLY-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Walton updated MASSEMBLY-595:
Attachment: 0001-MASSEMBLY-595-Upgrade-to-pick-up-PLXCOMP-196-and-PLX.patch
Now fixed in PLXCOMP. Upgrade to 2.0.2 to pick up the fixes.
> Tar file contains world-writeable files when fileSets with and without
> fileMode are mixed
> -
>
> Key: MASSEMBLY-595
> URL: https://jira.codehaus.org/browse/MASSEMBLY-595
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2.2
>Reporter: Joseph Walton
> Attachments:
> 0001-MASSEMBLY-595-Upgrade-to-pick-up-PLXCOMP-196-and-PLX.patch,
> MASSEMBLY-595.tar.gz
>
>
> I have an assembly descriptor with some fileSets that do and some that don't
> set the fileMode. Any resources after fileMode has been set end up with
> world-writable permissions.
> This assembly descriptor:
> {code}
>
> dist
>
> tar.gz
>
>
>
> src/main/files
> a
>
>
> src/main/files
> b
> 0744
>
>
> src/main/files
> c
>
>
>
> {code}
> gives:
> {code}
> $ tar tvvf target/test-1-SNAPSHOT-dist.tar.gz
> drwxr-xr-x jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/a/
> -rw-r--r-- jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/a/empty-file
> drwxrwxrwx jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/b/
> -rwxr--r-- jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/b/empty-file
> drwxrwxrwx jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/c/
> -rwxrwxrwx jwalton/jwalton 0 2012-01-05 18:55 test-1-SNAPSHOT/c/empty-file
> {code}
> The third copy of the fileSet, with no {{fileMode}} set, is now
> world-writable, unlike the first. The second directory, with no
> {{directoryMode}} specified, has the same problem.
--
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
[jira] (MNG-2974) Unable to resolve & download snapshot versions from CLI
[
https://jira.codehaus.org/browse/MNG-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-2974:
---
Description:
When I try to use a snapshot released version of a plugin on the command line
interface maven doesn't resolve these and download them from registered the
plugin repositories. When using non snapshot versions it is not a problem to
resolve and download them. When I add the plugin (a snapshot version) to a POM
and run it it does download it. So the problem does not lie with the repo
which is registered in the settings.xml in a profile which is active. The
problem just seems to lie with the resolving and dowloading part of the
process. Cause after the snapshot plugin is download using the POM way it
does find the plugin when running it from the CLI.
I first discovered this bug when trying to use the Maven install plugin. Here
are commands used in the process. Reproding this way of use I got the same
result when requesting other snapshot version of plugins that were not in the
repository.
Command used to load snapshot version from the CLI (this gives the error you
find below)
mvn org.apache.maven.plugins:maven-install-plugin:2.2-SNAPSHOT:install-file
(... + correct plugin params )
Command used to load a specific released version from the CLI
mvn org.apache.maven.plugins:maven-install-plugin:2.1:install-file (... +
correct plugin params )
Command used to load a the top released version from the CLI
mvn org.apache.maven.plugins:maven-install-plugin:install-file (... + correct
plugin params )
Settings.xml File
{code:xml}
apachesnapshots
d
http://people.apache.org/repo/m2-snapshot-repository/
false
true
allways
ignore
{code}
Hope I gave you enough information to fix this error. It's not major but does
hinder me at this point cause now I have to manually place this plugin in
everyone of my developers local repo.
was:
When I try to use a snapshot released version of a plugin on the command line
interface maven doesn't resolve these and download them from registered the
plugin repositories. When using non snapshot versions it is not a problem to
resolve and download them. When I add the plugin (a snapshot version) to a POM
and run it it does download it. So the problem does not lie with the repo
which is registered in the settings.xml in a profile which is active. The
problem just seems to lie with the resolving and dowloading part of the
process. Cause after the snapshot plugin is download using the POM way it
does find the plugin when running it from the CLI.
I first discovered this bug when trying to use the Maven install plugin. Here
are commands used in the process. Reproding this way of use I got the same
result when requesting other snapshot version of plugins that were not in the
repository.
Command used to load snapshot version from the CLI (this gives the error you
find below)
mvn org.apache.maven.plugins:maven-install-plugin:2.2-SNAPSHOT:install-file
(... + correct plugin params )
Command used to load a specific released version from the CLI
mvn org.apache.maven.plugins:maven-install-plugin:2.1:install-file (... +
correct plugin params )
Command used to load a the top released version from the CLI
mvn org.apache.maven.plugins:maven-install-plugin:install-file (... + correct
plugin params )
Settings.xml File
apachesnapshots
d
http://people.apache.org/repo/m2-snapshot-repository/
false
true
allways
ignore
Hope I gave you enough information to fix this error. It's not major but does
hinder me at this point cause now I have to manually place this plugin in
everyone of my developers local repo.
> Unable to resolve & download snapshot versions from CLI
> ---
>
> Key: MNG-2974
> URL: https://jira.codehaus.org/browse/MNG-2974
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6
> Environment: Windows
>Reporter: Yves Van Steen
>Assignee: Brett Porter
>
> When I try to use a snapshot released version of a plugin on the command line
> interface maven doesn't resolve
[jira] (MEAR-60) Improve support for skinny war files
[ https://jira.codehaus.org/browse/MEAR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289096#comment-289096 ] Connor Barry commented on MEAR-60: -- Hi Andreas, I'm a little new to Maven internals but experiencing this exact problem as well. How did you configure your war plugin to use the non-timestamped version of the jar dependencies? I feel like that is a little cleaner than keeping the timestamp versions around in the EAR's APP-INF/lib folder. > Improve support for skinny war files > > > Key: MEAR-60 > URL: https://jira.codehaus.org/browse/MEAR-60 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Affects Versions: 2.3 > Environment: mvn 2.0.5 >Reporter: Marcel Schutte >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.7 > > Attachments: maven-ear-plugin-addon-1.0-SNAPSHOT.jar, > maven-ear-plugin-addon-1.0-SNAPSHOT-sources.jar, > maven-ear-plugin-MEAR-60.patch > > > Provide a boolean configuration option for webModules to include the war's > transitive dependencies. > As described on > http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html it > is very common in a J2EE environment to use so called skinny wars. Here the > war's WEB-INF/lib will not contain the dependent jars, but instead they are > packaged inside the EAR. The war references them through its > META-INF/MANIFEST.MF > This option could be used to avoid the 'painful part' mentioned in the above > web page. The war's dependencies wouldn't have to be duplicated alongside the > ear's. > I also found an old issue (MEAR-14) which has asked for the current default > behavior of not including the transitive dependencies. It suggests a property > to include specific dependencies of the war. As far as I can tell this has > never been implemented and this is also not what I am asking for. My proposal > is an all of nothing kind of option for each war module in the ear. > On a side note, for me this is the part where removal of the old maven 1 > style properties per dependency is missed the most. With them it was possible > to decide for each single dependency whether to put it in WEB-INF/lib or > reference it through the manifest classpath. But of course, then we didn't > have the transitive dependencies -- 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
[jira] (MRELEASE-727) release plugin uses wrong checkout directory
Dominik Bartholdi created MRELEASE-727: -- Summary: release plugin uses wrong checkout directory Key: MRELEASE-727 URL: https://jira.codehaus.org/browse/MRELEASE-727 Project: Maven 2.x Release Plugin Issue Type: Bug Components: perform Affects Versions: 2.2.2, 2.2 Environment: mvn 3.0.3 Reporter: Dominik Bartholdi Priority: Blocker Attachments: release_failed.txt, testproject.zip When performing a release build on a multi module project, the plugin uses a wrong checkout directory and therefore is unable to perform the release. I tested this with both version 2.2 and 2.2.2 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project test_multi_parent: Error executing Maven. Working directory "/Users/domi/work/ws/sts_0/test_multi_parent/target/checkout/test_multi_parent/test_multi_parent" does not exist! -> [Help 1] We use flat project structure (where parent and modul project are in the same directory) The SVN Repo looks like this: .../svnrepos/KUQ/trunk/test_multi_parent .../svnrepos/KUQ/trunk/test_multi_module1 I'll attache a minimal test project to reproduce it and a file containing the whole log output for release:prepare and release:perform To reproduce the problem: - adjust the SVN paths in the pom.xml - checkin to SVN - release:prepare - release:perform -Dgoals=install -- 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
[jira] (MNG-5230) Command line option to exclude modules from reactor
[
https://jira.codehaus.org/browse/MNG-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289070#comment-289070
]
Falko Modler commented on MNG-5230:
---
Good point! Before I created this ticket, I was actually looking for such a
negation feature of -pl.
> Command line option to exclude modules from reactor
> ---
>
> Key: MNG-5230
> URL: https://jira.codehaus.org/browse/MNG-5230
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.0.3
>Reporter: Falko Modler
>
> Every now and then I want to exclude one or more modules from a rather large
> reactor build.
> One reason for this can be: The respective module has tests that take long
> time to execute and I know that I don't need to execute them.
> Introducing yet another profile for this is not desirable for various reasons.
> So, something like an opposite to -pl would come in handy. Let's say "-el"
> for "exclude list".
> Example:
> {code}
> root
> + module a
> + module a1
> + module a2
> + module b
> + module b1
> + module c
> {code}
> Calling _mvn -el a1,c_ would build all modules execpt a1 and c.
--
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
[jira] (MINVOKER-107) mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current build dependency
[
https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289062#comment-289062
]
Dawid Weiss commented on MINVOKER-107:
--
Same with Maven 3.0.3.
> 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
> ${project.build.directory}/local-repo
> 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
[jira] (MINVOKER-107) mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current build dependency
[
https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289061#comment-289061
]
Dawid Weiss edited comment on MINVOKER-107 at 1/22/12 4:38 AM:
---
This issue is a bug and is repeatable for me. The invoker plugin installs
shapshot versions of artefacts but this happens ONLY if running:
{noformat}mvn clean deploy{noformat}
and NOT if running:
{noformat}mvn clean verify{noformat}
So it is the deployment of artefacts that somehow renders -SNAPSHOT versions to
concrete numbered revisions. Build logs from our Bamboo where this is apparent:
Passing build (mvn clean verify):
http://builds.carrot2.org/browse/RNDTEST-MASTER-JOB1-109/log
Failing build (mvn clean deploy):
http://builds.carrot2.org/browse/RNDTEST-MASTER-JOB1-108/log
Passing build's invoker install section:
{noformat}
22-Jan-2012 11:31:03[INFO] --- maven-invoker-plugin:1.5:install
(integration-test) @ junit4-maven-plugin-tests ---
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-runner/0.0.5-SNAPSHOT/randomizedtesting-runner-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/target/randomizedtesting-runner-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-runner/0.0.5-SNAPSHOT/randomizedtesting-runner-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/pom.xml to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-parent/0.0.5-SNAPSHOT/randomizedtesting-parent-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin/0.0.5-SNAPSHOT/junit4-maven-plugin-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin/target/junit4-maven-plugin-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin/0.0.5-SNAPSHOT/junit4-maven-plugin-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-ant/ant-junit4/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/ant-junit4/0.0.5-SNAPSHOT/ant-junit4-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-ant/ant-junit4/target/ant-junit4-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/ant-junit4/0.0.5-SNAPSHOT/ant-junit4-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin-tests/0.0.5-SNAPSHOT/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin-tests/0.0.5-SNAPSHOT/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.jar
{noformat}
Failing build's invoker install section:
{noformat}
22-Jan-2012 11:26:32[INFO] --- maven-invoker-plugin:1.5:install
(integration-test) @ junit4-maven-plugin-tests ---
22-Jan-2012 11:26:33[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/pom.xml
to
/home/bamboo/b
[jira] (MINVOKER-107) mvn deploy of SNAPSHOT failed with maven3 when invoker:run look for current build dependency
[
https://jira.codehaus.org/browse/MINVOKER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289061#comment-289061
]
Dawid Weiss commented on MINVOKER-107:
--
This issue is a bug and is repeatable for me. The invoker plugin installs
shapshot versions of artefacts but this happens ONLY if running:
mvn clean deploy
and NOT if running:
mvn clean verify
So it is the deployment of artefacts that somehow renders -SNAPSHOT versions to
concrete numbered revisions. Build logs from our Bamboo where this is apparent:
Passing build (mvn clean verify):
http://builds.carrot2.org/browse/RNDTEST-MASTER-JOB1-109/log
Failing build (mvn clean deploy):
http://builds.carrot2.org/browse/RNDTEST-MASTER-JOB1-108/log
Passing build's invoker install section:
{noformat}
22-Jan-2012 11:31:03[INFO] --- maven-invoker-plugin:1.5:install
(integration-test) @ junit4-maven-plugin-tests ---
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-runner/0.0.5-SNAPSHOT/randomizedtesting-runner-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/target/randomizedtesting-runner-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-runner/0.0.5-SNAPSHOT/randomizedtesting-runner-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/pom.xml to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/randomizedtesting-parent/0.0.5-SNAPSHOT/randomizedtesting-parent-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin/0.0.5-SNAPSHOT/junit4-maven-plugin-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin/target/junit4-maven-plugin-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin/0.0.5-SNAPSHOT/junit4-maven-plugin-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-ant/ant-junit4/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/ant-junit4/0.0.5-SNAPSHOT/ant-junit4-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-ant/ant-junit4/target/ant-junit4-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/ant-junit4/0.0.5-SNAPSHOT/ant-junit4-0.0.5-SNAPSHOT.jar
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin-tests/0.0.5-SNAPSHOT/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.pom
22-Jan-2012 11:31:04[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.jar
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugin-tests/target/local-repo/com/carrotsearch/randomizedtesting/junit4-maven-plugin-tests/0.0.5-SNAPSHOT/junit4-maven-plugin-tests-0.0.5-SNAPSHOT.jar
{noformat}
Failing build's invoker install section:
{noformat}
22-Jan-2012 11:26:32[INFO] --- maven-invoker-plugin:1.5:install
(integration-test) @ junit4-maven-plugin-tests ---
22-Jan-2012 11:26:33[INFO] Installing
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/runner/pom.xml
to
/home/bamboo/bamboo3-work/xml-data/build-dir/RNDTEST-MASTER-JOB1/integration-maven/junit4-maven-plugi
