Build error on Win7 x64

[anthony-legay]

Hi ! I just downloaded the package and I ran into a Build error when doing the first mvn clean install.

Here is an extract of the error log :

Command line was: "C:\Program Files\Java\jdk1.7.0_40\jre\..\bin\javadoc.exe" @options @packages

Refer to the generated Javadoc files in 'D:\Divers\Dev\workspace\slick2d-maven\slick2d-core\target\apidocs' dir.

    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: MavenReportException: Error while creating archive:
Exit code: 1 - Le chemin d'accès spécifié est introuvable.
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.command"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.fills"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.geom"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.gui"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.imageout"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.loading"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.muffin"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.openal"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.opengl"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.particles"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.particles.effects"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.state"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.svg"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.tests"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.tests.states"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.tests.xml"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.tiled"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.util"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.util.pathfinding"
javadoc: warning - Multiple sources of package comments found for package "org.newdawn.slick.util.xml"

I just installed a fresh Java jdk 1.7, but it's the 64 bits version, would this be a problem ?

[nguillaumin]

Hi,

Could you paste here the complete log from Maven? There's not enough in this one to find out what went wrong.

Thanks.

[anthony-legay]

I uploaded it to pastebin because it was too long. Sorry.

http://pastebin.com/L79L9uQ4

[nguillaumin]

Thanks,

I'd say there's something wrong with your Maven or Java install. See this line for example:

[WARNING] Unable to find the javadoc version: Exit code: 1 - Le chemin d'accès spécifié est introuvable.
    java version "1.7.0_40"
    Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
    Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

    Command line was:"C:\Program Files\Java\jdk1.7.0_40\jre\..\bin\javadoc.exe" -J-version

It means Maven can't extract the version of the javadoc.exe binary on your system for some reason. That's what causing the build to fail, when it tries to build the Javadoc for the libraries.

Which version of Maven are you using? Maybe an old version that's not compatible with the latest JDKs? I'm running 3.1.0 myself.

I just tried it on 32bit Windows and it works fine (I don't have access to a 64bit Windows machine unfortunately).

[anthony-legay]

That's what I thought... and I didn't understand, because it was able to find the java.exe, on the same location ! It's a bit weird :( I'm runnning Maven 2.x because I use the eclipse maven integration plugin and I think, apparently that it's not compatible with 3.x version, is it ? (I thought m2e stands for maven 2 so...)

I just did the build on my Macbook (much easier with the OSX terminal, no doubt and it worked fine). I will try again tonight on my PC, I'll try to install 32 bits JDK or something.

Thank you for your answer ! I'll tell you if I manage to build it on my PC.

2013/9/24 nguillaumin notifications@github.com

Thanks,

I'd say there's something wrong with your Maven or Java install. See this line for example:

[WARNING] Unable to find the javadoc version: Exit code: 1 - Le chemin d'accès spécifié est introuvable. java version "1.7.0_40" Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

Command line was:"C:\Program Files\Java\jdk1.7.0_40\jre\..\bin\javadoc.exe" -J-version

It means Maven can't extract the version of the javadoc.exe binary on your system for some reason. That's what causing the build to fail, when it tries to build the Javadoc for the libraries.

Which version of Maven are you using? Maybe an old version that's not compatible with the latest JDKs? I'm running 3.1.0 myself.

I just tried it on 32bit Windows and it works fine (I don't have access to a 64bit Windows machine unfortunately).

— Reply to this email directly or view it on GitHubhttps://github.com/nguillaumin/slick2d-maven/issues/5#issuecomment-24989717 .

Anthony LEGAY Ingénieur Développement

Tél. +33(0) 328 328 000 Fax. +33(0) 328 328 329

Sarbacane Software 3 avenue Antoine Pinay Parc d'activité des 4 vents 59510 HEM - FRANCE www.sarbacane.com

[nguillaumin]

What might be happening is that if the Maven version you use is too old, it's expecting the JDK versions strings to contain "Sun" rather than "Oracle", and then it fails to parse it.

Concerning the Eclipse Maven plugin, as far as I know it doesn't rely at all on your external Maven installation, it embeds its own (You can see that in the Maven preferences within Eclipse).

[akiwarheit]

(I thought m2e stands for maven 2 so...)

m2e defaults to using Maven 3.x.x. For what it's worth, I would advise you to install Maven 2.2.1 externally and have your m2e plugin point to it, it can be done under Preferences > Maven > Installations

Also make sure Java is declared in your environment variables? Not sure what the issue is here so I'm just throwing you random fixes to usual stuff.