Re: Change versions in build.xml and project.xml?

Maven I bet ;-)
Your wise version numbers comments are welcome.
I just think that having a 1.x and breaking some "user API / xml DTD" at
each minnor number is dangerous as well.

Let s try to have a 1.x this year, with a bunch of new features and good QA
;-)
Alex

----- Original Message ----- 
From: "Vincent Massol" <[email protected]>
To: <aspectwerkz-devel-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org>
Sent: Saturday, March 06, 2004 8:09 PM
Subject: RE: [aspectwerkz-devel] Change versions in build.xml and
project.xml?


>
>
> > -----Original Message-----
> > From: aspectwerkz-devel-admin-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org [mailto:aspectwerkz-
> > [email protected]] On Behalf Of Alex
> > Sent: 06 March 2004 19:12
> > To: aspectwerkz-devel-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
> > Subject: Re: [aspectwerkz-devel] Change versions in build.xml and
> > project.xml?
> >
> > the 0.10 is in aspectwerkz2 cvs module and what you described should
> be in
> > place (0.10.RC1)
>
> ok, will checkout aspectwerkz2.
>
> <rant>
> hmmm... ok, so HEAD is dead? i.e. there's no more development at all on
> it, not even bug fixes? If so, it should have a version of 0.9.1dev or
> something like that... ;-).
>
> Anyway, so it means that 0.10 is a major change, right? I guess that's
> why it was developed on a branch (as the usual practice is to have the
> latest version on HEAD and bug fixes on a branch).
>
> BTW, I find that having 0.x versions is very misleading. It's supposed
> to mean that it's not stable yet. So it's supposed to say to people:
> don't use this version in any serious work. But the problem is that when
> a framework stays in 0.x state for long and when that framework is
> useful (as AW is!) and there's lots of advertising for it (as there is
> for AW), then 0.x doesn't mean anything anymore and you'll end up anyway
> with users very angry if you break seriously some APIs. So I guess AW
> 0.9 is equivalent to a 1.x version and 0.10 is equivalent to a 2.x
> one... :-) That's probably why the branch is called aspectwerkz2 ;-)
> </rant>
>
> Thanks Alex and don't be concerned about my rant. It's not addressed at
> AW in particular. It's just that I see so many frameworks in the java
> open source world doing this that I am a bit tired with this strategy...
> :-)
>
> Thanks
> -Vincent
>
> >
> > Alex
> >
> > ----- Original Message -----
> > From: "Vincent Massol" <[email protected]>
> > To: <aspectwerkz-devel-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org>
> > Sent: Saturday, March 06, 2004 5:38 PM
> > Subject: [aspectwerkz-devel] Change versions in build.xml and
> project.xml?
> >
> >
> > > Hi,
> > >
> > > I remember pointing this out some time ago but I did not get any
> > > response from you guys.
> > >
> > > I have done an update a CVS update of the aspectwerkz module and if
> I
> > > build it, it will generate 0.9 libraries. This is obviously wrong as
> the
> > > version should be 0.10dev (or 0.10-SNAPSHOT, or whatever convention
> > > you'd like to use).
> > >
> > > Don't you think it would be a good idea to modify build.xml and
> > > project.xml to use 0.10dev instead of 0.9?
> > >
> > > Thanks
> > > -Vincent
>
>
> _______________________________________________
> aspectwerkz-devel mailing list
> aspectwerkz-devel-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
> http://lists.codehaus.org/mailman/listinfo/aspectwerkz-devel
>
>