You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by "Farr, Aaron" <Aa...@am.sony.com> on 2004/11/03 15:09:54 UTC

RE: [poll] (excalibur|avalon|)-framework, (excalibur|avalon|)-log kit?

> -----Original Message-----
> From: Leif Mortenson [mailto:leiflists@tanukisoftware.com]
> >>
> >>
> >I recommend not changing anything for current releases.  For future
> >releases, we should change only the groupId.
> >
> >
> I would prefer deciding on a style for our first release and then
> sticking to it. The
> users will already be making some changes for the move from avalon to
> excalibur.
> I would like to avoid making them make another set of changes for our
> second release.

Perhaps I wasn't clear.

The code for, say, avalon-framework-4.2.0.jar hasn't changed.  Neither will
the code for 4.1.x.  So why not keep those under
avalon-framework/avalon-framework as it is now?  No change in code, so no
change for users.

When (if) Excalibur releases avalon-framework-4.3.0.jar or whatever is next
then let's change to excalibur[-framework]/avalon-framework-4.3.0.jar.  The
code will have changed at that point and users would be making a change from
4.2 to 4.1 anyway.

So yes, for *our* first release we should pick one form and stick with it.
But I don't think there's any need to change or rename older releases.

Just my $0.02. :)

J. Aaron Farr
  SONY ELECTRONICS
  STP SYSTEMS
  (724) 696-7653

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/