Is there any reason why the castor plugin doesn't provide 'ready to go' jelly script? What I mean by this is that in order to use the castor plugin you have to write maven.xml that sets properties then calls tags defined within the castor plugin. Isn't the more 'normal' plugin mechanism to define executable jelly script that you configure with properties?
would it be 'nicer' if the castor plugin did something like
javac any java sources
generate sources from an xsd - default from say src/castor/${pom.id}.xsd to target/castor/java
add target/castor/java to compile.src.set
call java:jar to compile and assemble the ${maven.final.name}.jar?
One thing I like about maven is that in general, if you place your sources in default locations, you don't have to write any jelly script or configure anything and the default goal for the plugin will do something sensible.
More than happy to modify / patch the castor plugin if that's what people want.
cheers Nathan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]