Bryan Loofbourrow wrote:
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?
Could the build-helper help you:
http://mojo.codehaus.org/build-helper-maven-plugin/
?
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
