Skip to content

Maven Build issue #76

Open
Open

Description

@jnsanders1983

@Endolf I am trying to incorporate changes from ccc6d11
we have a hard requirement of hot plug. I am new to maven, so I am not real knowledgeable. What I have managed to do is get the 2.0.9 source code compile with maven via the terminal, and also through Eclipse 2021-09. I incorporated the file changes from the commit mentioned above.

The linux-plugin can't resolve the class DisposableDevice. I could/have fixed this by including the coreAPI in the linux-plugin build path in Eclipse. and it compiles and I can create some test code to test the refreshDefaultControllerEnvironment() method.

But I can't compile this code with maven via the terminal, it fails at compiling coreAPI and I get the following error.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project coreapi: Compilation failure
[ERROR] /home/jdaccs2/eclipse-workspace-2021/jinput-master/coreAPI/src/main/java/net/java/games/input/DefaultControllerEnvironment.java: warnings found and -Werror specified
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project coreapi: Compilation failure
/home/jdaccs2/eclipse-workspace-2021/jinput-master/coreAPI/src/main/java/net/java/games/input/DefaultControllerEnvironment.java: warnings found and -Werror specified

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: Compilation failure
/home/jdaccs2/eclipse-workspace-2021/jinput-master/coreAPI/src/main/java/net/java/games/input/DefaultControllerEnvironment.java: warnings found and -Werror specified

at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1161)
at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:168)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more

we tried removing -Werror from the pom and it gets a little further and says it can't resolve DisposableDevice.

I am sure that there is a build path issue somewhere in one of the poms but, I myself, nor anyone I personally know do not have enough knowledge with maven to begin to solve this issues. I am hoping that you can provide some insight on this. Overall the code changes are not that complicated and they add one new interface and the other files changes either extend or implement that interface.

Thanks.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions