+0 But I must agree with Brett here. It should not take that much time to create a execute:java goal, and I really think the executeplugin should have one.
/Kaare On 09/03/06, Brett Porter <[EMAIL PROTECTED]> wrote: > +0.5 > > I'm confused by the <classpath> element in the middle of the arguments, > especially in light of what the TODO says. > > If you are going to have a classpath, why not have a mojo for exec:java? > With... > > <configuration> > <options /> -> stuff before the mainClass > <systemProperties /> -> special case of above > <mainClass /> -> not required with mainJar > <mainJar /> -> java -jar ... > <classpath /> > <arguments /> -> args after the mainClass (args[]) > </configuration> > > My 2 cents. Not a blocker, but I really think the classpath thing above > is confusing. > > - Brett > > jerome lacoste wrote: > > Hi everyone, > > > > Apparently the exec-maven-plugin is referenced from a not yet > > published m2 book and needs to be available from a repository before > > the book gets out. > > > > The plugin has been available 5 weeks as snapshot and I didn't see any > > reported problems/enhancements requests since. To my knowledege the > > only Jira issue in mojo-sandbox that references exec in its > > description is http://jira.codehaus.org/browse/MOJO-34, but it's not > > directly related to the plugin. > > > > So.. as there doesn't seem to be any show stopper, I would like to > > graduate the plugin from the sandbox and make a first official 1.0 > > release (skipping any form of beta). > > > > I'll open up the vote for 72h, then provide a summary > > > > +1 from me > > > > J > > >
