[
http://jira.codehaus.org/browse/CONTINUUM-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129440#action_129440
]
Benoit Decherf commented on CONTINUUM-1633:
-------------------------------------------
If I do it that way I will have a diferent behaviour between builds and the
release.
I won't be able to choose the version of the JDK to use (It seems that on some
case, the behaviour is diferent between jdk1.4 and jdk1.6 with target and
source 1.4), I won't be able to upgrade easily maven (I will have to do an
internal version of continuum to upgrade the jars), and I won't be able to pass
variable that are defined in the profile.
And in case of an error, it's easier to check the output of the release plugin
than just see the failed phase and a short description of the problem.
The actual ways continuum make release is useless for us, and we will have to
make a own release system If you are not interested with this feature.
I'm finishing a first version of the release system we need (integrated to
continuum). I will give you a sample URL at the end of the week to know what
you think about it and if it will be possible to integrate it to continuum.
> 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
