On 15/05/2011, at 2:20 AM, phil swenson wrote: > Your code might work, but it doesn't solve my real problem..... > > Let me give a little context. This example is me breaking down a > complex problem to it's simplest form. I have legacy java code that I > am calling from a gradle plugin. This legacy code is widely used > across 1000s of people and dozens of projects, so I would like to > avoid modifying it. My unit tests on the gradle plugin all work fine, > but when I call my plugin task from gradle itself I get this > ClassNotFoundException from deep inside this legacy code.
Do you have a stacktrace for this exception? -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
