--- Sam Ruby <[EMAIL PROTECTED]> wrote:
> Morgan Delagrange wrote:
> > 
> > Yes, it's definitely a full-fledged application,
> like
> > Latka and Catcus.  Ripe for promotion, should
> someone
> > volunteer to make it happen, call the vote, help
> with
> > the repackaging, rippling GUMP failures, etc.
> 
> Rippling GUMP failures?  It is not like anything
> which has a dependency 
> on Jelly has seen any any gump builds for months or
> anything.

Absolutely.  That's part of what I'm trying to address
by breaking up the Jelly build into 1) the "core"
library and tags and 2) separate builds for each
additional tag.  That way, when HttpClient snapshot
20021214 has a different interface than 20021208, the
entire GUMP world doesn't suffer.

And that's why I'm only mildly interested in moving
out of commons.  It's a nice-to-have, but we've got
enough problems making Jelly stable in its current
incarnation before we think about repackaging every
single class (a very GUMP-unfriendly act).  I just
want to make it clear that, while I'm willing to
organize a 1.0 release, and while I'm willing to
reorganize Jelly into a more stable series of builds,
I'm not interested in doing the brunt of the
repackaging work if Jelly gets promoted.  In other
words, +0.  :)

> I certainly will help in any way I can, but fter
> that point I really 
> would like to see Jelly manage its dependencies by
> actually taking 
> integration errors seriously and reacting in a
> timely fashion, instead 
> of merely reacting to changes when the possibility
> of a release.
> 
> A chain of dependencies are only as strong as its
> weakest link.

I agree.  I think reorganizing the build will do just
that.  We'll have a core library with a more stable
build.  Whenever that build goes to hell, I believe
the response will be more timely.  At present, you
have the core libraries bundled in with all the tags,
and it doesn't work well.  The core Jelly build should
not fail if any single tag can't build (IIRC the
current build failure is some problem with HttpClient,
which is not a core Jelly dependency).  It's better
for the developers and it's definitely better for the
wide web of GUMP.

> Address that and I would be +1 to a jakarta-jelly.

And I'll be +0.  ;)

> - Sam Ruby
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 


=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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

Reply via email to