continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Decherf (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-1633) release using mvn release plugin
Date Thu, 22 May 2008 15:38:22 GMT


Benoit Decherf updated CONTINUUM-1633:

    Attachment: continuum_release2.patch

Here is my alternative.
There are several changes:
  - I add the possibility to make the release from a previous tag/revision (and create a branch
from this tag to create the release).
  - It is now possible to release all/several projects of a group. (The projects doesn't need
to have the same parent).
  - The release is done by an external maven process.
  - Profiles are supported.

This still not support the mutliple project. I will work to add it.

This is what I like to have in continuum. Please give me some feedback about it.

> 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
>             Fix For: 1.x
>         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 contact one of the administrators:
For more information on JIRA, see:


View raw message