Apple has no tools.jar, they just load it into the regular jar. This is why the standard web page
http://maven.apache.org/general.html#tools-jar-dependency has you make a profile. On Tue, Apr 10, 2012 at 1:06 PM, Anders Hammar <[email protected]> wrote: > Most likely there is a system scope dependency pointing at the locally > installed tools.jar. The path is different on Windows (for example) > and Mac OS. Have a look in the pom and look for that dependency. > > System scope dependencies are evil, > /Anders > > On Tue, Apr 10, 2012 at 18:50, Francois Eyl <[email protected]> wrote: >> 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 one. >> >> Here is the full message : >> >> [ERROR] Failed to execute goal on project com.sma.connector.movex: Could not >> resolve dependencies for project >> com.sma.connector.movex:com.sma.connector.movex:jar:2.3.3-SNAPSHOT: Could >> not find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> -> [Help 1] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal on project com.sma.connector.movex: Could not resolve dependencies for >> project com.sma.connector.movex:com.sma.connector.movex:jar:2.3.3-SNAPSHOT: >> Could not find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> at >> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:196) >> at >> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:108) >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258) >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201) >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> at >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> at >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> Caused by: org.apache.maven.project.DependencyResolutionException: Could not >> resolve dependencies for project >> com.sma.connector.movex:com.sma.connector.movex:jar:2.3.3-SNAPSHOT: Could >> not find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> at >> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:170) >> at >> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:171) >> ... 22 more >> Caused by: org.sonatype.aether.resolution.DependencyResolutionException: >> Could not find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> at >> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:412) >> at >> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:164) >> ... 23 more >> Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could >> not find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:541) >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:220) >> at >> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:395) >> ... 24 more >> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not >> find artifact jdk:tools:jar:5.0 at specified path >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/../lib/tools.jar >> at >> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:260) >> ... 26 more >> >> >> java -version : >> java version "1.6.0_31" >> Java(TM) SE Runtime Environment (build 1.6.0_31-b04-414-11M3626) >> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-414, mixed mode) >> >> I know the tools.jar is linked to Oracle compiler (also, I guess one of my >> dependency needs it since I don't), but I can't figure out how to workaround >> this. >> Can somebody help me make this work please? >> >> Thanks, >> Francois >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
