[
http://jira.codehaus.org/browse/MRELEASE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated MRELEASE-457:
-----------------------------------
Attachment: MRELEASE-457.patch
This patch enables the release of child modules even with SCMs which doesn't
support sparse checkout. The trick is to parse the pom to be released and
search for a similar pom in the target/checkout directory. Then use this poms
directory for running the release-perform goals.
There is currently a small issue left with child modules releasing because we
get the childModules relative path added to the base SCM-URL. This is needed
for SVN but breaks a lot other SCMs. The workaround is to add a <scm> section
to each submodule until we fixed this bug.
> 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
