[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_58042 ]
Brett Porter commented on MRELEASE-66:
--
+1 to change the super POM. Please file it under MNG for 2.0.3.
anything else to do in this issue?
Source and Javadoc bundles should be
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_57393 ]
Dan Tran commented on MRELEASE-66:
--
How about fixup super pom to activate the profile only when
-DperformRelease=true.
Currently it is activated with any value.
Then the user can
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_57401 ]
Dan Tran commented on MRELEASE-66:
--
I checked in the fix for http://jira.codehaus.org/browse/MRELEASE-59 to allow
user to override
with -Darguments=-DperformRelease=false.
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_54784 ]
Dan Tran commented on MRELEASE-66:
--
According to Jason, updateReleaseInfo is not used any more
dantran folk, what is the purpose of deploy:deploy's updateReleaseInfo flag
field (
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_54815 ]
Brett Porter commented on MRELEASE-66:
--
It's still used. possibly not required by 2.1, but then to be able to deploy to
a repo and serve 2.0 clients it'll still be needed.
[ http://jira.codehaus.org/browse/MRELEASE-66?page=comments#action_54729 ]
Dan Tran commented on MRELEASE-66:
--
cl.createArgument().setLine( -DperformRelease=true );
triggers super pom performRelease Profile which will generate those bundle
