[
http://jira.codehaus.org/browse/MRELEASE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243380#action_243380
]
Mark Struberg commented on MRELEASE-457:
----------------------------------------
Hi Olivier!
Please also check Grants comment with the projectPath. Hi is right that I
(mis-?) used an existing parameter for passing the information about the found
child pom. Otoh I think changing the project path is also not the correct way.
To be completely clean, we probably need to introduce a new parameter. But not
sure if this is really needed - that's why I didn't commit it myself but asked
for reviews ;)
LieGrue,
strub
> 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: Olivier Lamy
> 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
