[
http://jira.codehaus.org/browse/WAGON-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233218#action_233218
]
Anthony Whitford commented on WAGON-303:
----------------------------------------
I would very much like improved git compatibility and agree that the current
implementation is basically making an assumption about tagging conventions that
is true for cvs and svn, but is not true for git...
Personally, rather than leverage settings.xml as Kathryn suggests, I think I
would rather see improved url parsing/handling. Why can't .../project.git/dir
mean what we think it should mean, but beneath the covers is translated to the
appropriate multiple steps by the git provider?
> Make wagon-scm work better with git
> -----------------------------------
>
> Key: WAGON-303
> URL: http://jira.codehaus.org/browse/WAGON-303
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-scm
> Affects Versions: 1.0-beta-6
> Reporter: Kathryn Huxtable
> Attachments: wagon-scm.patch
>
>
> Using wagon-scm with site:deploy doesn't work with git because the wagon
> appends the current target to the repository name. This only works with
> subversion.
> I have added a mechanism to supply a branch or tag in settings.xml and use it
> for non-git repositories.
--
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
