maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MRELEASE-457) Non sparse-checkout SCM support
Date Thu, 23 Dec 2010 22:52:58 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Struberg closed MRELEASE-457.
----------------------------------

    Resolution: Fixed

Grant, I've looked at my patch again and it seems that the solution of passing the child modules
location via the releaseDescriptors checkoutPath property is the least intrusive way. Using
the projectPath would change lot of functionality and would break a few other things as far
as I've seen.

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