You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2012/11/23 01:26:14 UTC
[jira] (CONTINUUM-1633) release using mvn release plugin
[ https://jira.codehaus.org/browse/CONTINUUM-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1633:
------------------------------------
Patch Submitted: Yes
> release using mvn release plugin
> --------------------------------
>
> Key: CONTINUUM-1633
> URL: https://jira.codehaus.org/browse/CONTINUUM-1633
> Project: Continuum
> Issue Type: Improvement
> Components: Release
> Affects Versions: 1.1
> Reporter: Benoit Decherf
> Labels: backlog-to-cleanup
> Attachments: continuum_release2.patch
>
>
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira