You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2004/05/15 06:09:26 UTC
[sandbox] active components?
I'm interested in finding out which parts of sandbox are not active and
which would be worth putting time into getting a release done.
Currently on the Commons site we list these as the active components,
which are actually active and where are they release wise?
attributes
bzip2
chain
compress
convert
email
functor
hivemind - promoted to jakarta
jex
jrcs - left commons (need to confirm, bit unsure on this)
launcher
mapper
messenger
naming - moved to directory project
periodicity
primitives
reflect
resources
sql
threadpool
vfs
Though the navigation lists the following as sandbox projects [and thus we
assume active]. Not quite the same, so a bit of figuring out to do here.
Attributes
Cache
Chain
Clazz
Compress
Convert
Email
Events
Functor
Id
JJar
JRCS
Mapper
Messenger
Resources
Scaffold
SQL
ThreadPool
VFS
Workflow
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Martin Cooper <ma...@apache.org>.
AFAIK, both Chain and Resources are in pretty good shape, and are awaiting
one of their committers to step up to the plate. Unfortunately, we / they
are all pretty busy right now, but I expect that the effort will go in to
getting these promoted and released shortly after Struts 1.2.1 happens.
--
Martin Cooper
On Sat, 15 May 2004, Joe Germuska wrote:
> At 12:09 AM -0400 5/15/04, Henri Yandell wrote:
> >I'm interested in finding out which parts of sandbox are not active and
> >which would be worth putting time into getting a release done.
> >
> >chain
>
> chain is expected to be a core part of Struts 1.3.x; I've been using
> it with Struts for a while and don't know of any reason why it
> couldn't be released, although I don't know the chain code itself
> very well.
>
> >email
>
> I don't think anyone is actively watching over email. I haven't used
> the code myself, but I've looked it over (not too recently) and it's
> probably close to a release.
>
> >resources
>
> I'm not sure at all how close resources is to a release, but it too
> is probably going to be a dependency of Struts 1.3.x.
>
> Joe
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Joe Germuska <Jo...@Germuska.com>.
At 12:09 AM -0400 5/15/04, Henri Yandell wrote:
>I'm interested in finding out which parts of sandbox are not active and
>which would be worth putting time into getting a release done.
>
>chain
chain is expected to be a core part of Struts 1.3.x; I've been using
it with Struts for a while and don't know of any reason why it
couldn't be released, although I don't know the chain code itself
very well.
>email
I don't think anyone is actively watching over email. I haven't used
the code myself, but I've looked it over (not too recently) and it's
probably close to a release.
>resources
I'm not sure at all how close resources is to a release, but it too
is probably going to be a dependency of Struts 1.3.x.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Martin Cooper" <ma...@apache.org>
> > > reflect
> > Never got finished, releatively unlikely to
>
> Just curious - why do you say it's relatively unlikely to be finished?
It seems very low down Robert and My priority list, and I'm not that
convinced about the need. Especially as I no longer support inter commons
dependencies.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Martin Cooper <ma...@apache.org>.
On Sun, 16 May 2004, Stephen Colebourne wrote:
> From: "Henri Yandell" <ba...@generationjava.com>
> > convert
> I've been too busy to put time into this, but I reckon there is definitely a
> need.
>
> > primitives
> Now in commons proper (sandbox version deleted)
>
> > reflect
> Never got finished, releatively unlikely to
Just curious - why do you say it's relatively unlikely to be finished?
--
Martin Cooper
>
> > Clazz
> Completed, but no great demand
>
> > Events
> Needs more work than time available
>
> 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
Re: [sandbox] active components?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Henri Yandell" <ba...@generationjava.com>
> convert
I've been too busy to put time into this, but I reckon there is definitely a
need.
> primitives
Now in commons proper (sandbox version deleted)
> reflect
Never got finished, releatively unlikely to
> Clazz
Completed, but no great demand
> Events
Needs more work than time available
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "Mario Ivankovits" <im...@apache.org>
> I never thought a sandbox component could have a release too, but great
> to see :-)
It can't. Henri means promotion to commons proper, then release ;-) And I
hope that vfs can achieve this, but bear in mind that to do so all your
dependecies must also be properly released.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Mario Ivankovits <im...@apache.org>.
Henri Yandell wrote:
From the point of "commons-vfs":
>Currently on the Commons site we list these as the active components,
>which are actually active and where are they release wise?
>
>bzip2
>
>
the cvs seems empty - maybe moved to compress?
>compress
>
>
this might be a dependency for vfs in the future
>vfs
>
>
Currently again active ;-)
But for sure to early for a release - even if the whole package is in a
really good state - i am new to jakarta and would like to learn
something about the protocols and systems (build, gump, how to
request/upload dependencies) before i am ready to push a release.
And i would like to bring someting in line within the project. There are
many todos in the source which needs some investigation.
I am not sure about a timeframe, but 2-3 months to a release should be
realistic.
I never thought a sandbox component could have a release too, but great
to see :-)
>Though the navigation lists the following as sandbox projects [and thus we
>assume active]. Not quite the same, so a bit of figuring out to do here.
>
>VFS
>
The same as "vfs" - just the wrong(?) case.
I dont know the wish of the original authors - but i vote for "vfs".
-- Mario
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Hi Robert,
thanks for clarifying and continued help :)
I'll do what you proposed...
Cheers,
Oliver
robert burrell donkin wrote:
> hi oliver
>
> releases of sandbox components by the jakarta-common team are forbidden.
> (i believe that - with pmc approval - that slide could release a sandbox
> component for it's own purposes.) so, what's needed is promotion to the
> jakarta commons.
>
> of course, one of the major is that the component has an active
> community to support it and that it's ready for (at least a 0.x)
> release. it's never too early to push for promotion, especially if the
> component is already mature (in a code sense).
>
> you might like to start another thread asking other people what they
> think is required for promotion but i'd say that a good place to start
> would be by adding transaction to the website.
>
> - robert
>
> On 17 May 2004, at 08:23, Oliver Zeigermann wrote:
>
>> Although newly created package transaction is active and actually
>> almost feature complete as it has been factored out from the Jakarta
>> Slide Project. What is involved to make a release or is it pre-mature
>> to think about it now?
>>
>> Oliver
>>
>> Henri Yandell wrote:
>>
>>> I'm interested in finding out which parts of sandbox are not active and
>>> which would be worth putting time into getting a release done.
>>> Currently on the Commons site we list these as the active components,
>>> which are actually active and where are they release wise?
>>> attributes
>>> bzip2
>>> chain
>>> compress
>>> convert
>>> email
>>> functor
>>> hivemind - promoted to jakarta
>>> jex
>>> jrcs - left commons (need to confirm, bit unsure on this)
>>> launcher
>>> mapper
>>> messenger
>>> naming - moved to directory project
>>> periodicity
>>> primitives
>>> reflect
>>> resources
>>> sql
>>> threadpool
>>> vfs
>>> Though the navigation lists the following as sandbox projects [and
>>> thus we
>>> assume active]. Not quite the same, so a bit of figuring out to do here.
>>> Attributes
>>> Cache
>>> Chain
>>> Clazz
>>> Compress
>>> Convert
>>> Email
>>> Events
>>> Functor
>>> Id
>>> JJar
>>> JRCS
>>> Mapper
>>> Messenger
>>> Resources
>>> Scaffold
>>> SQL
>>> ThreadPool
>>> VFS
>>> Workflow
>>> 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
>>
>>
>
>
> ---------------------------------------------------------------------
> 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: [sandbox] active components?
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
hi oliver
releases of sandbox components by the jakarta-common team are
forbidden. (i believe that - with pmc approval - that slide could
release a sandbox component for it's own purposes.) so, what's needed
is promotion to the jakarta commons.
of course, one of the major is that the component has an active
community to support it and that it's ready for (at least a 0.x)
release. it's never too early to push for promotion, especially if the
component is already mature (in a code sense).
you might like to start another thread asking other people what they
think is required for promotion but i'd say that a good place to start
would be by adding transaction to the website.
- robert
On 17 May 2004, at 08:23, Oliver Zeigermann wrote:
> Although newly created package transaction is active and actually
> almost feature complete as it has been factored out from the Jakarta
> Slide Project. What is involved to make a release or is it pre-mature
> to think about it now?
>
> Oliver
>
> Henri Yandell wrote:
>
>> I'm interested in finding out which parts of sandbox are not active
>> and
>> which would be worth putting time into getting a release done.
>> Currently on the Commons site we list these as the active components,
>> which are actually active and where are they release wise?
>> attributes
>> bzip2
>> chain
>> compress
>> convert
>> email
>> functor
>> hivemind - promoted to jakarta
>> jex
>> jrcs - left commons (need to confirm, bit unsure on this)
>> launcher
>> mapper
>> messenger
>> naming - moved to directory project
>> periodicity
>> primitives
>> reflect
>> resources
>> sql
>> threadpool
>> vfs
>> Though the navigation lists the following as sandbox projects [and
>> thus we
>> assume active]. Not quite the same, so a bit of figuring out to do
>> here.
>> Attributes
>> Cache
>> Chain
>> Clazz
>> Compress
>> Convert
>> Email
>> Events
>> Functor
>> Id
>> JJar
>> JRCS
>> Mapper
>> Messenger
>> Resources
>> Scaffold
>> SQL
>> ThreadPool
>> VFS
>> Workflow
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [sandbox] active components?
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Although newly created package transaction is active and actually almost
feature complete as it has been factored out from the Jakarta Slide
Project. What is involved to make a release or is it pre-mature to think
about it now?
Oliver
Henri Yandell wrote:
> I'm interested in finding out which parts of sandbox are not active and
> which would be worth putting time into getting a release done.
>
> Currently on the Commons site we list these as the active components,
> which are actually active and where are they release wise?
>
> attributes
> bzip2
> chain
> compress
> convert
> email
> functor
> hivemind - promoted to jakarta
> jex
> jrcs - left commons (need to confirm, bit unsure on this)
> launcher
> mapper
> messenger
> naming - moved to directory project
> periodicity
> primitives
> reflect
> resources
> sql
> threadpool
> vfs
>
> Though the navigation lists the following as sandbox projects [and thus we
> assume active]. Not quite the same, so a bit of figuring out to do here.
>
> Attributes
> Cache
> Chain
> Clazz
> Compress
> Convert
> Email
> Events
> Functor
> Id
> JJar
> JRCS
> Mapper
> Messenger
> Resources
> Scaffold
> SQL
> ThreadPool
> VFS
> Workflow
>
>
> 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: [sandbox] active components?
Posted by Oliver Zeigermann <oz...@c1-fse.de>.
Right now the code for persisting sequences is in the transaction
package along with other code that transactionally modifies files.
Should we move it into the Id project or should we try to release both
packages along and have Id use Transation?
Still wondering...
Oliver
Tim Reilly wrote:
>>Id
>
>
> Id is active. In terms of a release... we have some work to do on uuid
> stability and changing the api to match with jdk 1.5. The other identifiers
> have a longer history and spun-off from lang. Oliver Zeigermann has proposed
> some new work on sequence persistence. After that I'd imagine a release
> would be possible, but I don't have a set time-line in mind (except I need
> to get off my rear and get the uuid stuff square.)
>
> Thanks,
> -TR
>
>
>
> ---------------------------------------------------------------------
> 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: [sandbox] active components?
Posted by Tim Reilly <ti...@consultant.com>.
> Id
Id is active. In terms of a release... we have some work to do on uuid
stability and changing the api to match with jdk 1.5. The other identifiers
have a longer history and spun-off from lang. Oliver Zeigermann has proposed
some new work on sequence persistence. After that I'd imagine a release
would be possible, but I don't have a set time-line in mind (except I need
to get off my rear and get the uuid stuff square.)
Thanks,
-TR
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [sandbox] active components?
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Henri Yandell [mailto:bayard@generationjava.com]
>
> This definitely sounds like a worry.
>
> Our site has informally released the snapshot versions as
> (effectively) an alpha release. Is Spring dependent on these
> versions too?
As far as I know, Spring is using the snapshot version from just
before they released 1.0 of Spring framework.
> Documentation looks good. Do you have a roadmap for finishing that?
No. I can get one done, though, and get back to you.
> What future does Attributes have with the 1.5 Annotations? Do
> they replace it, or is it still viable then? [I suspect that
> is FAQ-worthy].
Definitely FAQ-worthy, that one. Will include it.
Short answer is that Attributes is a stop-gap measure until
1.5 is commonly used. Given that it is only about now that
people even are starting to debate requiring 1.4 for their
projects means that the gap may be there for some time.
In short: I expect 1.5 Annotations to become the standard
when 1.5 becomes the standard.
> Do you need any help anywhere?
If you could read the docs and send me a list of all the
questions and/or any critique that popped up in your head.
I frequently find that my idea of what a user is looking
for in the docs and what they actually are looking for are
at odds. (See question of Attributes vs. 1.5 Annotations.)
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [sandbox] active components?
Posted by Henri Yandell <ba...@generationjava.com>.
This definitely sounds like a worry.
Our site has informally released the snapshot versions as (effectively) an
alpha release. Is Spring dependent on these versions too?
Documentation looks good. Do you have a roadmap for finishing that?
What future does Attributes have with the 1.5 Annotations? Do they replace
it, or is it still viable then? [I suspect that is FAQ-worthy].
Do you need any help anywhere?
On the subject of community, I think you've got the right answer. For a
smaller number of active developers, documentation needs to take up any
slack. I don't think the active developer size should stop us from
recognising the reality that a release is needed.
Hen
On Sat, 15 May 2004, Leo Sutic wrote:
>
>
> > From: Henri Yandell [mailto:bayard@generationjava.com]
> >
> > I'm interested in finding out which parts of sandbox are not
> > active and which would be worth putting time into getting a
> > release done.
> >
> > Currently on the Commons site we list these as the active
> > components, which are actually active and where are they release wise?
> >
> > attributes
>
> Attributes is active. Release-wise its in a bit of a bind - I
> know that it is used by people - for example in the Spring Framework
> (www.springframework.org). If each downloader of Spring can be
> considered a user, then attributes has over 10,000 users. Of course
> this statistic is 50-75% made up, but I'd be surprised if it
> has less than ten users.
>
> However, this has not resulted in a community of *developers*,
> making attributes one of those projects that don't quite
> live up to the Apache standards. There's me, but that's
> all.
>
> In defense of this state, it appears that attributes does
> pretty much everything people want it to do, and so there is
> little reason for anyone to dive in.
>
> Relase-wise I'm now focusing on writing documentation,
> not putting new features in.
>
> A release would be great, especially for the spring people,
> but I don't know if it is possible due to the lack of developers.
>
> /LS
>
>
> ---------------------------------------------------------------------
> 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: [sandbox] active components?
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Henri Yandell [mailto:bayard@generationjava.com]
>
> I'm interested in finding out which parts of sandbox are not
> active and which would be worth putting time into getting a
> release done.
>
> Currently on the Commons site we list these as the active
> components, which are actually active and where are they release wise?
>
> attributes
Attributes is active. Release-wise its in a bit of a bind - I
know that it is used by people - for example in the Spring Framework
(www.springframework.org). If each downloader of Spring can be
considered a user, then attributes has over 10,000 users. Of course
this statistic is 50-75% made up, but I'd be surprised if it
has less than ten users.
However, this has not resulted in a community of *developers*,
making attributes one of those projects that don't quite
live up to the Apache standards. There's me, but that's
all.
In defense of this state, it appears that attributes does
pretty much everything people want it to do, and so there is
little reason for anyone to dive in.
Relase-wise I'm now focusing on writing documentation,
not putting new features in.
A release would be great, especially for the spring people,
but I don't know if it is possible due to the lack of developers.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org