[jira] Commented: (MRELEASE-457) Non sparse-checkout SCM support

["Mark Struberg (JIRA)" <ji...@codehaus.org>]

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

Mark Struberg commented on MRELEASE-457:
----------------------------------------

the broken <scm> URL assembling is done in the following code parts:

* DefaultModelInheritanceAssembler#assembleModelInheritance calls
  childScm.setDeveloperConnection( appendPath( parentScm.getDeveloperConnection(), child.getArtifactId(), childPathAdjustment, appendPaths ) );

* MavenProject#getModulePathAdjustment which actually creates the pathAdjustment

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