In which case that would make sense since I didn't have time to update my environments yet to the latest milestone. However, JavaExec worked immediately and it may be more appropriate for my purposes.
On Mon, May 2, 2011 at 4:09 PM, Ladislav Thon <[email protected]> wrote: > Thanks, Ladislav and Adam, for your quick response. Turns out the >> application plugin will work...as long as the maven plugin isn't present >> (which in my case they'll both be required). Appears to be a naming >> collision issue on the "install" task: > > > I think that was solved in 1.0-milestone-3. At least according to > http://wiki.gradle.org/display/GRADLE/Gradle+1.0-milestone-3+Breaking+Changes, > the 'install' task in 'application' plugin was renamed to 'installApp' (but > I didn't have time to try yet). > > LT > > >> >> Cause: Cannot add task ':install' as a task with that name already exists. >> >> I'll take a look at JavaExec next. >> >> >> On Mon, May 2, 2011 at 2:38 PM, Adam Murdoch <[email protected] >> > wrote: >> >>> >>> On 03/05/2011, at 6:27 AM, Russ Rollins wrote: >>> >>> I've been thinking about several Gradle projects that I have on the >>> horizon and wondering about creating a task/plugin common to the projects >>> that would: >>> 1. define a specific set of compile and runtime dependencies >>> 2. compile the code (groovy, scala, java) >>> 3. execute a main() on one of the compiled classes with the appropriate >>> classpath as defined in step #1 >>> >>> >>> You might look at the application plugin for this: >>> http://gradle.org/current/docs/userguide/application_plugin.html >>> >>> Alternatively, you could use the JavaExec task in your plugin: >>> http://gradle.org/current/docs/dsl/org.gradle.api.tasks.JavaExec.html >>> >>> >>> -- >>> Adam Murdoch >>> Gradle Co-founder >>> http://www.gradle.org >>> VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting >>> http://www.gradleware.com >>> >>> >> >
