Hi Zsolt, On Thu, Dec 17, 2009 at 10:43 PM, tinca <[email protected]> wrote:
> > > Hans Dockter wrote: > > > > On Thu, Dec 17, 2009 at 11:43 AM, tinca <[email protected]> wrote: > > > > ... > > 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. > > ... > > > > > > Hello Hans, > > You were right. After so many looking at, I have finally seen: there was > content, but due to changed output path the jar included that added dir. > Lesson learned. If one to change conventions, better think twice its > effects. > > Thank you! > > Zsolt > I have been through the same a couple of times. I'm wondering what Gradle could do to make debugging easier here. Maybe the debug log could show a list of all classes provided by the buildSrc project. - Hans > -- > View this message in context: > http://old.nabble.com/custom-plugin%27s-class-is-not-found-tp26801277p26835494.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 > > >
