tag:blogger.com,1999:blog-3821115221571460038.post9038156402701573604..comments2011-12-30T20:27:32.127-08:00Comments on Shanks' Tech Musings: JMockit & JavaAgent - Enterprise integration woesShankar Vasudevannoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3821115221571460038.post-55996914124932605022010-02-01T18:00:47.451-08:002010-02-01T18:00:47.451-08:00Note that the "discoverPathToJarFile" me...Note that the "discoverPathToJarFile" method has a fallback mechanism which takes the path to the jmockit jar file from the classpath.<br />So, my first attempt to avoid the exception "IllegalArgumentException: URI has an authority component" would be changing "String jarFilePath = discoverPathToJarFile();" to "String jarFilePath = findPathToJarFileFromClasspath();". This should work even with a remote file (it works in a regular environment).<br /><br />If you can test this in your CI environment and confirm it does work, I could remove the problematic "new File(jarFileURI)" code from the next version of JMockit.Rogeriohttp://www.blogger.com/profile/17185104709482425736noreply@blogger.com