[
http://jira.codehaus.org/browse/CONTINUUM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated CONTINUUM-2591:
------------------------------------
Attachment: CONTINUUM-2591-trunk.patch
here's a naive application of the patch to trunk. I haven't checked it works
yet - it seemed odd to be changing the method signatures when trunk had
approached it differently (I think by delegating some of the methods). It needs
a closer look, but I ran out of time.
It's better to address patches to trunk - the 1.3.x releases should be small,
and we're overdue to get a 1.4.1 out anyway...
> Git based maven2 builds can't properly release or checkout on branch
> --------------------------------------------------------------------
>
> Key: CONTINUUM-2591
> URL: http://jira.codehaus.org/browse/CONTINUUM-2591
> Project: Continuum
> Issue Type: Bug
> Components: Release
> Affects Versions: 1.3.6
> Reporter: Brent N Atkinson
> Priority: Critical
> Attachments: CONTINUUM-2591-trunk.patch, CONTINUUM-2591.patch
>
>
> It is not possible to add or release a maven2 project using the git scm when
> the project is on a branch. There appears to be multiple reasons for this:
> * The maven-scm version bundled with continuum is old and doesn't include git
> providers with sufficiently complete git support.
> * Git SCM URLs don't include sufficient information to identify the branch.
> * Continuum-release's UpdateWorkingCopyPhase doesn't properly update the
> working (it always uses master rather than the current branch)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
