You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brent N Atkinson (JIRA)" <ji...@codehaus.org> on 2010/12/01 22:19:03 UTC
[jira] Commented: (CONTINUUM-2591) Git based maven2 builds can't
properly release or checkout on branch
[ http://jira.codehaus.org/browse/CONTINUUM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246000#action_246000 ]
Brent N Atkinson commented on CONTINUUM-2591:
---------------------------------------------
Once the maven-scm git provider is updated, as long as the pom includes the proper 'tag' attribute in the scm metadata, continuum (actually maven-scm) can properly checkout the project and switch to the branch named in the 'tag' attribue.
> 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.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