never mind.... whatever my issue was, it went away. Thought it was weird I was losing my java core libs. And it was - they are back :)
On Fri, Mar 26, 2010 at 11:32 AM, phil swenson <[email protected]> wrote: > Argh. Since I abandoned using ant.java to launch a process in Gradle, > I've been in jar hell. The reason I abandoned it is stdout is hidden > when running gradle, so was advised to use processbuilder.... > > Anyway, this means I need to build the runtime classpath for my calls. > The problem is the normal way of finding the runtime classpath > System.properties["java.class.path"] only pulls back the gradle launch > jar. I have been told that this is what happens when a launching java > via the -jar command. Normally, you get every jar in the classpath > including the java libs like rt.jar. > > So I have build up my runtime classpath now using this line of code: > buildscript.configurations.classpath.each{ cp << it.getCanonicalPath() > } > > However, what I"m missing are the core java libs like rt.jar. So when > I run my external process via ProcessBuilder I now get this error: > javax.xml.xpath.XPath.class not found, which is in rt.jar > > Could someone point me to a good way to find the core and ext java libs? > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
