On Dec 28, 2011, at 9:54 AM, Levi Yourchuck wrote: > What is the "gradle" work around? This issue comes up a lot. > The work around is to do the unsupported thing :) James Carr shows a good example of this on one of his posts: http://blog.james-carr.org/2011/12/06/gradle-tip-startstop-embedded-jetty-for-system-tests/
Longer term... a conversation with Adam 6 months ago revealed the desire to build a rich model around task relationships which includes lifecycle support / conditional support. None of this has been worked on to my knowledge. It's a great idea... just not there yet. > > > On Dec 27, 2011, at 10:03 PM, Peter Niederwieser <[email protected]> wrote: > >> >> Steve Ebersole wrote >>> >>> Is this possible yet? If not, does anyone know the JIRA issue under >>> which that work would get done? >>> >> >> It's possible (call another task's `execute` method) but not officially >> supported. >> >> -- >> Peter Niederwieser >> Principal Engineer, Gradleware >> http://gradleware.com >> Creator, Spock Framework >> http://spockframework.org >> Twitter: @pniederw >> >> >> -- >> View this message in context: >> http://gradle.1045684.n5.nabble.com/Call-a-task-from-another-task-tp5103731p5104415.html >> Sent from the gradle-dev mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
