You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stephen Colebourne <sc...@btopenworld.com> on 2004/01/04 20:49:43 UTC
[collections] What is left to do for 3.0?
The [collections] CVS has been tidied up prior to a 3.0 release today. The
CVS now only contains those classes to be released in a 3.0. These are all I
know of:
- Should PriorityQueue be deprecated? (Buffer effectively replaces it)
- Add CaseInsensitiveMap?
Do we just RC1 and then release, or do we need a public Beta? (I favour the
former)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Phil Steitz" <ph...@steitz.com>
> It's in. Have a look. I will add to / improve the tests if we decide to
> keep it in (though, once again, I am amazed at how good the stock
> framework tests are :-)
Looks fine to me :-)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] maven site Was: [collections] What is left to do for 3.0?
Posted by di...@multitask.com.au.
Henri Yandell <ba...@generationjava.com> wrote on 05/01/2004 07:37:08 PM:
>
>
> On Sun, 4 Jan 2004, Phil Steitz wrote:
>
> > Stephen Colebourne wrote:
> >
> > > I'm OK with RC1, but would like to switch to maven with this
release:
> >
> > +1, and I would like to settle the maven site issues so we can also
get
> > [lang]'s site published.
>
> Any thoughts on not using Maven's 'Project Documentation' standard bit
in
> the corner?
>
> I've been playing with sites that throw it all away and define their own
> navigation completely and quite like the result:
>
> http://www.osjava.org/norbert/
>
> So many of the Maven reports are just extra noise.
Which ones?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[collections] maven site Was: [collections] What is left to do for
3.0?
Posted by Henri Yandell <ba...@generationjava.com>.
On Sun, 4 Jan 2004, Phil Steitz wrote:
> Stephen Colebourne wrote:
>
> > I'm OK with RC1, but would like to switch to maven with this release:
>
> +1, and I would like to settle the maven site issues so we can also get
> [lang]'s site published.
Any thoughts on not using Maven's 'Project Documentation' standard bit in
the corner?
I've been playing with sites that throw it all away and define their own
navigation completely and quite like the result:
http://www.osjava.org/norbert/
So many of the Maven reports are just extra noise.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Phil Steitz <ph...@steitz.com>.
Stephen Colebourne wrote:
>>>>>- Add CaseInsensitiveMap?
>>>>
>>I could commit this eve. if that's what we want to do.
>
> Add it, I'll take a look, and if necessary we may delete it again
> temporarily.
It's in. Have a look. I will add to / improve the tests if we decide to
keep it in (though, once again, I am amazed at how good the stock
framework tests are :-)
> I'm OK with RC1, but would like to switch to maven with this release:
+1, and I would like to settle the maven site issues so we can also get
[lang]'s site published.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Phil Steitz" <ph...@steitz.com>
> Henri Yandell wrote:
> >>>- Should PriorityQueue be deprecated? (Buffer effectively replaces it)
> >>+1
Then PriorityQueueUtils will get deleted too (as its a new class, and we
don't want to add something immediately deprecated)
> >>>- Add CaseInsensitiveMap?
> I could commit this eve. if that's what we want to do.
Add it, I'll take a look, and if necessary we may delete it again
temporarily.
> > The RC1 from memory. We should [though wouldn't] be able to rename the
> > RC1 if it's good, so the CaseInsensitiveMap bit shouldn't magically
appear
> > in the released version.
>
> I agree that there should be no API changes after RC1. Given that Stephen
> was not thrilled with the API, it might be best to leave it out for now,
> especially since this is very easy for users to implement themselves (with
> any kind of behavior they want) by extending AbstractHashedMap (or
HashedMap).
I'm OK with RC1, but would like to switch to maven with this release:
- better index.xml needed
- better navigation.xml needed (links to javadoc of 2.1 and 3.0)
- javadoc overview.xml needs to be included
- build of source zips doesn't include all necessary files (developer guide
etc)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
>
> On Sun, 4 Jan 2004, Phil Steitz wrote:
>
>
>>Stephen Colebourne wrote:
>>
>>>The [collections] CVS has been tidied up prior to a 3.0 release today. The
>>>CVS now only contains those classes to be released in a 3.0. These are all I
>>>know of:
>>>
>>>- Should PriorityQueue be deprecated? (Buffer effectively replaces it)
>>
>>+1
>
>
> Yep, be aggressive.
>
>
>>>- Add CaseInsensitiveMap?
>>
>>I don't want to hold up the release. If we are actually ready to cut RC1
>>now, it is probably better to hold off on adding anything new. The class
>>is trivial, however, so if we expect a little span time between now and
>>actual release, we might want to add it now.
>
>
> How long does CaseInsensitiveMap need?
I could commit this eve. if that's what we want to do.
>
>
>>>Do we just RC1 and then release, or do we need a public Beta? (I favour the
>>>former)
>>
>>What has [collections] done in the past?
>
>
> The RC1 from memory. We should [though wouldn't] be able to rename the
> RC1 if it's good, so the CaseInsensitiveMap bit shouldn't magically appear
> in the released version.
I agree that there should be no API changes after RC1. Given that Stephen
was not thrilled with the API, it might be best to leave it out for now,
especially since this is very easy for users to implement themselves (with
any kind of behavior they want) by extending AbstractHashedMap (or HashedMap).
Otherwise, things look pretty good to me at this point.
Phil
>
> Hen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Henri Yandell <ba...@generationjava.com>.
On Sun, 4 Jan 2004, Phil Steitz wrote:
> Stephen Colebourne wrote:
> > The [collections] CVS has been tidied up prior to a 3.0 release today. The
> > CVS now only contains those classes to be released in a 3.0. These are all I
> > know of:
> >
> > - Should PriorityQueue be deprecated? (Buffer effectively replaces it)
>
> +1
Yep, be aggressive.
> > - Add CaseInsensitiveMap?
>
> I don't want to hold up the release. If we are actually ready to cut RC1
> now, it is probably better to hold off on adding anything new. The class
> is trivial, however, so if we expect a little span time between now and
> actual release, we might want to add it now.
How long does CaseInsensitiveMap need?
> > Do we just RC1 and then release, or do we need a public Beta? (I favour the
> > former)
>
> What has [collections] done in the past?
The RC1 from memory. We should [though wouldn't] be able to rename the
RC1 if it's good, so the CaseInsensitiveMap bit shouldn't magically appear
in the released version.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [collections] What is left to do for 3.0?
Posted by Phil Steitz <ph...@steitz.com>.
Stephen Colebourne wrote:
> The [collections] CVS has been tidied up prior to a 3.0 release today. The
> CVS now only contains those classes to be released in a 3.0. These are all I
> know of:
>
> - Should PriorityQueue be deprecated? (Buffer effectively replaces it)
+1
>
> - Add CaseInsensitiveMap?
I don't want to hold up the release. If we are actually ready to cut RC1
now, it is probably better to hold off on adding anything new. The class
is trivial, however, so if we expect a little span time between now and
actual release, we might want to add it now.
>
> Do we just RC1 and then release, or do we need a public Beta? (I favour the
> former)
What has [collections] done in the past?
>
> Stephen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org