Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mvn clean install package -DskipTests is not working #45

Closed
jgaleotti opened this issue May 2, 2019 · 3 comments
Closed

mvn clean install package -DskipTests is not working #45

jgaleotti opened this issue May 2, 2019 · 3 comments

Comments

@jgaleotti
Copy link
Collaborator

jgaleotti commented May 2, 2019

evomaster-client-java-controller fails to compile.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project evomaster-client-java-controller: Error creating shaded jar: duplicate entry: META-INF/services/shaded.com.fasterxml.jackson.databind.Module -> [Help 1]

The stack trace is
Caused by: java.util.zip.ZipException: duplicate entry: META-INF/services/shaded.com.fasterxml.jackson.databind.Module
at java.util.zip.ZipOutputStream.putNextEntry (ZipOutputStream.java:232)
at java.util.jar.JarOutputStream.putNextEntry (JarOutputStream.java:109)
at org.apache.maven.plugins.shade.resource.ServicesResourceTransformer.modifyOutputStream (ServicesResourceTransformer.java:130)
at org.apache.maven.plugins.shade.DefaultShader.shade (DefaultShader.java:133)
at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute (ShadeMojo.java:442)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
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)

@arcuri82
Copy link
Collaborator

arcuri82 commented May 3, 2019

when you build the client, should always use clean.
We have a comment in the doc stating:
Note: if you get an error from the shade-plugin, then make sure to use clean in your Maven commands.

@arcuri82
Copy link
Collaborator

arcuri82 commented Jun 5, 2019

Hi,
any update on this issue?

@jgaleotti
Copy link
Collaborator Author

Hi, I used clean in my maven command and it is working now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants