> Yes, there is an easier way. Implement a custom task to which you'll
> pass a path to plugin.xml and a name for a path.
Finaly, the more I look at the ant code for plugins the more I think we must
redesign it.
In the actual ant scripts, each plugin is a ant project, so there is no way
to define ant dependencies between plugins.
(=> if you compile a plugin A that depends on another one (B), you must
manually compile B before compiling A => we loose one of the major ant
benefit)
I suggest to define each plugin as a target, so that we can define someting
like:
<target name="protocol-httpclient" depend="lib-http,lib-commons-httpclient">
and then automatically extracts dependencies from plugin.xml with something
like:
<xmlproperty file="plugin.xml"/>
<target name="protocol-httpclient" depend="${plugin.requires.import
(plugin)}">
....
</target>
Any comment is welcome.
Jérôme
--
http://motrech.free.fr/
http://www.frutch.org/
