> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 14, 2004 2:18 PM
> To: Avalon Developers List
> Subject: Re: [PROPOSAL] Adopting JIRA
> 
> Farr, Aaron wrote:
> 
> >>-----Original Message-----
> >>From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> >>Sent: Wednesday, January 14, 2004 2:06 PM
> >>To: Avalon Developers List
> >>Subject: Re: [PROPOSAL] Adopting JIRA
> >>
> >>Farr, Aaron wrote:
> >>
> >>>Thoughts?
> >>
> >>One more approach - create groups relative to maven GroupID (which would
> >>be closeish to the moderate approach you described).  This means that we
> >>should be able to more simply automate project to JIRA links in our
> >>documentation.
> >
> >
> > I like the idea of tying it to Maven.  Though that would result in a
> project
> > list like this:
> >
> > http://www.apache.org/dist/avalon/
> >
> > right?
> 
> Umm - good point - that's way too many groups.
> Perhaps we should review project group ids as we move forward.  E.g.:
> 
>     cornerstone-xxx ---> avalon-components
>     excalibur-xxx ---> excalibur
>     avalon-xxx ---> avalon

Sounds pretty good.  I'm a +1 on consolidating cornerstone-xxx and
excalibur-xxx since generally we do a Cornerstone release or an Excalibur
release (several components all at once).  

But for Avalon, we have framework, meta, repository, utilities, etc.
They're all on different release schedules.  But if we really want meta,
repository and utilities to be extensions of the framework, then they could
all be included under one group ID (and JIRA project).

Fortress should be separate.  It was originally excalibur-fortress and then
moved to avalon-fortress.  It should either stay there or move to just
"fortress."

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to