peter reilly wrote:
To embed the config information, the easiest
is to map the info to objects.
Ant introspection is very powerfull and easy
to use for normal java data object.
The problem is that it only works when you know in advance
what the configuration elements are going to be. In this
examp
I want to write a task that allows me to embed XML configuration
information to set up some integration tests using JUnit as a
base.
I can live with a DOM or JDOM to interpret and transform into my
configuration objects. The concept is based on some work I originally
did to extend JUnit for testin
Dominique Devienne wrote:
This is indeed interesting. I do something quite similar for another purpose
(scans a JAR for all classes having a give static method signature, executes
all these methods, gathering the meta-info required, generate a XML file
then stuck into the JAR's META-INF directory).
Currently, if you want to support the JAR Services standard set forth
by Sun, you have to create a file with an interface name in
META-INF/services and list all the implementations.
This can get to become a problem if we are adding and removing classes,
and we forget to update this hand maintained
