Should dependencies for Ant tasks, such as code generators, be declared as runtime dependencies for a project? It makes the portability of an Ant task problematic. I thought the Magic plugins were going to provide the same functionality as Ant tasks, just with resource and dependency help. It would be nice if I could declare dependencies for a plugin and get the runtime depenencies for it like so: <xpath id="path" key="plugin-name"/>
Where should classes that get generated by code generators end up if they aren't going to be edited. Do they belong in "src/main"? I was thinking more like "src/gen". If that were the case, I would need the ability to add another source directory to the Javac task.
- Cameron
Stephen McConnell wrote:
Updated MagicPath.java is attached. This fixes the problem of non-downloading of resources referenced in external paths - the update also improves the handling of the path content.
Example 1: Create an ant path composed of the transitive runtime dependencies for the current project.
<xpath id="path"/>
Example 2: Create an ant path composed of the target artifact and its full transitive runtime dependencies.
<xpath id="path" key="avalon-meta-tools"/>
I'm updated dpml now so you can either do an 'ant setup' or jump down to tools/magic, update MagicPath.java and do 'ant update'.
Cheers, Steve.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
