continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (CONTINUUM-1633) release using mvn release plugin
Date Wed, 02 Apr 2008 05:03:58 GMT


Brett Porter closed CONTINUUM-1633.

      Assignee: Brett Porter
    Resolution: Won't Fix

I think the answer here is that we need to be able to use the configuration from the POM (which
I believe is already filed). Executing the release plugin externally doesn't seem to make
much sense - you'd get the same functionality from the classes. You'd also lose the ability
to monitor it's progress.

> release using mvn release plugin
> --------------------------------
>                 Key: CONTINUUM-1633
>                 URL:
>             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:
For more information on JIRA, see:


View raw message