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
