Hans Dockter wrote:
>
> On Thu, Dec 17, 2009 at 11:43 AM, tinca <[email protected]> wrote:
>
> ...
>> root project's classpath (at least no reason to think otherwise). The
>> target
>> project's build however can not see it.
>>
>
> Have you checked the content of the jar. To clarify things you could add
> the
> jar explicitly to the buildscript classpath of the build.gradle.
>
> Which version of Gradle are you using?
>
Yes, I have. Every time I change something or have any suspect an empty jar
could be
produced.
gradle version is 0.8.
>> Is there a way to see what classpath is seen by gradle when starting
>> execution of a script?
>>
>
> At the beginning of your script you could write:
>
> gradle.buildScriptClassLoader.getURLs().each { println it }
>
If I understood correctly what is in the user guide, gradle automatically
makes a jar from classes under buildSrc and puts that jar on the classpath
(it is not explicitly written like this, though).
A buildSrc-0.1.jar does exist, has the appropriate content, but is not on
the classpath.
If I remove the buildSrc and turn back to using the plugin separately
compiled and imported by buildscript {} the root script execution does not
even show the classpath URLs (the println is put into the root
gradle.build), but immediately errors. Is that classpath only for buildSrc
execution (the name suggestso)? Is it used further for root script as well?
In a search for the latter I tried
gradle.scriptClassLoaderProvider.classLoader to no avail.
Thanks!
Zsolt
--
View this message in context:
http://old.nabble.com/custom-plugin%27s-class-is-not-found-tp26801277p26827724.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
