Re: release button in project group page.

[Benoit Decherf]

Yes, but I think that it should release all projects in the group.
It's really strange that this button doesn't work as the "build all 
projects" button. And it would be a very great feature if it do it.


Benoit.

Edwin Punzalan wrote:

I think this is because the release plugin is being called at the parent pom
once to also release all its modules whereas builds are being called at each
project in the project group.
On Sun, Mar 2, 2008 at 3:23 AM, Benoit Decherf <[EMAIL PROTECTED]>
wrote:

  

Hi,

The release button of the project group page only works if all projects
in the group have the same parent and the parent is in the group.

Why doesn't it make a release of all projects in the group ?  I think
that it should work as the build all projects button.

Benoit.




  

release button in project group page.

[Benoit Decherf]

Hi,

The release button of the project group page only works if all projects 
in the group have the same parent and the parent is in the group.


Why doesn't it make a release of all projects in the group ?  I think 
that it should work as the build all projects button.


Benoit.

continuum-model

[Benoit Decherf]

Hi,

I'm working on bug CONTINUUM-1633 
. So the release process 
will be done executing maven directly.
I want to add a class describing the result of a release 
prepare/process/rollback/clean action similar to the buildResult for the 
build.
Additionaly, I'd like to fix the bug CONTINUUM-1506 
 and add some field to 
the result page.


So I create a bean ResultRelease in continuum model project. Can you 
confirm that this bean should gone in this component ? Or should it be 
directly in continuum-api ? The bean won't be mapped to any database table.


Thanks,
Benoit.

Re: profile and projects/build definitions

[Benoit Decherf]

Ok, so for the release process, the user should be able to select the 
profile he want to use.
There should be a combo with the list of available profiles in the 
releasePrepare.jsp ?


Benoit.

Emmanuel Venisse wrote:

A profile can't be applied to a project because generally, users want to
build their projects for different environment.

Maybe, we'll add a defaut project profile in future versions that can be
overriden in the build definition

Emmanuel

On Jan 25, 2008 11:31 AM, Benoit Decherf <[EMAIL PROTECTED]> wrote:

  

Hi

I m' working on http://jira.codehaus.org/browse/CONTINUUM-1633 because
it's blocker for us.

I think that some other bugs on continuum release should be corrected if
the release process is externalized to mvn.

But there is a problem with CONTINUUM-1572
<http://jira.codehaus.org/browse/CONTINUUM-1572>.  Actually, the profile
is associated to a build definition. But the jdk version to use or the
maven version should be associated to the component, don't you think ? I
don't want to modify the core of continuum so have you plane to make a
refactoring of the profile usage ? Or why a profile isn't associated to
the project (or project group) ?

Benoit




  

profile and projects/build definitions

[Benoit Decherf]

Hi

I m' working on http://jira.codehaus.org/browse/CONTINUUM-1633 because 
it's blocker for us.


I think that some other bugs on continuum release should be corrected if 
the release process is externalized to mvn.


But there is a problem with CONTINUUM-1572 
.  Actually, the profile 
is associated to a build definition. But the jdk version to use or the 
maven version should be associated to the component, don't you think ? I 
don't want to modify the core of continuum so have you plane to make a 
refactoring of the profile usage ? Or why a profile isn't associated to 
the project (or project group) ?


Benoit