Re: [SURVEY] Commons-URI or not? - jarring or ... and exposing some classes?

[Sung-Gu <je...@apache.org>]

I'd like to consider the compelete opposite situation.

If a project (knows what they exactly need) wanted just several classes from
another project,
should they include a whole jar from the project?   What's the possbile
solution?

Here you are, my one...
You can notice there are xxx.md5, xxx.asc xxx.tar.gz and xxx.zip at
http://www.apache.org/dist/jakarta/commons/xxxx
How about exposing some classes files at
http://www.apache.org/dist/jakarta/commons/xxxx/classes?
Is it nonsense with ant from net?   They might be jarred as 'an only jar' in
build.xml of antother project

Hmmm...  Just my simple thought... your opinion please...

Sung-Gu


----- Original Message ----- 
From: "Craig R. McClanahan" <cr...@apache.org>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Cc: "Commons HttpClient Project" <co...@jakarta.apache.org>
Sent: Thursday, June 26, 2003 2:06 AM
Subject: Re: [SURVEY] Commons-URI or not?


>
>
> On Wed, 25 Jun 2003, Eric Johnson wrote:
>
> > [snip]
> > One of the negatives that others have mentioned on the HttpClient list
> > is the growing dependency problem within the Apache projects,
> > particularly with the myriad of dependencies on commons projects, and
> > among the commons projects themselves.  Perhaps what we need to do is
> > start clumping some of the commons projects together, as well as having
> > the stand-alone pieces we have now.  A first cut at combining some of
> > the commons projects into one giant JAR might include:
> >
>
> Have a look at the build.xml file in the "combo" subdirectory of the
> jakarta-commons CVS repository -- it lets you do exactly this sort of
> thing, and even lets you pick the versions you want (by virtue of
> specifying the CVS tags to build with).
>
> I try to maintain the "latest official release" CVS tag of all released
> commons packages (but nothing from the sandbox, since by definition they
> are not released), but don't always have a chance to do so in a timely
> manner -- others are welcome to help.
>
> Craig McClanahan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
commons-httpclient-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