Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 works just fine now since args4j no more needs tools.jar. Thanks for your helps. 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 activated when the vendor is 'Sun', and Apple != Sun, so you leave tools.jar out altogether on Apple On Tue, Apr 10, 2012 at 2:32 PM, Francois Eyl wrote: 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 wrote: 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 Hammarwrote: 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 Eylwrote: 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.DefaultProjectDepende
Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 activated when the vendor is 'Sun', and Apple != Sun, so you leave tools.jar out altogether on Apple On Tue, Apr 10, 2012 at 2:32 PM, Francois Eyl wrote: 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 wrote: 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 Hammarwrote: 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 Eylwrote: 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
Re: OSX and Maven Compiler Plugin (tools.jar missing)
That page tells you to only enable tools.jar when a profile is activated, and the profile is only activated when the vendor is 'Sun', and Apple != Sun, so you leave tools.jar out altogether on Apple On Tue, Apr 10, 2012 at 2:32 PM, Francois Eyl wrote: > 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 wrote: >>> >>> 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 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 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
Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 wrote: 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 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 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(DefaultProjectD
Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 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 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 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/
Re: OSX and Maven Compiler Plugin (tools.jar missing)
Hi folks, the last time I created a link Cheers, Siegfried Goeschl On 10.04.12 19:20, Benson Margulies wrote: 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 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 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.s
Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 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 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
Re: OSX and Maven Compiler Plugin (tools.jar missing)
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 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.sona
OSX and Maven Compiler Plugin (tools.jar missing)
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.DefaultArtifact
