Ok guys, I sorted it out!
In fact my project was using the args4j library (2.0.10), this lib had a
dependency to tools.jar. As the profile solution was not working for me
(guess because it was a dynamic dependency), I finally ended up with
upgrading the args4j lib to 2.0.16 and everything
Hi guys,
I'm facing to a strange issue with the maven-compiler-plugin on my OSX
system while the same project/pom work fine on windows and linux. For
some reason the plugin tries to access the tools.jar in a directory that
doesn't exist on OSX since I'm not using the Oracle JVM but the Apple
I've seen that documentation page before, but what I'm supposed to do,
since the page tells the tools.jar is already included on OSX?
Thanks guys,
Francois
Le 10/04/12 19:20, Benson Margulies a écrit :
Apple has no tools.jar, they just load it into the regular jar. This
is why the standard
Ok I see, you make a symbolic link on classes.jar right?
I guess there is a cleaner way to achieve this with maven?
Thanks,
Francois
Le 10/04/12 20:23, Siegfried Goeschl a écrit :
Hi folks,
the last time I created a link
Cheers,
Siegfried Goeschl
On 10.04.12 19:20, Benson Margulies
Understand - I've try to put this code to my pom.xml. But got the same
result, keeps to lookup for that tools.jar.
Any thoughts?
Thanks,
Francois
Le 10/04/12 20:46, Benson Margulies a écrit :
That page tells you to only enable tools.jar when a profile is
activated, and the profile is only
