[
http://jira.codehaus.org/browse/MRELEASE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232444#action_232444
]
Benjamin Bentmann commented on MRELEASE-457:
--------------------------------------------
bq. Or is this part too early in the lifecycle to get access to the
maven-scm-provider?
Yes. Also, how would you find this maven-scm-provider, e.g. there is no
artifact id/version mentioned in the URL, add another black magic discovery? In
general, I have a strong objection against the idea that construction of the
effective POM requires pluggable/external components as this makes the POM
depend on a specific runtime environment (e.g. Maven class loader hierarchy)
and hinders its consumption in tools other than Maven. The POM should be fully
declarative and be controlled by fixed/well-known rules.
> 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
