Hey all,
First day back at work and first up we're doing a release - at the end of
the year I'd bumped our poms to use the 2.4 plugin but never did any
releases, and now - I find it appears to be broken with git.
In my release config we have:
<pushChanges>false</pushChanges>
<localCheckout>true</localCheckout>
however, when release:perform runs, the mojo tries to clone from the REMOTE
repository which doesn't have the new tag, dropping back to 2.3.2 and
everything works fine and we can release.
Is this a known issue?
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On Wed, Dec 19, 2012 at 12:04 PM, Robert Scholte <rfscho...@apache.org>wrote:
> The Apache Maven team is pleased to announce the release of the Maven
> Release Plugin, version 2.4
>
> This plugin is used to release a project with Maven, saving a lot of
> repetitive, manual work. Releasing a project is made in two steps: prepare
> and perform.
>
> http://maven.apache.org/**plugins/maven-release-plugin/<http://maven.apache.org/plugins/maven-release-plugin/>
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.**plugins</groupId>
> <artifactId>maven-release-**plugin</artifactId>
> <version>2.4</version>
> </plugin>
>
> Release Notes - Maven 2.x Release Plugin - Version 2.4
>
> ** Bug
> * [MRELEASE-186] - Active profiles are not carried through into the
> release descriptor
> * [MRELEASE-260] - Profiles given on command-line not added to
> exec.additionalArguments
> * [MRELEASE-415] - Plugin fails to activate profiles in submodules.
> * [MRELEASE-459] - releaseProfiles has no effect without passing
> profiles in the command line
> * [MRELEASE-511] - release:prepare "Error parsing version, cannot
> determine next version: Unable to parse the version string" when running in
> batch mode.
> * [MRELEASE-571] - When collecting active profiles, the active
> profiles from parent poms are not considered
> * [MRELEASE-614] - releaseProfiles works only if at least one
> (default) profile is activated in the same pom.xml
> * [MRELEASE-619] - release:branch doesn't work as expected with
> multi-module projects
> * [MRELEASE-667] - Profiles activated in settings.xml can't be
> deactivated for release
> * [MRELEASE-750] - String index out of range: -1 in
> ReleaseUtils.**loadResolvedDependencies()
> when using Parent-Module-Layout
> * [MRELEASE-755] - When passing arguments to underlying maven
> executions not all maven options are accepted
> * [MRELEASE-772] - mvn release:prepare fails with IOException and a
> write error (Access is denied)
> * [MRELEASE-775] - IllegalStateException while checking for
> modifications if multiple exclusion patterns match
> * [MRELEASE-785] - Arguments containing spaces and quotes cause the
> forked maven process to fail
> * [MRELEASE-786] - -Darguments doesn't allow -T to be passed to forked
> builds for multi threading
> * [MRELEASE-787] - release:prepare-with-pom fails when
> suppressCommitBeforeTag is used (SVN)
> * [MRELEASE-795] - Wrong level when using release:branch
> * [MRELEASE-808] - Can't generate release-pom.xml when custom
> finalName contains ${project.version}
>
> ** Improvement
> * [MRELEASE-559] - Clarify parameter documentation for release:branch
> * [MRELEASE-734] - When releaseVersion and developmentVersion are
> passed in command-line but are empty should be treated as not-defined
> * [MRELEASE-783] - release:update-versions should not need SCM config
> * [MRELEASE-796] - Add AbstractScmReleaseMojo
>
> ** New Feature
> * [MRELEASE-592] - Please allow de-activation of profiles
>
> ** Task
> * [MRELEASE-776] - use maven-plugin-tools' java 5 annotations
>
>
> Enjoy,
>
> -The Apache Maven team
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org>
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
