profile and projects/build definitions

[Benoit Decherf-2]

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

[Emmanuel Venisse-2]

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 <decherfb@...> 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
>

[Benoit Decherf-2]

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 <decherfb@...> 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
>>
>>    
>
>  

[Emmanuel Venisse-2]

Yes, it can be done like that.

Emmanuel

On Jan 25, 2008 1:16 PM, Benoit Decherf <decherfb@...> wrote:

> 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 <decherfb@...> 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
> >>
> >>
> >
> >
>
>