[
http://jira.codehaus.org/browse/MRELEASE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100153
]
Yves Van Steen commented on MRELEASE-237:
-----------------------------------------
If it is possible I would like to see a property to the release plugin
-Dblock-reactor that blocks the modules being build/released.
mvn -N release:prepare release:perform is the command I use know.
and in the configuration of the release plugin
...
<arguments>-N<arguments>
...
This seems to work but is not that clear. Definitly not to maven newbies who
just what that one pom released.
I've had to roll back some stuff because the -N was forgotten to the command
and someone made a mess of things.
Defenitily not fun for an administrator but it's my job. You break it, I fix
it!
The tag will still have all the files and directories in it's path but that I
don't mind that much. Maybe you could create an extra property
-Dscm-remove-modules property that first of all reacts to the block-reactor
property and that sais it removes the module directories from the created tag
in the source repository. This would be possible for subversion but not sure
for other repository types. So make it scm dependent.
Otherwise it was just a configuration in the maven pom like so :
...
<block-reactor>true</block-reactor>
<scm-remove-modules>true</scm-remove-modules>
...
If this was in maven, maven would be perfect. To me this is just the last hick
up in functionality.
> can't release a pom without it's modules
> ----------------------------------------
>
> Key: MRELEASE-237
> URL: http://jira.codehaus.org/browse/MRELEASE-237
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-5
> Reporter: Brett Porter
>
> We have the common pattern of a parent POM which may have modules, but is
> released independently from them (plugins, archetypes being a classic
> example). This is currently not possible in the release plugin.
--
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
