This will require you to write a plugin and venture into scary land! On 28 June 2012 11:58, Stephen Connolly <[email protected]> wrote: > Sorry mis-read... nope you can't do that... > > You could probably do some hook with toolchains to fork a maven > instance with the JDK pulled from toolchains though > > On 28 June 2012 11:57, Stephen Connolly <[email protected]> > wrote: >> Toolchains is the maven way for such >> >> On 27 June 2012 17:28, Bodhayan Chakraborty <[email protected]> wrote: >>> Hi, >>> >>> I want to execute a maven plugin with a defined JDK irrespective of the JDK >>> that invoked the "mvn" command. I have developed a plugin which invokes a >>> API. That API can run only in 32 bit java. The goal for that plugin is >>> "store:store". So, if I execute "mvn clean compile deploy store:store", the >>> "clean", "compile" and "deploy" goals should run in the same JVM which >>> invoked the "mvn" command. But, the "store:store" should run in a different >>> JVM. Is that possible? >>> >>> Thanks in advance. >>> >>> Bodhayan.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
