[
http://jira.codehaus.org/browse/CONTINUUM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246107#action_246107
]
Brett Porter commented on CONTINUUM-2591:
-----------------------------------------
yep, I understand. I actually think the technique is quite acceptable (we have
special cases for other SCMs around too), perhaps best if a concurrent patch is
submitted to SCM so that it can be cleaned up as soon as the next release of
that happens.
As for patching trunk & branch - that's certainly helpful in getting it applied
to both, with the priority being for trunk since it always has to land there
anyway. In this case, because of the scope of the change (upgrading libraries /
crude fix), I think it's better not to apply it to 1.3.x and instead focus on
pushing for a non-beta 1.4 release soon :)
> 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
