maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Gardner (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MRELEASE-457) Non sparse-checkout SCM support
Date Fri, 20 Aug 2010 08:53:32 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232553#action_232553
] 

Grant Gardner edited comment on MRELEASE-457 at 8/20/10 3:51 AM:
-----------------------------------------------------------------

Can this be implemented with the projectPath concept that the release plugin already understands?

ie change the git provider to parse the additional path information into the scm repository's
projectPath attribute. Then as long as you follow the convention in placing modules in a subdirectory
named for the module it should just work.

Of course it would be even better if the childPathAdjustment code was changed to use the relative
path between module and parent rather than artifactId. I think even SVN modules that don't
follow the convention are already broken in this regard.

      was (Author: lwoggardner):
    Can this be implemented with the projectPath concept that the release plugin already understands?

ie change the git provider to parse the additional path information into the scm repository's
projectPath attribute. Then as long as you follow the convention in placing modules in a subdirectory
named for the module it should just work.

Of course it would be event better if the childPathAdjustment code was changed to use the
relative path between module and parent rather than artifactId. I think even SVN modules that
don't follow the convention are already broken in this regard.
  
> Non sparse-checkout SCM support
> -------------------------------
>
>                 Key: MRELEASE-457
>                 URL: http://jira.codehaus.org/browse/MRELEASE-457
>             Project: Maven 2.x Release Plugin
>          Issue Type: New Feature
>          Components: perform, scm
>    Affects Versions: 2.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 2.1
>
>         Attachments: MRELEASE-457.2.patch, MRELEASE-457.patch
>
>
> Some SCMs like GIT, Mercurial, Bazaar, BitKeeper, Darcs, and Monotone doesn't support
sparse checkouts (checkout of a single subdirectory).
> So while doing a mvn release:perform in a sub-module, we will always get the _whole_
project checked out into target/checkout!
> For doing the clean build from this checkout, we have to implement a functionality to
find the right submodule first.

-- 
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

        

Mime
View raw message