You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephen McConnell <mc...@osm.net> on 2002/07/28 01:24:06 UTC
excalibur manifest declaration issue
Following on from some discussion with the James group I was checking
into depedencies they have with Avalon - and in particular - attempting
to seperate this in terms of Framework, Excalibur package XXX, Phoenix,
and Phoenix Block XXX.
One the james members provided me with a short-list of excalibur
depedencies:
org.apache.avalon.excalibur.io.*
org.apache.avalon.excalibur.thread.*
org.apache.avalon.excalibur.datasource.*
org.apache.avalon.excalibur.collections.*
When looking at the manifest declarations for the excalibur components
for io, thread, datasource and collections, I noticed that none contain
the declarations of the extensions they are depedendent on. As the
manifest files in Excalibur are (generally) created automatically, can
the procedure be extended to include generation of extension depedencies ?
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: excalibur manifest declaration issue
Posted by Peter Donald <pe...@apache.org>.
On Sun, 28 Jul 2002 09:24, Stephen McConnell wrote:
> Following on from some discussion with the James group I was checking
> into depedencies they have with Avalon - and in particular - attempting
> to seperate this in terms of Framework, Excalibur package XXX, Phoenix,
> and Phoenix Block XXX.
>
> One the james members provided me with a short-list of excalibur
> depedencies:
>
> org.apache.avalon.excalibur.io.*
> org.apache.avalon.excalibur.thread.*
> org.apache.avalon.excalibur.datasource.*
> org.apache.avalon.excalibur.collections.*
>
> When looking at the manifest declarations for the excalibur components
> for io, thread, datasource and collections, I noticed that none contain
> the declarations of the extensions they are depedendent on. As the
> manifest files in Excalibur are (generally) created automatically, can
> the procedure be extended to include generation of extension depedencies ?
Checkout the jarlib-* tasks in ant1.5 which is intended to do this sort of
thing
--
Cheers,
Peter Donald
----------------------------------------------
Money is how people with no talent keep score.
----------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>