I am trying to use Jelly for a data generation application that does not require Maven. I can run standalone (without Maven) Jelly through a Java class as follows:
JellyContext context = new JellyContext(); context.runScript( resolveURL("script.xml"));
Are there any short comings of using Jelly this way as opposed to using it in conjunction with Maven?
Hetal,
I don't think there's any shortcomings except the obvious fact that you have to master the classpath yourself...
Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
