[jira] (MRELEASE-808) prepare-with-pom needs to be run twice when contains ${project.version}
[
https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315108#comment-315108
]
Darryl L. Miles commented on MRELEASE-808:
--
Test might succeed but does it relate to the problem ?
I have been using 2.3.2 also scm:git: also shouldn't the output version be
0.0.1, shouldn't the output effective pom.xml not include any ${variables} ?
Indeed this is the nature of the problem, the in memory model of the pom.xml is
copied the project.version changed and the variables not reinterpreted.
What is most important is if the plugin works for real (certainly for the
source tree my commit is based on '55dcd08' it did not work for real). So
before my patch is doesn't work after my patch it does work, this has been
tested by me.
I shall see if I can update and run your new test and then try each of these
these things. But I suspect the new test does not touch the problem. Maybe
that is why it passes without needing my patch.
> prepare-with-pom needs to be run twice when contains
> ${project.version}
> ---
>
> Key: MRELEASE-808
> URL: https://jira.codehaus.org/browse/MRELEASE-808
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
> Attachments:
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
>
>
> Setup your project with a element setup like:
> ${project.groupId}.${project.artifactId}-${project.version}
> Setup ${project.version} to a SNAPSHOT like:
> 0.0.1-SNAPSHOT
> The key thing here is the use of ${project.version} in the and ew
> start with a SNAPSHOT version trying to perform a release.
> Now we run: mvn release:prepare-with-pom
> It will bail out with error now and a message ... "Cannot reliably adjust the
> finalName of project:" and I believe this is due to the -SNAPSHOT being
> visible and the code that throw the exception is looking at the original,
> unedited version of the pom.xml.
> I think after editing the pom.xml the in-memory model should be refreshed and
> all ${variable} be re-interpreted.
--
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-808) prepare-with-pom needs to be run twice when contains ${project.version}
[
https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315112#comment-315112
]
Darryl L. Miles commented on MRELEASE-808:
--
Your change has not showed up in git at http://git.apache.org/maven-scm.git
yet. Until it does I can not begin testing (as I lost patience for SVN
sometime ago :) and will only use it when paid to do so)
> prepare-with-pom needs to be run twice when contains
> ${project.version}
> ---
>
> Key: MRELEASE-808
> URL: https://jira.codehaus.org/browse/MRELEASE-808
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
> Attachments:
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
>
>
> Setup your project with a element setup like:
> ${project.groupId}.${project.artifactId}-${project.version}
> Setup ${project.version} to a SNAPSHOT like:
> 0.0.1-SNAPSHOT
> The key thing here is the use of ${project.version} in the and ew
> start with a SNAPSHOT version trying to perform a release.
> Now we run: mvn release:prepare-with-pom
> It will bail out with error now and a message ... "Cannot reliably adjust the
> finalName of project:" and I believe this is due to the -SNAPSHOT being
> visible and the code that throw the exception is looking at the original,
> unedited version of the pom.xml.
> I think after editing the pom.xml the in-memory model should be refreshed and
> all ${variable} be re-interpreted.
--
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-808) prepare-with-pom needs to be run twice when contains ${project.version}
[
https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315113#comment-315113
]
Kristian Rosenvold commented on MRELEASE-808:
-
Maybe you will see it if you use the canonical git repo at
https://git-wip-us.apache.org/repos/asf/maven-scm.git
> prepare-with-pom needs to be run twice when contains
> ${project.version}
> ---
>
> Key: MRELEASE-808
> URL: https://jira.codehaus.org/browse/MRELEASE-808
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
> Attachments:
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
>
>
> Setup your project with a element setup like:
> ${project.groupId}.${project.artifactId}-${project.version}
> Setup ${project.version} to a SNAPSHOT like:
> 0.0.1-SNAPSHOT
> The key thing here is the use of ${project.version} in the and ew
> start with a SNAPSHOT version trying to perform a release.
> Now we run: mvn release:prepare-with-pom
> It will bail out with error now and a message ... "Cannot reliably adjust the
> finalName of project:" and I believe this is due to the -SNAPSHOT being
> visible and the code that throw the exception is looking at the original,
> unedited version of the pom.xml.
> I think after editing the pom.xml the in-memory model should be refreshed and
> all ${variable} be re-interpreted.
--
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] (MPIR-260) No translation for report.dependency-info.* in several resource bundles
Anders Hammar created MPIR-260: -- Summary: No translation for report.dependency-info.* in several resource bundles Key: MPIR-260 URL: https://jira.codehaus.org/browse/MPIR-260 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: dependency-info Affects Versions: 2.5 Environment: n/a Reporter: Anders Hammar Priority: Minor Need to add the report.dependency-info.* props in several of the resource bundles: * de * cs * es * gl * hu * it (lacking several other props as well) * ja * ko * lt * nl (lacking several other props as well) * no * pl (lacking some others as well) * pt_BR * pt * ru * sk * sv * tr * zh_CN * zh_TW We should try to fix as many as possible. -- 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] (MPIR-260) No translation for report.dependency-info.* in several resource bundles
[ https://jira.codehaus.org/browse/MPIR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MPIR-260: --- Description: Need to add the report.dependency-info.* props in several of the resource bundles: * de * cs * es * gl * hu * it (lacking several other props as well) * ja * ko * lt * nl (lacking several other props as well) * no * pl (lacking some others as well) * pt_BR * pt * ru * sk * sv * tr * zh_CN * zh_TW It's these props: report.dependency-info.name report.dependency-info.title report.dependency-info.description was: Need to add the report.dependency-info.* props in several of the resource bundles: * de * cs * es * gl * hu * it (lacking several other props as well) * ja * ko * lt * nl (lacking several other props as well) * no * pl (lacking some others as well) * pt_BR * pt * ru * sk * sv * tr * zh_CN * zh_TW We should try to fix as many as possible. > No translation for report.dependency-info.* in several resource bundles > --- > > Key: MPIR-260 > URL: https://jira.codehaus.org/browse/MPIR-260 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependency-info >Affects Versions: 2.5 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > > Need to add the report.dependency-info.* props in several of the resource > bundles: > * de > * cs > * es > * gl > * hu > * it (lacking several other props as well) > * ja > * ko > * lt > * nl (lacking several other props as well) > * no > * pl (lacking some others as well) > * pt_BR > * pt > * ru > * sk > * sv > * tr > * zh_CN > * zh_TW > It's these props: > report.dependency-info.name > report.dependency-info.title > report.dependency-info.description -- 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] (MPIR-261) Wrong URL for Hudson home page in resource bundles
Anders Hammar created MPIR-261: -- Summary: Wrong URL for Hudson home page in resource bundles Key: MPIR-261 URL: https://jira.codehaus.org/browse/MPIR-261 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Components: cim Affects Versions: 2.6 Environment: n/a Reporter: Anders Hammar Priority: Trivial For the 'report.cim.jenkins.intro' prop the URL to the homepage for the Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It should be 'http://hudson-ci.org/'. -- 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] (MPIR-261) Wrong URL for Hudson home page in resource bundles
[ https://jira.codehaus.org/browse/MPIR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reassigned MPIR-261: -- Assignee: Anders Hammar > Wrong URL for Hudson home page in resource bundles > -- > > Key: MPIR-261 > URL: https://jira.codehaus.org/browse/MPIR-261 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: cim >Affects Versions: 2.6 > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar >Priority: Trivial > > For the 'report.cim.jenkins.intro' prop the URL to the homepage for the > Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It > should be 'http://hudson-ci.org/'. -- 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] (MPIR-261) Wrong URL for some CI home pages in resource bundles
[ https://jira.codehaus.org/browse/MPIR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar updated MPIR-261: --- Description: For the 'report.cim.jenkins.intro' prop the URL to the homepage for the Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It should be 'http://hudson-ci.org/'. Also, the URL for Continuum is wrong. was:For the 'report.cim.jenkins.intro' prop the URL to the homepage for the Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It should be 'http://hudson-ci.org/'. Summary: Wrong URL for some CI home pages in resource bundles (was: Wrong URL for Hudson home page in resource bundles) > Wrong URL for some CI home pages in resource bundles > > > Key: MPIR-261 > URL: https://jira.codehaus.org/browse/MPIR-261 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: cim >Affects Versions: 2.6 > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar >Priority: Trivial > > For the 'report.cim.jenkins.intro' prop the URL to the homepage for the > Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It > should be 'http://hudson-ci.org/'. > Also, the URL for Continuum is wrong. -- 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] (MPIR-261) Wrong URL for some CI home pages in resource bundles
[ https://jira.codehaus.org/browse/MPIR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar closed MPIR-261. -- Resolution: Fixed Fix Version/s: 2.7 Fixed in [r1417883|http://fisheye.codehaus.org/changelog/mojo/?cs=1417883] > Wrong URL for some CI home pages in resource bundles > > > Key: MPIR-261 > URL: https://jira.codehaus.org/browse/MPIR-261 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: cim >Affects Versions: 2.6 > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar >Priority: Trivial > Fix For: 2.7 > > > For the 'report.cim.jenkins.intro' prop the URL to the homepage for the > Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It > should be 'http://hudson-ci.org/'. > Also, the URL for Continuum is wrong. -- 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] (MPIR-260) No translation for report.dependency-info.* in several resource bundles
[ https://jira.codehaus.org/browse/MPIR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315116#comment-315116 ] Anders Hammar commented on MPIR-260: Swedish translation added in [r1417886|http://fisheye.codehaus.org/changelog/mojo/?cs=1417886] > No translation for report.dependency-info.* in several resource bundles > --- > > Key: MPIR-260 > URL: https://jira.codehaus.org/browse/MPIR-260 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependency-info >Affects Versions: 2.5 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > > Need to add the report.dependency-info.* props in several of the resource > bundles: > * de > * cs > * es > * gl > * hu > * it (lacking several other props as well) > * ja > * ko > * lt > * nl (lacking several other props as well) > * no > * pl (lacking some others as well) > * pt_BR > * pt > * ru > * sk > * sv > * tr > * zh_CN > * zh_TW > It's these props: > report.dependency-info.name > report.dependency-info.title > report.dependency-info.description -- 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] (MPIR-262) Add support for 'report.cim.bamboo.intro' resource property
Anders Hammar created MPIR-262: -- Summary: Add support for 'report.cim.bamboo.intro' resource property Key: MPIR-262 URL: https://jira.codehaus.org/browse/MPIR-262 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: cim Affects Versions: 2.6 Environment: n/a Reporter: Anders Hammar Priority: Minor There is no specific property for Bamboo as there is for many other CIs. Add support for 'report.cim.bamboo.intro'. -- 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] (MPIR-262) Add support for 'report.cim.bamboo.intro' resource property
[ https://jira.codehaus.org/browse/MPIR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar closed MPIR-262. -- Resolution: Fixed Fix Version/s: 2.7 Assignee: Anders Hammar Fixed in [r1417917|http://svn.apache.org/r1417917] > Add support for 'report.cim.bamboo.intro' resource property > --- > > Key: MPIR-262 > URL: https://jira.codehaus.org/browse/MPIR-262 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: cim >Affects Versions: 2.6 > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar >Priority: Minor > Fix For: 2.7 > > > There is no specific property for Bamboo as there is for many other CIs. Add > support for 'report.cim.bamboo.intro'. -- 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] (MPIR-260) No translation for report.dependency-info.* in several resource bundles
[ https://jira.codehaus.org/browse/MPIR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315116#comment-315116 ] Anders Hammar edited comment on MPIR-260 at 12/6/12 8:37 AM: - Swedish translation added in [r1417886|http://svn.apache.org/r1417886] was (Author: afloom): Swedish translation added in [r1417886|http://fisheye.codehaus.org/changelog/mojo/?cs=1417886] > No translation for report.dependency-info.* in several resource bundles > --- > > Key: MPIR-260 > URL: https://jira.codehaus.org/browse/MPIR-260 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependency-info >Affects Versions: 2.5 > Environment: n/a >Reporter: Anders Hammar >Priority: Minor > > Need to add the report.dependency-info.* props in several of the resource > bundles: > * de > * cs > * es > * gl > * hu > * it (lacking several other props as well) > * ja > * ko > * lt > * nl (lacking several other props as well) > * no > * pl (lacking some others as well) > * pt_BR > * pt > * ru > * sk > * sv > * tr > * zh_CN > * zh_TW > It's these props: > report.dependency-info.name > report.dependency-info.title > report.dependency-info.description -- 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] (MPIR-261) Wrong URL for some CI home pages in resource bundles
[ https://jira.codehaus.org/browse/MPIR-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315115#comment-315115 ] Anders Hammar edited comment on MPIR-261 at 12/6/12 8:36 AM: - Fixed in [r1417883|http://svn.apache.org/r1417883] was (Author: afloom): Fixed in [r1417883|http://fisheye.codehaus.org/changelog/mojo/?cs=1417883] > Wrong URL for some CI home pages in resource bundles > > > Key: MPIR-261 > URL: https://jira.codehaus.org/browse/MPIR-261 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: cim >Affects Versions: 2.6 > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar >Priority: Trivial > Fix For: 2.7 > > > For the 'report.cim.jenkins.intro' prop the URL to the homepage for the > Hudson project is incorrectly stated as 'https://hudson.dev.java.net/'. It > should be 'http://hudson-ci.org/'. > Also, the URL for Continuum is wrong. -- 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-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
Karl Heinz Marbaise created MINVOKER-147:
Summary: setupIncludes / parallelThreads does not guarantee
execution of setup*/pom.xml first.
Key: MINVOKER-147
URL: https://jira.codehaus.org/browse/MINVOKER-147
Project: Maven 2.x Invoker Plugin
Issue Type: Bug
Affects Versions: 1.8
Environment: All.
Reporter: Karl Heinz Marbaise
Priority: Critical
I've setup an integration test for a maven plugin. I have configured the
maven-invoker-plugin like the following:
{code}
org.apache.maven.plugins
maven-invoker-plugin
org.codehaus.groovy
groovy
${org.codehaus.groovy-groovy.version}
org.codehaus.gmaven.runtime
gmaven-runtime-1.8
${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
true
false
${project.build.directory}/local-repo
${project.build.directory}/it
src/it
true
*/pom.xml
setup
verify
src/it/settings.xml
1
integration-tests
install
run
{code}
I have a setup-config/pom.xml project which must be installed before any other
tests which seemed to be working with the above configuration.
But I would like to use the parallelThreads with for example 3 or 4 the result
is that the build fails, cause the setup-config/pom.xml project is not running
before any other integration.
This gives the hint that it is not guaranteed that the setup-*/pom.xml project
will be running before other integration tests.
In my opinion the setup-*/pom.xml project must be started first with the
appropriate threads afterwards the other integration tests must be started
within a second step.
--
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-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315135#comment-315135
]
Karl Heinz Marbaise commented on MINVOKER-147:
--
An output of the wrong behaviour:
{code}
...
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ configurator-maven-plugin
---
[INFO] Building jar:
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ configurator-maven-plugin ---
[INFO]
[INFO] --- maven-invoker-plugin:1.8:install (integration-tests) @
configurator-maven-plugin ---
[INFO] Installing d:\ws\maven-configurator-plugin\pom.xml to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.pom
[INFO] Installing
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-invoker-plugin:1.8:run (integration-tests) @
configurator-maven-plugin ---
[INFO] use parallelThreads 4
[INFO] Building: basicTest\pom.xml
[INFO] Building: configurationViaClassPathTest\pom.xml
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] Building: setup-config\pom.xml
[INFO] run script verify.groovy
[INFO] ..FAILED (3.8 s)
[INFO] The post-build script did not succeed. The expected content in
d:\ws\maven-configurator-plugin\target\it\basicTest\build.log couldn't be
found.[ERROR] Failed to execute goal
com.hrs.maven.plugins:configurator-maven-plugin:0.1.0-SNAPSHOT:configurator
(default) on project basic-test: The parameters 'resources' for goal
com.hrs.maven.plugins:configurator-maven-plugin:0.1.0-SNAPSHOT:configurator are
missing or invalid -> [Help 1]
[INFO] Building: simpleReplacementTest\pom.xml
[INFO] ..FAILED (8.4 s)
[INFO] The build exited with code 1. See
d:\ws\maven-configurator-plugin\target\it\configurationViaClassPathTest\build.log
for details.
[INFO] run script verify.groovy
[INFO] ..SUCCESS (9.1 s)
[INFO] run script verify.groovy
[INFO] ..SUCCESS (6.1 s)
Project version: 0.1.0-SNAPSHOT
..
{code}
In this scenario the setup-config is started in parallel with others which
can't be working.
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://ji
[jira] (MINVOKER-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315136#comment-315136
]
Anders Hammar commented on MINVOKER-147:
You should use 'setupIncludes':
http://maven.apache.org/plugins/maven-invoker-plugin/examples/prepare-build-env.html
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
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-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Hammar updated MINVOKER-147:
---
Priority: Major (was: Critical)
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
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-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315138#comment-315138
]
Karl Heinz Marbaise commented on MINVOKER-147:
--
The same scenario as above with parallelThreads set to 1 (default).
{code}
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ configurator-maven-plugin
---
[INFO] Building jar:
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ configurator-maven-plugin ---
[INFO]
[INFO] --- maven-invoker-plugin:1.8:install (integration-tests) @
configurator-maven-plugin ---
[INFO] Installing d:\ws\maven-configurator-plugin\pom.xml to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.pom
[INFO] Installing
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-invoker-plugin:1.8:run (integration-tests) @
configurator-maven-plugin ---
[INFO] Building: setup-config\pom.xml
[INFO] ..SUCCESS (2.9 s)
[INFO] Building: basicTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (3.4 s)
[INFO] Building: configurationViaClassPathTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (3.2 s)
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (2.5 s)
[INFO] Building: replacementInMultipleFilesTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (3.1 s)
[INFO] Building: simpleReplacementTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (3.1 s)
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 6, Failed: 0, Errors: 0, Skipped: 0
[INFO] -
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 27.045s
[INFO] Finished at: Thu Dec 06 15:59:08 CET 2012
[INFO] Final Memory: 31M/373M
[INFO]
{code}
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/
[jira] (MINVOKER-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315141#comment-315141
]
Karl Heinz Marbaise commented on MINVOKER-147:
--
The problem is that doc give the default value for setupIncludes
'setup*/pom.xml' which brings me to the conclusion that setting it explicit
shouldn't change anything. The following proves my assumption:
{code}
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ configurator-maven-plugin
---
[INFO] Building jar:
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ configurator-maven-plugin ---
[INFO]
[INFO] --- maven-invoker-plugin:1.8:install (integration-tests) @
configurator-maven-plugin ---
[INFO] Installing d:\ws\maven-configurator-plugin\pom.xml to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins
\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.pom
[INFO] Installing
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
to d:\ws\maven-configurator-pl
ugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-invoker-plugin:1.8:run (integration-tests) @
configurator-maven-plugin ---
[INFO] use parallelThreads 4
[INFO] Building: setup-config\pom.xml
[INFO] Building: basicTest\pom.xml
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] Building: configurationViaClassPathTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.9 s)
[INFO] Building: replacementInMultipleFilesTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (6.0 s)
[INFO] Building: simpleReplacementTest\pom.xml
[INFO] ..FAILED (6.4 s)
[INFO] The build exited with code 1. See
d:\ws\maven-configurator-plugin\target\it\setup-config\build.log for details.
[INFO] ..FAILED (6.4 s)
[INFO] The build exited with code 1. See
d:\ws\maven-configurator-plugin\target\it\configurationViaClassPathTest\build.log
for det
ails.
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.1 s)
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.3 s)
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 4, Failed: 2, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * setup-config\pom.xml
[ERROR] * configurationViaClassPathTest\pom.xml
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.240s
[INFO] Finished at: Thu Dec 06 16:08:46 CET 2012
[INFO] Final Memory: 31M/373M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-tests) on
project configurator-mav
en-plugin: 2 builds failed. See console output above for details. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
The problem in my opinion is based on the block of projects which will be
started in parallel:
{code}
[INFO] use parallelThreads 4
[INFO] Building: setup-config\pom.xml
[INFO] Building: basicTest\pom.xml
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] Building: configurationViaClassPathTest\pom.xml
{code}
which could never working. To be sure to run the setup*/pom.xml projects first
it must be executed in a separate step. The order of the setup*/pom.xml jobs
isn't guaranteed.
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.
[jira] (MINVOKER-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315141#comment-315141
]
Karl Heinz Marbaise edited comment on MINVOKER-147 at 12/6/12 9:14 AM:
---
The problem is that doc give the default value for setupIncludes
'setup*/pom.xml' which brings me to the conclusion that setting it explicit
shouldn't change anything. The following proves my assumption:
{code}
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ configurator-maven-plugin
---
[INFO] Building jar:
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ configurator-maven-plugin ---
[INFO]
[INFO] --- maven-invoker-plugin:1.8:install (integration-tests) @
configurator-maven-plugin ---
[INFO] Installing d:\ws\maven-configurator-plugin\pom.xml to
d:\ws\maven-configurator-plugin\target\local-repo\com\hrs\maven\plugins
\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.pom
[INFO] Installing
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
to d:\ws\maven-configurator-pl
ugin\target\local-repo\com\hrs\maven\plugins\configurator-maven-plugin\0.1.0-SNAPSHOT\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-invoker-plugin:1.8:run (integration-tests) @
configurator-maven-plugin ---
[INFO] use parallelThreads 4
[INFO] Building: setup-config\pom.xml
[INFO] Building: basicTest\pom.xml
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] Building: configurationViaClassPathTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.9 s)
[INFO] Building: replacementInMultipleFilesTest\pom.xml
[INFO] run script verify.groovy
[INFO] ..SUCCESS (6.0 s)
[INFO] Building: simpleReplacementTest\pom.xml
[INFO] ..FAILED (6.4 s)
[INFO] The build exited with code 1. See
d:\ws\maven-configurator-plugin\target\it\setup-config\build.log for details.
[INFO] ..FAILED (6.4 s)
[INFO] The build exited with code 1. See
d:\ws\maven-configurator-plugin\target\it\configurationViaClassPathTest\build.log
for det
ails.
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.1 s)
[INFO] run script verify.groovy
[INFO] ..SUCCESS (4.3 s)
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 4, Failed: 2, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * setup-config\pom.xml
[ERROR] * configurationViaClassPathTest\pom.xml
[INFO] -
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 19.240s
[INFO] Finished at: Thu Dec 06 16:08:46 CET 2012
[INFO] Final Memory: 31M/373M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-tests) on
project configurator-mav
en-plugin: 2 builds failed. See console output above for details. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
The problem in my opinion is based on the block of projects which will be
started in parallel:
{code}
[INFO] use parallelThreads 4
[INFO] Building: setup-config\pom.xml
[INFO] Building: basicTest\pom.xml
[INFO] Building: missingConfigurationTest\pom.xml
[INFO] Building: configurationViaClassPathTest\pom.xml
{code}
which could never work. To be sure to run the setup*/pom.xml projects first it
must be executed in a separate step. The order of the setup*/pom.xml jobs isn't
guaranteed.
was (Author: khmarbaise):
The problem is that doc give the default value for setupIncludes
'setup*/pom.xml' which brings me to the conclusion that setting it explicit
shouldn't change anything. The following proves my assumption:
{code}
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ configurator-maven-plugin
---
[INFO] Building jar:
d:\ws\maven-configurator-plugin\target\configurator-maven-plugin-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-plugin-plugin:3.2:addPluginArtifactMetadata
(default-addPluginArtifactMetadata) @ configurator-maven-plugin ---
[INFO]
[INFO] --- maven-invoker-plugin:1.8:install (integration-tests) @
configurator-maven-plugin ---
[INFO] Installing d:\ws\maven-configurator-plugin\pom.xml to
d:\ws\maven-configura
[jira] (MINVOKER-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315145#comment-315145
]
Anders Hammar commented on MINVOKER-147:
Ok, might be a bug then.
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
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-147) setupIncludes / parallelThreads does not guarantee execution of setup*/pom.xml first.
[
https://jira.codehaus.org/browse/MINVOKER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315152#comment-315152
]
Karl Heinz Marbaise commented on MINVOKER-147:
--
Taken a look into the source code and in my opinion the problem is based on the
method
[getBuildJobs()|http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-invoker-plugin/src/main/java/org/apache/maven/plugin/invoker/AbstractInvokerMojo.java]
which correctly defines the order of jobs but will give the jobs as a single
result which can't be ok. There must be a separate call or better a
parameterized call of getBuildJobs(setupIncludes) first and second the
getBuildJobs(pomIncludes) and running the first one and afterwards the seconds
to be sure the setupIncludes will run first.
> setupIncludes / parallelThreads does not guarantee execution of
> setup*/pom.xml first.
> -
>
> Key: MINVOKER-147
> URL: https://jira.codehaus.org/browse/MINVOKER-147
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: All.
>Reporter: Karl Heinz Marbaise
>
> I've setup an integration test for a maven plugin. I have configured the
> maven-invoker-plugin like the following:
> {code}
>
> org.apache.maven.plugins
> maven-invoker-plugin
>
>
> org.codehaus.groovy
> groovy
> ${org.codehaus.groovy-groovy.version}
>
>
> org.codehaus.gmaven.runtime
> gmaven-runtime-1.8
>
> ${org.codehaus.gmaven.runtime-gmaven-runtime-1.8}
>
>
>
> true
> false
>
> ${project.build.directory}/local-repo
> ${project.build.directory}/it
> src/it
> true
>
> */pom.xml
>
> setup
> verify
> src/it/settings.xml
> 1
>
>
>
> integration-tests
>
> install
> run
>
>
>
>
>
> {code}
> I have a setup-config/pom.xml project which must be installed before any
> other tests which seemed to be working with the above configuration.
> But I would like to use the parallelThreads with for example 3 or 4 the
> result is that the build fails, cause the setup-config/pom.xml project is not
> running before any other integration.
> This gives the hint that it is not guaranteed that the setup-*/pom.xml
> project will be running before other integration tests.
> In my opinion the setup-*/pom.xml project must be started first with the
> appropriate threads afterwards the other integration tests must be started
> within a second step.
--
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-808) prepare-with-pom needs to be run twice when contains ${project.version}
[
https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Miles updated MRELEASE-808:
-
Attachment: 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
UPDATED PATCH
This replaces the existing patch.
Patch against GIT tree maven-release.git trunk 55dcd08
This add checking/protection from other use since the previous version pf the
patch, this version protects against cases where projectVersion="1" and
releaseVersion="2" this is why it was considered unsafe before.
The most ideal patch would be to have the newly constructed MavenProject model
in memory go back to the original ${variable} and reinterpret the variable in
the context of the new in-memory model and then set the finalName field to the
new value.
But for now this patch fixes the problem for me and should provide protection
against editing the value incorrectly in other cases.
> prepare-with-pom needs to be run twice when contains
> ${project.version}
> ---
>
> Key: MRELEASE-808
> URL: https://jira.codehaus.org/browse/MRELEASE-808
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
> Attachments:
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch,
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
>
>
> Setup your project with a element setup like:
> ${project.groupId}.${project.artifactId}-${project.version}
> Setup ${project.version} to a SNAPSHOT like:
> 0.0.1-SNAPSHOT
> The key thing here is the use of ${project.version} in the and ew
> start with a SNAPSHOT version trying to perform a release.
> Now we run: mvn release:prepare-with-pom
> It will bail out with error now and a message ... "Cannot reliably adjust the
> finalName of project:" and I believe this is due to the -SNAPSHOT being
> visible and the code that throw the exception is looking at the original,
> unedited version of the pom.xml.
> I think after editing the pom.xml the in-memory model should be refreshed and
> all ${variable} be re-interpreted.
--
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-808) prepare-with-pom needs to be run twice when contains ${project.version}
[
https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315155#comment-315155
]
Darryl L. Miles commented on MRELEASE-808:
--
I can confirm that testing with the unit test (this PASSES) but without any
version of my patch fails to process a real release run with the following
command line:
mvn -X -DignoreSnapshots=true release:prepare-with-pom
With my patch it works as expected with 2 new commits generated with correct
information.
The reason for using -DignoreSnapshots=true is because I am using the version
of the plugin and its dependency from my local M2 repository with the following
configuration:
org.apache.maven.plugins
maven-release-plugin
2.4-SNAPSHOT
org.apache.maven.scm
maven-scm-providers-standard
1.9-SNAPSHOT
pom
org.apache.maven.scm
maven-scm-provider-gitexe
1.9-SNAPSHOT
org.apache.maven.scm
maven-scm-api
1.9-SNAPSHOT
org.apache.maven.release
maven-release-manager
2.4-SNAPSHOT
> prepare-with-pom needs to be run twice when contains
> ${project.version}
> ---
>
> Key: MRELEASE-808
> URL: https://jira.codehaus.org/browse/MRELEASE-808
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
> Attachments:
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch,
> 0001-MRELEASE-808-Allow-fixup-of-SNAPSHOT-version-in-fina.patch
>
>
> Setup your project with a element setup like:
> ${project.groupId}.${project.artifactId}-${project.version}
> Setup ${project.version} to a SNAPSHOT like:
> 0.0.1-SNAPSHOT
> The key thing here is the use of ${project.version} in the and ew
> start with a SNAPSHOT version trying to perform a release.
> Now we run: mvn release:prepare-with-pom
> It will bail out with error now and a message ... "Cannot reliably adjust the
> finalName of project:" and I believe this is due to the -SNAPSHOT being
> visible and the code that throw the exception is looking at the original,
> unedited version of the pom.xml.
> I think after editing the pom.xml the in-memory model should be refreshed and
> all ${variable} be re-interpreted.
--
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-746) SCM URL being mangled
[
https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315156#comment-315156
]
Darryl L. Miles commented on MRELEASE-746:
--
So you are saying this is a problem with beanstalk ? and this ticket can be
closed as not a bug in Maven ?
> SCM URL being mangled
> -
>
> Key: MRELEASE-746
> URL: https://jira.codehaus.org/browse/MRELEASE-746
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2
> Environment: Windows 7 SP1, Java SDK 1.6.0_03, Maven 3.0.4
>Reporter: Logan McGrath
>Assignee: Mark Struberg
>
> When performing {{mvn release:prepare}}, the plugin is removing colons from
> my GIT URL. My project is hosted on Beanstalk.
> Here's the [redacted] URL specified in the POM's SCM element:
> git@[account].beanstalkapp.com:/[project].git
> Here's the [redacted] URL the plugin ends up using:
> git@[account].beanstalkapp.com/[project].git
> Notice the missing colon.
> The specific error I get using {{mvn release:prepare}} is:
> {noformat}
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear
> to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> {noformat}
> Running the command {{mvn release:prepare -X}} gives me:
> Command output:
> {noformat}
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit
> files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:310)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException:
> Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> fatal: 'git@[account].beanstalkapp.com/[project].git' does not appear to be a
> git repository
> fatal: The remote end hung up unexpectedly
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168)
> at
> org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148)
> at
> org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.jav
[jira] (MRELEASE-809) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)
[ https://jira.codehaus.org/browse/MRELEASE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Miles updated MRELEASE-809: - Attachment: 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch Patch in git format against maven-scm.git master c96ca24 The code in the CheckIn operation the patch sources could be improved as it does two "git status --porcelain" during the check-in operation. Maybe these could merged into the 'git status' I now perform. This patch also make an API public this follows the same design as the Bazaar plugin uses. > prepare-with-pom deletes release-pom.xml then tries to git add it (presumably > so the next commit records the fact) > -- > > Key: MRELEASE-809 > URL: https://jira.codehaus.org/browse/MRELEASE-809 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.3.2 >Reporter: Darryl L. Miles > Attachments: > 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch > > > When running: git release:prepare-with-pom > After the tag is created and pushed, it then runs the sequence: > git rm release-pom.xml > git add -- pom.xml release-pom.xml > But the "git add" fails because the "git rm" did the action of removing the > actual file and adding the file removal fact to the cached index ready for > the next commit to pickup. > The solution is to remove the "release-pom.xml" argument from the "git add" > it is unnecessary. -- 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-809) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)
[ https://jira.codehaus.org/browse/MRELEASE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315157#comment-315157 ] Darryl L. Miles edited comment on MRELEASE-809 at 12/6/12 11:17 AM: Patch in git format against maven-scm.git master c96ca24 The code in the CheckIn operation the patch touches could be improved as it does two "git status --porcelain" during the check-in operation. Maybe these could merged into the 'git status' I now perform. This patch also make an API public this follows the same design as the Bazaar plugin uses. was (Author: dlmiles): Patch in git format against maven-scm.git master c96ca24 The code in the CheckIn operation the patch sources could be improved as it does two "git status --porcelain" during the check-in operation. Maybe these could merged into the 'git status' I now perform. This patch also make an API public this follows the same design as the Bazaar plugin uses. > prepare-with-pom deletes release-pom.xml then tries to git add it (presumably > so the next commit records the fact) > -- > > Key: MRELEASE-809 > URL: https://jira.codehaus.org/browse/MRELEASE-809 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.3.2 >Reporter: Darryl L. Miles > Attachments: > 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch > > > When running: git release:prepare-with-pom > After the tag is created and pushed, it then runs the sequence: > git rm release-pom.xml > git add -- pom.xml release-pom.xml > But the "git add" fails because the "git rm" did the action of removing the > actual file and adding the file removal fact to the cached index ready for > the next commit to pickup. > The solution is to remove the "release-pom.xml" argument from the "git add" > it is unnecessary. -- 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-809) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)
[ https://jira.codehaus.org/browse/MRELEASE-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315173#comment-315173 ] Darryl L. Miles commented on MRELEASE-809: -- Possible duplicate of MRELEASE-539 ??? But patch provided here. > prepare-with-pom deletes release-pom.xml then tries to git add it (presumably > so the next commit records the fact) > -- > > Key: MRELEASE-809 > URL: https://jira.codehaus.org/browse/MRELEASE-809 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.3.2 >Reporter: Darryl L. Miles > Attachments: > 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch > > > When running: git release:prepare-with-pom > After the tag is created and pushed, it then runs the sequence: > git rm release-pom.xml > git add -- pom.xml release-pom.xml > But the "git add" fails because the "git rm" did the action of removing the > actual file and adding the file removal fact to the cached index ready for > the next commit to pickup. > The solution is to remove the "release-pom.xml" argument from the "git add" > it is unnecessary. -- 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-539) prepare-with-pom fails for git provider
[
https://jira.codehaus.org/browse/MRELEASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315172#comment-315172
]
Darryl L. Miles commented on MRELEASE-539:
--
also reported in MRELEASE-809 with patch provided there.
> prepare-with-pom fails for git provider
> ---
>
> Key: MRELEASE-539
> URL: https://jira.codehaus.org/browse/MRELEASE-539
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: Git, prepare-with-pom
>Affects Versions: 2.0
>Reporter: Maarten Billemont
>
> When running the release-with-pom goal; toward the end, the release-poms are
> deleted and this change is committed. Unfortunately, with the GIT provider,
> this is done by first git rm'ing the files and then git add'ing them
> (presumably, to add the rm change to the index). The latter fails because
> the files are no longer present.
> {code}
> [INFO] Executing: /bin/sh -c cd /Users/lhunath/work/git && git rm
> release-pom.xml d/release-pom.xml c/release-pom.xml e/release-pom.xml
> [INFO] Working directory: /Users/lhunath/work/git
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /Users/lhunath/work/git && git add -- pom.xml
> release-pom.xml d/pom.xml d/release-pom.xml c/pom.xml c/release-pom.xml
> e/pom.xml e/release-pom.xml
> [INFO] Working directory: /Users/lhunath/work/git
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to commit files
> Provider message:
> The git-add command failed.
> Command output:
> fatal: pathspec 'release-pom.xml' did not match any files
> {code}
--
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-801) Wrong value of element from branch
[ https://jira.codehaus.org/browse/MRELEASE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Miles updated MRELEASE-801: - Attachment: 0001-MRELEASE-801-don-t-use-scm.tag-HEAD-for-GIT-provider.patch Patch to GIT maven-release.git trunk a603d07 This patch copies what CVS does in the situation. > Wrong value of element from branch > > > Key: MRELEASE-801 > URL: https://jira.codehaus.org/browse/MRELEASE-801 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: branch, Git >Affects Versions: 2.3.2 >Reporter: Benson Margulies > Attachments: > 0001-MRELEASE-801-don-t-use-scm.tag-HEAD-for-GIT-provider.patch > > > The branch mojo produces HEAD. This can't be right; HEAD isn't the > name of a branch, it's the name of a ref. -- 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] (SCM-706) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)
[ https://jira.codehaus.org/browse/SCM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-809 to SCM-706: - Complexity: Intermediate Component/s: (was: Git) maven-scm-provider-git Affects Version/s: (was: 2.3.2) 1.8.1 Key: SCM-706 (was: MRELEASE-809) Project: Maven SCM (was: Maven 2.x Release Plugin) > prepare-with-pom deletes release-pom.xml then tries to git add it (presumably > so the next commit records the fact) > -- > > Key: SCM-706 > URL: https://jira.codehaus.org/browse/SCM-706 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.8.1 >Reporter: Darryl L. Miles > Attachments: > 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch > > > When running: git release:prepare-with-pom > After the tag is created and pushed, it then runs the sequence: > git rm release-pom.xml > git add -- pom.xml release-pom.xml > But the "git add" fails because the "git rm" did the action of removing the > actual file and adding the file removal fact to the cached index ready for > the next commit to pickup. > The solution is to remove the "release-pom.xml" argument from the "git add" > it is unnecessary. -- 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] (MINSTALL-82) Add sha 256 support
[ https://jira.codehaus.org/browse/MINSTALL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315179#comment-315179 ] John Dyer commented on MINSTALL-82: --- This would be GREAT! > Add sha 256 support > --- > > Key: MINSTALL-82 > URL: https://jira.codehaus.org/browse/MINSTALL-82 > Project: Maven 2.x Install Plugin > Issue Type: New Feature > Components: install:install >Affects Versions: 2.3.1 >Reporter: Todd Nine > Attachments: sha256.patch > > > Currently no facility for sha 256 exists in the install plugin. Utilities > such as chef depend on sha 256 to validate downloaded files. I have added > the functionality to the plugin. Node that my 2 plexus classes are not > properly loaded and I have hard coded the sha256 implementation. I'm > unfamiliar with plexus, but all the classes should be correct to submit to > the digest utilities. > Thanks, > Todd -- 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-810) When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
Darryl L. Miles created MRELEASE-810:
Summary: When running ScmCommitDevelopmentPhase the wrong version
is presented to the commit log
Key: MRELEASE-810
URL: https://jira.codehaus.org/browse/MRELEASE-810
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Reporter: Darryl L. Miles
Priority: Minor
When running ScmCommitDevelopmentPhase the wrong version is presented to the
commit log
When trying to get the default new development commit message to read:
[maven-release-plugin] prepare for next development iteration 0.0.2-SNAPSHOT
The default message does not use {0} even though a parameter is presented. I
suspect {0} was not used as it was the wrong version number and no one bothered
to fix it.
--
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] (MDEP-187) dependency:copy fails when invoked from m2e with workspace resolution enabled, or more generally when copying within reactor for phases earlier than package
[ https://jira.codehaus.org/browse/MDEP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEP-187: --- Summary: dependency:copy fails when invoked from m2e with workspace resolution enabled, or more generally when copying within reactor for phases earlier than package (was: dependency:copy fails when invoked from m2e with workspace resolution enabled) > dependency:copy fails when invoked from m2e with workspace resolution > enabled, or more generally when copying within reactor for phases earlier > than package > > > Key: MDEP-187 > URL: https://jira.codehaus.org/browse/MDEP-187 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy, copy-dependencies >Affects Versions: 2.1 >Reporter: Igor Fedorenko > Attachments: MDEP-187b.diff, MDEP-187c.diff, MDEP-187.diff > > > m2e resolves workspace artifacts to their output folders but dependency:copy > expects all artifacts to be files. I will provide trivial patch shortly. -- 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-810) When running ScmCommitDevelopmentPhase the wrong version is presented to the commit log
[
https://jira.codehaus.org/browse/MRELEASE-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Miles updated MRELEASE-810:
-
Attachment: 0001-MRELEASE-810-ScmCommitDevelopmentPhase-include-SNAPS.patch
Patch on git tree maven-release.git trunk a603d07
> When running ScmCommitDevelopmentPhase the wrong version is presented to the
> commit log
> ---
>
> Key: MRELEASE-810
> URL: https://jira.codehaus.org/browse/MRELEASE-810
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
>Reporter: Darryl L. Miles
>Priority: Minor
> Attachments:
> 0001-MRELEASE-810-ScmCommitDevelopmentPhase-include-SNAPS.patch
>
>
> When running ScmCommitDevelopmentPhase the wrong version is presented to the
> commit log
> When trying to get the default new development commit message to read:
> [maven-release-plugin] prepare for next development iteration 0.0.2-SNAPSHOT
> The default message does not use {0} even though a parameter is presented. I
> suspect {0} was not used as it was the wrong version number and no one
> bothered to fix it.
--
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
