[
http://jira.codehaus.org/browse/CONTINUUM-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134814#action_134814
]
PeteJohlie commented on CONTINUUM-1633:
---------------------------------------
I am having the same issue with continuum and the release button.
It does not behave like the plugin and my pom is not handled the same.
Setting up a goal as follows:
POM filename: pom.xml
Goals: release:prepare release:perform -X -e -Ptst
Arguments: --batch-mode --non-recursive
Build Fresh (Run always a clean checkout instead of an SCM update)
Always Build
Is it default?
Schedule: Never DEFAULT_SCHEDULE
Profile: vm-tst-apps
Type: maven2
Description:
We have modified the <preparationGoals> of the release plugin to use
cargo:deploy for some profiles
I can get that to work in continuum when using a specific build definition. Our
only problem is that we do not get the chance to provide release/tag/etc
values.
However, when using the release button (which allows us to provide the values),
the variables do not work.
Why doesn't the release button just act like a cmd-line invocation of the mvn
release:prepare?
thanks
> 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
> Fix For: 1.x
>
>
> 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
