Adam Murdoch wrote:
>
> A typical approach is to use a custom plugin, which creates the deploy
> task and configures it appropriately. Your plugin would do something like:
> deploy.dependsOn war
>
I'm trying to write a custom task as a temporary solution until somebody
comes up with a better one (The author of the previously mentioned tomcat
plugin says he's working on another plugin to allow you to deploy to an
arbitrary server, for example).
As such, in that file that I posted in my previous message, where would I
put the dependsOn statement? Or would I need to configure that in my
subProjects{} block? Also, in the method def copyWar() how do I make that
be of type:Copy? I'm not a groovy aficionado so I'm learning on the fly
here.
Adam Murdoch wrote:
>
> You could potentially put this code in the task itself, but this does
> couple the task implementation a bit too tightly to your particular
> project and limits your options for reusing the task. This may or may not
> be an issue for you.
>
We're a small shop with a single project tree so this isn't really a problem
in the short term, particularly knowing that somebody is working on
developing a full blown plugin
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Execute-command-line-task-tp4311284p4313413.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
