[
http://jira.codehaus.org/browse/CONTINUUM-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129445#action_129445
]
Brett Porter commented on CONTINUUM-1633:
-----------------------------------------
there is also an issue for using the different profiles in a release. Your
problem is real - I would just like to see the release system fix the real
issues at hand than delegate it all.
But it's great that you are working on an alternative - we look forward to
seeing it!
> release using mvn release plugin
> --------------------------------
>
> Key: CONTINUUM-1633
> URL: http://jira.codehaus.org/browse/CONTINUUM-1633
> Project: Continuum
> Issue Type: Improvement
> Components: Release
> Affects Versions: 1.1
> Reporter: Benoit Decherf
> Assignee: Brett Porter
>
> I think that the release process should use the release plugin rather than
> the maven-release classes directly.
> Actually, it's possible to choose the maven installation to execute the
> compilation in continuum, BUT the maven version used to release a project
> can't be changed because of the compilation/runtime dependency of
> continuum-release.
> Also, if I configure the release plugin in pom.xml (for default values or to
> use a specific version of the plugin), this is ignored by continuum.
> What do you think about externalize the release execution using external
> command line as you do to execute scheduled goals ? Is there any blocker
> issue so that it's not possible ?
--
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
