ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albrecht, Matt" <matt.albre...@zilliant.com>
Subject RE: Splitting up optional.jar
Date Thu, 18 Jul 2002 16:07:21 GMT

1. As for the 'priority' of task naming, Ant could first check external (or
'optional') jars for task definitions, then use the ant-defined tasks as
defaults.  Then it comes down to figuring out how to prioritize these
external jars.

2. Requiring the 'META-INF' can get dangerous unless Ant has near absolute
control over the classloader (i.e. knowing what's in it).  My experiences
with loading META-INF files from JDK 1.1 as resources show that you can only
load one uniquely named resource per classloader.  'ClassLoader.getResource(
String )' was first defined in JDK 1.1, but 'ClassLoader.getResources(
String )' wasn't added until JDK 1.2.

This means that for an Ant 1.x release*, if Ant has explicit control over
loading each external jar, then Ant can parse each jar, but Ant cannot do
much about these resources if these jars are loaded in the default
classloader.

3.

> From: costinm@covalent.net [mailto:costinm@covalent.net]
> Sent: Thursday, July 18, 2002 9:52 AM
> 2 properties file is not bad - META-INF/anttasks.properties, 
> anttypes.properties.

Or perhaps these could be stuffed under a 'META-INF/ant/' directory.


-Matt

* assuming that all Ant 1.x releases must remain JDK 1.1 compat.


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message