one of the problems here is that if you start letting the CI
admin
make changes to project and project group names then you are
breaking
the linkage between the POM and the representation of the
project in
continuum. Unless you start adding in mapping
functionalities and
thats just a pain when really, the name in the CI ought to
reflect
reality in the project. Now perhaps the project group is
something
that can be opened more for some configuration changes since
it is
kind of an external concept being mapped onto the poms...its
using the
pom that you load up for these defaults and then also making
a project
for that same project group, mapping it twice into continuum
as a
group and as a project...
if this is really what we want to change here then perhaps
we ought to
make it an option for configuration of the project group in
all cases,
the ability to specify the name of the project group...or
give it some
kinda short identification element. I kinda like that idea,
then we
can use 'Doxia' for 'The Doxia Project' and we can even use
the short
user input project group Id in the urls...
it would be nice if we could setup a mapping for
http://ci.host.org/Doxia
and take you to the project group.
I know brett had that desire a while back, this would more
then
address that and make it easier to work with the project
group in
general
jesse
On 10/27/06, Rahul Thakur <rahul.thakur.xdev gmail.com> wrote:
> I believe its more to do with - auto/dynamic
configuration, or, giving
> a CI server admin more control to setup their continuum
installation.
>
> I think Continuum should be able to support both modes,
> a) zero-config (almost), and
> b) the ablity to afford more control to the user, like
in the case of
> edit/reorganize project groups.
>
> With dynamic configuration it would make it easy for a
project team to
> change the pom.xml and have the changes reflect in
Continuum, but same
> time - the CI admin user (as can be the case with
organisations where
> this is a separate role/job) , this would mean the
projects can, for
> example, hop groups as and when changes are detected.
>
> Thoughts?
>
> Cheers,
> Rahul
>
>
> ----- Original Message -----
> From: "Jesse McConnell (JIRA)" <jiracodehaus.org>
> To: <issuesmaven.apache.org>
> Sent: Saturday, October 28, 2006 5:36 AM
> Subject: [jira] Commented: (CONTINUUM-924) Add ability
to edit group
>
>
> > [
> > http://jira.codehaus.org/browse/CONTINUU
M-924?page=comments#action_78658 ]
> >
> > Jesse McConnell commented on CONTINUUM-924:
> > -------------------------------------------
> >
> > I wonder about this one a bit. Rahul was asking
about the same sort
> > of thing on irc a day or two ago and I am glad I
found this issue
> > here.
> >
> > My ultimate question on this is would we be better
served to change
> > things such that when the pom changes in the m2
project and have that
> > automagically applied to the names of projects and
project groups.
> >
> > Yes this needs to be added for the ant and shell
script project
> > groups...but for m2 and maybe m1 projects can be
pull this info from
> > the pom. The Project Object Model is actually
supposed to represent
> > all the major aspects of the project so perhaps we
can get away with
> > that.
> >
> >> Add ability to edit group
> >> -------------------------
> >>
> >> Key: CONTINUUM-924
> >> URL: http://
jira.codehaus.org/browse/CONTINUUM-924
> >> Project: Continuum
> >> Issue Type: Sub-task
> >> Affects Versions: 1.1
> >> Reporter: Carlos Sanchez
> >> Assigned To: Henry S. Isidro
> >>
> >> Now that groups are added it'd be nice to have
the ability of
> >> changing group name or moving projects from
group.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one
of the
> > administrators: h
ttp://jira.codehaus.org/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> > http://www.atl
assian.com/software/jira
> >
> >
>
>
--
jesse mcconnell
jesse.mcconnellgmail.com
|