Re: Declaring a dependency for tools.jar
+1 to Benson, is what we did on Google Doclava[1] to make the build working on Google team's Ubuntu and my Mac. just my 2cents, Simo [1] http://code.google.com/p/doclava/source/browse/trunk/pom.xml http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, Jan 24, 2011 at 11:59 PM, Benson Margulies bimargul...@gmail.com wrote: But if you want to run a build on a Mac, you need the profile so as to turn it off where there is no such file. On Mon, Jan 24, 2011 at 4:38 PM, Mike Calmus m...@calmus.org wrote: You can use this same dependency without using a profile at all. Just add it in like you would any other dependency. So long as the directory exists, it will work just fine. On Mon, 24 Jan 2011 09:15:14 -0800 (PST), Dean Schulze dean_w_schu...@yahoo.com wrote: The FAQ shows the profile below to declare a dependency for tools.jar. This seems to be a problem waiting to happen now that Oracle is the vendor for the official JVM. (A recent update to JDK 1.6 caused problems for Eclipse because Eclipse was expecting a property setting of Sun Microsystems instead of Oracle). If you need tools.jar in the system path shouldn't the profile be activated automatically? What would be the right way to activate this profile all of the time? Thanks. profile iddefault-tools.jar/id activation property namejava.vendor/name valueSun Microsystems Inc./value /property /activation dependencies dependency groupIdcom.sun/groupId artifactIdtools/artifactId version1.5/version scopesystem/scope systemPath${java.home}/../lib/tools.jar/systemPath /dependency /dependencies /profile http://maven.apache.org/general.html#tools-jar-dependency - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Declaring a dependency for tools.jar
The FAQ shows the profile below to declare a dependency for tools.jar. This seems to be a problem waiting to happen now that Oracle is the vendor for the official JVM. (A recent update to JDK 1.6 caused problems for Eclipse because Eclipse was expecting a property setting of Sun Microsystems instead of Oracle). If you need tools.jar in the system path shouldn't the profile be activated automatically? What would be the right way to activate this profile all of the time? Thanks. profile iddefault-tools.jar/id activation property namejava.vendor/name valueSun Microsystems Inc./value /property /activation dependencies dependency groupIdcom.sun/groupId artifactIdtools/artifactId version1.5/version scopesystem/scope systemPath${java.home}/../lib/tools.jar/systemPath /dependency /dependencies /profile http://maven.apache.org/general.html#tools-jar-dependency
Re: Declaring a dependency for tools.jar
You can use this same dependency without using a profile at all. Just add it in like you would any other dependency. So long as the directory exists, it will work just fine. On Mon, 24 Jan 2011 09:15:14 -0800 (PST), Dean Schulze dean_w_schu...@yahoo.com wrote: The FAQ shows the profile below to declare a dependency for tools.jar. This seems to be a problem waiting to happen now that Oracle is the vendor for the official JVM. (A recent update to JDK 1.6 caused problems for Eclipse because Eclipse was expecting a property setting of Sun Microsystems instead of Oracle). If you need tools.jar in the system path shouldn't the profile be activated automatically? What would be the right way to activate this profile all of the time? Thanks. profile iddefault-tools.jar/id activation property namejava.vendor/name valueSun Microsystems Inc./value /property /activation dependencies dependency groupIdcom.sun/groupId artifactIdtools/artifactId version1.5/version scopesystem/scope systemPath${java.home}/../lib/tools.jar/systemPath /dependency /dependencies /profile http://maven.apache.org/general.html#tools-jar-dependency
Re: Declaring a dependency for tools.jar
But if you want to run a build on a Mac, you need the profile so as to turn it off where there is no such file. On Mon, Jan 24, 2011 at 4:38 PM, Mike Calmus m...@calmus.org wrote: You can use this same dependency without using a profile at all. Just add it in like you would any other dependency. So long as the directory exists, it will work just fine. On Mon, 24 Jan 2011 09:15:14 -0800 (PST), Dean Schulze dean_w_schu...@yahoo.com wrote: The FAQ shows the profile below to declare a dependency for tools.jar. This seems to be a problem waiting to happen now that Oracle is the vendor for the official JVM. (A recent update to JDK 1.6 caused problems for Eclipse because Eclipse was expecting a property setting of Sun Microsystems instead of Oracle). If you need tools.jar in the system path shouldn't the profile be activated automatically? What would be the right way to activate this profile all of the time? Thanks. profile iddefault-tools.jar/id activation property namejava.vendor/name valueSun Microsystems Inc./value /property /activation dependencies dependency groupIdcom.sun/groupId artifactIdtools/artifactId version1.5/version scopesystem/scope systemPath${java.home}/../lib/tools.jar/systemPath /dependency /dependencies /profile http://maven.apache.org/general.html#tools-jar-dependency - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
dependency on tools.jar?
I am converting a project to maven, and I have some classes that depend on com.sun.javadoc package, which lives in the tools.jar file in a java install. My maven build is complaining because it can't find that dependency... I would have expected this to be automatically provided by maven, since it is part of the java install. How can I adjust my build to find this jar file? -db - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency on tools.jar?
On Wed, 2004-05-12 at 11:11, David Bock wrote: I am converting a project to maven, and I have some classes that depend on com.sun.javadoc package, which lives in the tools.jar file in a java install. My maven build is complaining because it can't find that dependency... I would have expected this to be automatically provided by maven, since it is part of the java install. How can I adjust my build to find this jar file? project.properties -- maven.jar.override = true maven.jar.tools = /path/to/your/tools.jar project.xml -- project ... dependencies dependency groupIdsun/groupId !-- This is the element used for maven.jar.tools above -- artifactIdtools/artifactId version1.4.2/version /dependency /dependencies /project Alternatively you can use a strategy like use here: http://cvs.plexus.codehaus.org/plexus/plexus-components/native/compiler/src/main/org/codehaus/plexus/compiler/javac/ Just create classloader, pull in the tools jar, load the compiler and go to town. I haven't decided myself what the best approach is. Hope that helps. -db - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]