This is not needed. The Apple VM already has those classes available
by default. What I did is creating an empty jar at the correct
location named tools.jar.
HTH,
Stéphane
On 6/11/07, Siegfried Goeschl [EMAIL PROTECTED] wrote:
I tried it recently with creating a symbolic link for tools.jar
I think what you have done is not considered a best practice in the Maven
world. I would do my best to remove the dependency on tools.jar. There is
no need to use this file.
On 6/12/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
This is not needed. The Apple VM already has those classes
Things like annotation processing with apt requires jdk classes (the
tools.jar) to be available during the build. This is what we do in Trails
for the same problem:
profiles
profile
!-- NOTE: This will not be activated on OS X, since
classes.jaralready has the tools in it.
Hi All,
Discovering the joy of coding Java in a Mac environment I learned that there
is no tools.jar in the Mac version of the JDK.
Consequence is, my projects having dependencies on tools.jar fail to build.
So for the project with a direct dependency, I used Profile successfully.
I created one
What causes your project to have a dependency on tools.jar?
I have been using maven on a mac for a while now and have never had to deal
with the tools.jar.
Nathan
On 6/11/07, Jerome Thibaud [EMAIL PROTECTED] wrote:
Hi All,
Discovering the joy of coding Java in a Mac environment I learned
The deal is that tools.jar is in classes.jar (i think) and is always
on the classpath. If you just exclude the dependency it should work.
On 6/11/07, Nathan Maves [EMAIL PROTECTED] wrote:
What causes your project to have a dependency on tools.jar?
I have been using maven on a mac for a while
The project is not Mac specific, the developers use Windows, Linux etc.
Someone introduced a dependency using the com.sun.tools.javac classes.
rgds
JT
On 6/11/07, Nathan Maves [EMAIL PROTECTED] wrote:
What causes your project to have a dependency on tools.jar?
I have been using maven on a
Are you saying that I can add an exclusion clause in a Profile triggered by
the OS type?
Would it act on the dependencies declared in the build/plugins/plugin
section ?
rgds
JT
On 6/11/07, Gregory Kick [EMAIL PROTECTED] wrote:
The deal is that tools.jar is in classes.jar (i think) and is
I tried it recently with creating a symbolic link for tools.jar pointing
to classes.jar
Cheers,
Siegfried Goeschl
Jerome Thibaud wrote:
Are you saying that I can add an exclusion clause in a Profile triggered by
the OS type?
Would it act on the dependencies declared in the
There might be a better way (or more Maven-ish way) to do it, but a
symbolic link is certainly the simplest.
Wayne
On 6/11/07, Siegfried Goeschl [EMAIL PROTECTED] wrote:
I tried it recently with creating a symbolic link for tools.jar pointing
to classes.jar
Cheers,
Siegfried Goeschl
Jerome
I agree with Gregory,
I would remove the dependency all-together.
Everything should just work.
On 6/11/07, Gregory Kick [EMAIL PROTECTED] wrote:
The deal is that tools.jar is in classes.jar (i think) and is always
on the classpath. If you just exclude the dependency it should work.
On
The symbolic link sounds like a nice trick, I'll try that.
In the meantime, I was expecting something more mainstream.
Also you guys realize that If i remove the dependency to tools.jar, my build
will work on Mac but will stop working on Windows and Linux.
rgds
JT
On 6/11/07, Nathan Maves
put it in a profile with os activation
On 6/11/07, Jerome Thibaud [EMAIL PROTECTED] wrote:
The symbolic link sounds like a nice trick, I'll try that.
In the meantime, I was expecting something more mainstream.
Also you guys realize that If i remove the dependency to tools.jar, my build
will
warning, for some reason the symlink does not work on the intel macs.
here is what I do (tcsh/csh syntax):
setenv JAVABASE /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0
setenv JAVAVERS Home
setenv JAVA_HOME $JAVABASE/$JAVAVERS
if (! -d $JAVA_HOME/jre || ! -r
Jerome Thibaud wrote:
The project is not Mac specific, the developers use Windows, Linux etc.
Someone introduced a dependency using the com.sun.tools.javac classes.
Using Sun's internal implementation classes in JDK v1.6 and above
triggers a compile error. The correct fix is to stop using
15 matches
Mail list logo
