A plausible and clever idea, but it doesn't work. Nor did supplying a URLClassLoader with the directory. I'm guessing that there's code somewhere in the new Kodo that just walks the class path property and does its own thing to find the license file.
I did some experimentation with invoking the enhancer from the command line using kodoc. If you put the bea.license file in a directory and add that directory to the classpath, everything works fine. If you put the bea.license file into a jar, at the root: [] jar -tf bea-license.jar META-INF/ META-INF/MANIFEST.MF License.bea ...and put that jar on the classpath, Kodo does not find the license file. So I think I'm back to the original problem: jars won't do it; how do I add an actual directory to a Maven classpath? -----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 02, 2006 3:32 PM To: Maven Users List Subject: Re: How do I add a directory to the classpath visible to a Maven plugin? > Specifically, I am trying to use BEA Kodo 4, the enhancer, and it > appears to require that the directory containing the license.bea file be > on the classpath. >From my understanding stuff on the classpath is treated the same, regardless of whether it came from a jar or a directory. So if you put the license.bea inside a jar file so that it was at the root directory of the archive it should be the same as attaching a directory. Then you could install that archive into your repository as <dependecy> <groupId>com.bea</group <artifactId>kodo</artifactId> <classifier>license</classifier> </dependency> and then users of your plugin would need to have installed into their local repository (or their company internal repository) the license jar. I'm guessing that you might even be able to check that this dependency exists and provide a reasomable error message from your plugin if it doesn't. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
