Re: Magic 1st Spell Demo: Unrecognized rooot element [system]

Niclas Hedhman wrote:

> Really cool!  Magic, IMHO, is more promising for ASF and many 
> commercial projects/products, than Maven (v1 or v2 doesn't matter).
> BUT, we will NEED user feedback. What works, what doesn't, what should 
> be added, and what should be left out.

> OTOH, Magic (if I get to influence enough) will NOT be everything for 
> everyone. But here is the beauty, if you have very special needs, just 
> insert more Ant targets in the build.xml...

The most useful par of Magic I see is dealing with the 
library/dependency hell.  What is the best way to reference 
libraries/resources that are managed by Magic from within a build file?  
It would be nice if you could name the dependency tags and reference 
them as classpathref or filesets from within the Ant build.  That would 
be handy for custom Ant tasks and when populating WAR files.  What 
variables/classpaths/filesets does Magic define that are usable within 
an Ant build file?

What is the best way to use a custom Ant task?  Should it be wrapped in 
a plugin?  What is the best way to add this Hibernate Ant task, for example:

<target name="hbm2ddl" description="Generates database schema with 
hbm2ddl.">
    <taskdef name="hbm2ddl"
        classname="net.sf.hibernate.tool.hbm2ddl.SchemaExportTask">
        <classpath refid="???"/>
    </taskdef>
    <hbm2ddl
        config="hibernate.cfg.xml"
        quiet="yes" text="yes" drop="no" delimiter=";"
        output="target/database-schema.sql"/>
</target>

--
Cameron Taggart