I know little about these tools mentioned recently like Beanshell, OGNL, Groovy, etc. Although I recently downloaded Beanshell and it appears to be a brillant application. It's like writing shell scripts in Java.
Anyway, if Maven moves away from Jelly and into Beanshell (or whatever other "scripting" language) are plugins still use Ant constructs? Tha is, will <javac/> compile source or will it be replaced with some completely other way of compiling? -----Original Message----- From: Stephen Colebourne To: Maven Users List Sent: 1/10/2004 8:17 AM Subject: Re: Scripting [was Simple properties question...] I suspect we would all like to dump jelly ASAP. I've come to realise that my initial problems, and thus opposition, to maven are due to jelly in a large part. And I do find ant fustrating too. What I want to use is a proper java-like (so I don't have to learn anything new) scripting language (so it doesn't need precompiling). I want eclipse/ide integration such that it offers completions just like other coding (so I don't need to go to the website all the time). And I want it to work the way I expect it to first time (as I don't have time to waste) Of course wish lists are easy, and I suspect you wouldn't disagree with the above. As I said, I have no experience with any of the script tools, so I have to leave the judgement to others :-) Stephen maven.javadoc.destdir="target/apidocs" maven.javadoc.sourcedir="src/java" maven.javadoc.private=true maven.javadoc.generate() maven.artifact.deploy-snapshot(maven.javadoc) From: "Jason van Zyl" <[EMAIL PROTECTED]> > Things like Beanshell and OGNL just work. I have never had a single > problem with OGNL which is simply just awesome for dealing with > expressions. And I've rarely had any problems with Beanshell. There > aren't many blog entries about either. Groovy may eventually be good if > it outlasts the hype. The ideas behind Groovy are awesome, I'll wait to > see if the implementation is equally so. > > > This is a decision not to be taken lightly, as maven can't > > afford to get it wrong a second time! > > Well, I'm not too worried about it. Right now I'll take the tool where > it's not a crap shoot what comes out the other end. I've spent an > ungodly number of hours trying to figure out why Jelly contexts that > seem to have popped into existence with no ryhme or reason, why some > classloading mechanism is used, and simply been baffled at what comes > out of Jexl. These things just don't happen with Beanshell and OGNL. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
