Hi Adam,
thanks for this quick reply. I was used to the HelperUtil class, but
I've already took a look at the ProjectBuilder class for testing my
Plugin implementation. The usage of ProjectBuilder for testing custom
tasks is a tiny bit more verbose than using the helperutil class, since
by using HelperUtil, I'ts a one liner to create a task instance.
I will use it more in the next days and may provide some more feedback.
Does anybody else (3party) plugin developer use the ProjectBuilder class?
regards,
René
Am 17.03.11 01:17, schrieb Adam Murdoch:
On 17/03/2011, at 11:06 AM, Rene Groeschke wrote:
Hi there,
When working directly on Gradle the HelperUtil.groovy class is really
helpful for testing Projects and Tasks. Actually, I am working on a
plugin which is a standalone and shipped extra. During the
development I would like to reuse the HelperUtil.groovy class from
Gradle. Is there a way to get this class into the main sourceset. The
simpliest solution I see at the moment is to move this class from
the test to the main sourceset.
any opinions or futher ideas?
The idea is that you should use ProjectBuilder, which is included in
the distribution. Is ProjectBuilder missing something that HelperUtil has?
the createTask
Have a look at the javadoc for ProjectBuilder:
http://gradle.org/1.0-milestone-1/docs/javadoc/org/gradle/testfixtures/ProjectBuilder.html
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
Co-Founder and VP of Engineering, Gradleware Inc. - Gradle Training,
Support, Consulting
http://www.gradleware.com
--
-----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
