[jira] (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-459. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in [r1391992|http://svn.apache.org/viewvc?rev=1391992&view=rev] > releaseProfiles has no effect without passing profiles in the command line > --- > > Key: MRELEASE-459 > URL: https://jira.codehaus.org/browse/MRELEASE-459 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.0-beta-8, 2.0-beta-9 >Reporter: Andreas Christoforides >Assignee: Robert Scholte > Labels: contributers-welcome, help-requested, > missing-integration-tests > Fix For: 2.4 > > Attachments: MRELEASE-459.1.patch, patch.txt > > > The releaseProfiles parameter on the perform goal is not taken into > consideration when no other profiles are passed in the command line. In other > words, the current code only uses the value of the parameter if you have > additional profiles passed in. > Example: > mvn release:perform -P someProfile (uses releaseProfiles value) > mvn release:perform (does NOT use releaseProfiles value) > The plugin should use the parameter even if no other profiles are passed. It > should actually encourage release profiles configured in your POM as opposed > to arbitrary profiles passed in the command line. > I have included a patch that uses the releaseProfiles parameter regardless of > any profiles passed in the command line. -- 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] (MCHANGES-290) Provide GitHub support for generate announcement report
Markku Saarela created MCHANGES-290: --- Summary: Provide GitHub support for generate announcement report Key: MCHANGES-290 URL: https://jira.codehaus.org/browse/MCHANGES-290 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Reporter: Markku Saarela Priority: Minor Attachments: announchement-github.patch Provide GitHub support for generate announcement report. Patch attached. -- 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] (MSHARED-246) Add option for T / threads
Robert Scholte created MSHARED-246:
--
Summary: Add option for T / threads
Key: MSHARED-246
URL: https://jira.codehaus.org/browse/MSHARED-246
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-invoker
Affects Versions: maven-invoker-2.0.11
Reporter: Robert Scholte
The {{InvocationRequest}} is missing an option to set the threadcount.
--
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-786) -Darguments doesn't allow -T to be passed to forked builds for multi threading
[
https://jira.codehaus.org/browse/MRELEASE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310020#comment-310020
]
Robert Scholte commented on MRELEASE-786:
-
Temporary fix in [r1392067|http://svn.apache.org/viewvc?rev=1392067&view=rev]
to prevent the {{UnrecognizedOptionException}}
Can only be fixed after MSHARED-246
> -Darguments doesn't allow -T to be passed to forked builds for multi threading
> --
>
> Key: MRELEASE-786
> URL: https://jira.codehaus.org/browse/MRELEASE-786
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.3.2
>Reporter: Tom Clark
>
> I would like to be able to use -T with the release plugin for the compiling
> phase, as the plugin is thread safe, which would allow for about half the
> release time.
> I've tried:
> {code}
> -Darguments='-T 3'
> {code}
> which doesn't throw an error but doesn't actually trigger multi threading.
> also:
> {code}
> -Darguments='-T3'
> -Darguments='"-T 3"'
> {code}
> Both throws an error saying that -T isn't parsable
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
> project parent: Failed to re-parse additional arguments for Maven invocation.
> Unrecognized option: -T -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
> (default-cli) on project parent: Failed to re-parse additional arguments for
> Maven invocation.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:319)
> 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.MojoExecutionException: Failed to re-parse
> additional arguments for Maven invocation.
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:295)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:247)
> 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.ReleaseExecutionException: Failed
> to re-parse additional arguments for Maven invocation.
> at
> org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:89)
> at
> org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:44)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease
RE: [jira] (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line
Please remove me from this mailing list Wayne Seth PMP CEA (h) 520-459-8069 (c) 520-456-6169 http://www.wayneseth.com -Original Message- From: Robert Scholte (JIRA) [mailto:j...@codehaus.org] Sent: Sunday, September 30, 2012 4:13 AM To: issues@maven.apache.org Subject: [jira] (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line [ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlas sian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-459. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in [r1391992|http://svn.apache.org/viewvc?rev=1391992&view=rev] > releaseProfiles has no effect without passing profiles in the command > line > -- > - > > Key: MRELEASE-459 > URL: https://jira.codehaus.org/browse/MRELEASE-459 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.0-beta-8, 2.0-beta-9 >Reporter: Andreas Christoforides >Assignee: Robert Scholte > Labels: contributers-welcome, help-requested, missing-integration-tests > Fix For: 2.4 > > Attachments: MRELEASE-459.1.patch, patch.txt > > > The releaseProfiles parameter on the perform goal is not taken into consideration when no other profiles are passed in the command line. In other words, the current code only uses the value of the parameter if you have additional profiles passed in. > Example: > mvn release:perform -P someProfile (uses releaseProfiles value) mvn > release:perform (does NOT use releaseProfiles value) The plugin should > use the parameter even if no other profiles are passed. It should actually encourage release profiles configured in your POM as opposed to arbitrary profiles passed in the command line. > I have included a patch that uses the releaseProfiles parameter regardless of any profiles passed in the command line. -- 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!defau lt.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-729) release:branch makes pom changes for branch in 'master' before branching
[
https://jira.codehaus.org/browse/MRELEASE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310021#comment-310021
]
Knut Vidar Siem commented on MRELEASE-729:
--
Isn't this the same problem as the one described in
[MRELEASE-335|http://jira.codehaus.org/browse/MRELEASE-335]? I don't know if
this aspect of the plugin varies between SCMs, but if not, the following
property quadruple should at least let you branch without committing to the
current branch/checkout/working copy. {{-DupdateBranchVersions=true
-DupdateWorkingCopyVersions=false -DsuppressCommitBeforeBranch=true
-DremoteTagging}}. (I have only tried this with Subversion.)
> 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: branch, 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] (MSHARED-246) Add option for T / threads
[
https://jira.codehaus.org/browse/MSHARED-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSHARED-246.
--
Resolution: Fixed
Fix Version/s: maven-invoker-2.0.12
Assignee: Robert Scholte
Fixed in [r1392106|http://svn.apache.org/viewvc?rev=1392106&view=rev]
> Add option for T / threads
> --
>
> Key: MSHARED-246
> URL: https://jira.codehaus.org/browse/MSHARED-246
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-invoker
>Affects Versions: maven-invoker-2.0.11
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: maven-invoker-2.0.12
>
>
> The {{InvocationRequest}} is missing an option to set the threadcount.
--
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] (MCHANGES-290) Provide GitHub support for generate announcement report
[ https://jira.codehaus.org/browse/MCHANGES-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MCHANGES-290: - Assignee: Olivier Lamy > Provide GitHub support for generate announcement report > --- > > Key: MCHANGES-290 > URL: https://jira.codehaus.org/browse/MCHANGES-290 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Reporter: Markku Saarela >Assignee: Olivier Lamy >Priority: Minor > Attachments: announchement-github.patch > > > Provide GitHub support for generate announcement report. > Patch attached. -- 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] (MCHANGES-290) Provide GitHub support for generate announcement report
[ https://jira.codehaus.org/browse/MCHANGES-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCHANGES-290. - Resolution: Fixed Fix Version/s: 2.9 patch applied. Thanks! > Provide GitHub support for generate announcement report > --- > > Key: MCHANGES-290 > URL: https://jira.codehaus.org/browse/MCHANGES-290 > Project: Maven 2.x Changes Plugin > Issue Type: Improvement > Components: announcement >Reporter: Markku Saarela >Assignee: Olivier Lamy >Priority: Minor > Fix For: 2.9 > > Attachments: announchement-github.patch > > > Provide GitHub support for generate announcement report. > Patch attached. -- 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] (MARCHETYPES-41) Projects from maven-archetype-quickstart use a very old JUnit: JUnit 3.8.1, released on 4 September 2002
[ https://jira.codehaus.org/browse/MARCHETYPES-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MARCHETYPES-41. --- Resolution: Fixed Fix Version/s: maven-archetype-quickstart-1.2 Assignee: Olivier Lamy upgraded to junit 4.8.2 (trunk was 4.7) > Projects from maven-archetype-quickstart use a very old JUnit: JUnit 3.8.1, > released on 4 September 2002 > > > Key: MARCHETYPES-41 > URL: https://jira.codehaus.org/browse/MARCHETYPES-41 > Project: Maven Archetype Bundles > Issue Type: Bug > Components: Maven Quickstart Archetype >Affects Versions: 1.2 >Reporter: Steinar Bang >Assignee: Olivier Lamy > Fix For: maven-archetype-quickstart-1.2 > > > When creating a project from the maven-archetype-quickstart the created > project uses JUnit 3.8.1. > maven-archetype-quickstart should create projects using a newer version of > JUnit, perferrably the current stable release. > In any case: JUnit 3.8.1 was released on 4 September 2002, which at the time > of writing (29 September 2012) is a little over 10 years old. In software > terms this is very old software. -- 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-5353) Ignore qualifiers in exclusive upper bound
Jesse Long created MNG-5353: --- Summary: Ignore qualifiers in exclusive upper bound Key: MNG-5353 URL: https://jira.codehaus.org/browse/MNG-5353 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4 Reporter: Jesse Long Please change the behaviour of exclusive upper bounds to the following: In a version range, like [1.7.0,1.8.0), 1.8.0-alpha1 should not be included in the range. 1.8.0* should not be included in the range. This allows for us configure natural ranges for projects using semantic versioning. Please see: http://markmail.org/message/4tubas4uok6ahbcp http://markmail.org/message/s2ry2uru4ibub43q -- 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-5353) version ranges: Ignore qualifiers in exclusive upper bound [lw,up)
[ https://jira.codehaus.org/browse/MNG-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5353: --- Complexity: Expert (was: Intermediate) Affects Version/s: 2.0.11 2.2.1 Issue Type: Wish (was: Bug) Summary: version ranges: Ignore qualifiers in exclusive upper bound [lw,up) (was: Ignore qualifiers in exclusive upper bound) > version ranges: Ignore qualifiers in exclusive upper bound [lw,up) > -- > > Key: MNG-5353 > URL: https://jira.codehaus.org/browse/MNG-5353 > Project: Maven 2 & 3 > Issue Type: Wish > Components: Dependencies >Affects Versions: 2.0.11, 2.2.1, 3.0.4 >Reporter: Jesse Long > > Please change the behaviour of exclusive upper bounds to the following: > In a version range, like [1.7.0,1.8.0), 1.8.0-alpha1 should not be included > in the range. 1.8.0* should not be included in the range. > This allows for us configure natural ranges for projects using semantic > versioning. > Please see: > http://markmail.org/message/4tubas4uok6ahbcp > http://markmail.org/message/s2ry2uru4ibub43q -- 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
