rather than always invoking the scripts in the same jvm as used to run maven, if you add support for toolchains, you could fork a toolchains defined jvm so that maven can be run from one jvm and the script from another
2010/1/2 Siegfried Goeschl <[email protected]>: > Hi Stephen, > > could you clarify the statement - I think I miss a bit or two .... :-) > > Cheers, > > Siegfried Goeschl > > Stephen Connolly wrote: >> I'd like to see support for toolchains so that you don't have to run >> maven with jdk 6 to use scripting >> >> Sent from my [rhymes with tryPod] ;-) >> >> On 2 Jan 2010, at 16:33, Tomasz Pik <[email protected]> wrote: >> >>> On Fri, Jan 1, 2010 at 12:29 PM, Stefano Fornari >>> <[email protected]> wrote: >>>> Hi All, >>>> I needed a plugin to run JavaScript scripts and I ran into >>>> script-maven-plugin. It looks that id does most of what I need, but I >>>> would need to extend it anyway to allow the evaluation of more than >>>> one script. Looking at the documentation and code, I noticed, it seems >>>> a bit outdated and supports BSF 2.x only. >>>> In the JDK 1.6, JSR223 is implemented and provides already the Rhino >>>> JavaScript engine implementation. I was therefore wondering if it >>>> makes sense at all to develop a script-maven-plugin 2.0 that supports >>>> JSR223 and drops support for BSF (who wants to use BSF engines can >>>> keep using 1.0-SNAPSHOT). I would develop such version and contribute >>>> it to the project if Tomasz is fine with it. The alternative is to >>>> develop a separate plugin, but it would be a pity to fragment this >>>> simple mojo. >>> >>> Yes, go for it. >>> Initially, I've been developing this plugin with groovy in mind >>> and then whole GMaven thing comes... >>> Also, with JDK1.6 being a de facto standard on developer's environments, >>> I think it would be better to use JSR233 instead of BSF. >>> >>> Regards, >>> Tomek >>>> >>>> What do you think? >>>> >>>> Stefano >>>> >>>> -- >>>> Ste >>>> >>> >>> --------------------------------------------------------------------- >>> 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] >> >> >> > > --------------------------------------------------------------------- > 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]
