[ https://issues.apache.org/jira/browse/HBASE-24858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175789#comment-17175789 ]
Josh Elser commented on HBASE-24858: ------------------------------------ Appears that the previous run will have both the unrelocated and the relocated services file in the sources jar {noformat} [DEBUG] Processing JAR /Users/jelser/projects/hbase-thirdparty.git/hbase-shaded-jetty/target/hbase-shaded-jetty-3.4.0-sources.jar [DEBUG] Transforming META-INF/services/org.apache.hbase.thirdparty.org.eclipse.jetty.http.HttpFieldPreEncoder using org.apache.maven.plugins.shade.resource.ServicesResourceTransformer [DEBUG] Transforming META-INF/services/org.eclipse.jetty.http.HttpFieldPreEncoder using org.apache.maven.plugins.shade.resource.ServicesResourceTransformer {noformat} That would explain why a {{clean}} or a fresh-checkout don't suffer from this. > Builds without a `clean` phase fail on hbase-shaded-jetty > --------------------------------------------------------- > > Key: HBASE-24858 > URL: https://issues.apache.org/jira/browse/HBASE-24858 > Project: HBase > Issue Type: Bug > Components: thirdparty > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Minor > > In 3.4.0-rc1 that [~zhangduo] created, I noticed that builds of the project > failed on hbase-shaded-jetty when I did not include {{clean}} in my build > command. > {noformat} > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 3.604 s > [INFO] Finished at: 2020-08-11T14:38:45-04:00 > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project > hbase-shaded-jetty: Error creating shaded jar: duplicate entry: > META-INF/services/org.apache.hbase.thirdparty.org.eclipse.jetty.http.HttpFieldPreEncoder > -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {noformat} > Poking around, it appears that this is actually to do with the creating of > the shaded source jar. -- This message was sent by Atlassian Jira (v8.3.4#803005)