hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-13300) maven-jar-plugin executions break build with newer plugin
Date Mon, 20 Jun 2016 22:33:57 GMT
Christopher Tubbs created HADOOP-13300:

             Summary: maven-jar-plugin executions break build with newer plugin
                 Key: HADOOP-13300
                 URL: https://issues.apache.org/jira/browse/HADOOP-13300
             Project: Hadoop Common
          Issue Type: Improvement
          Components: build
            Reporter: Christopher Tubbs

Several places throughout the Hadoop build (going back at least as far as 2.4.1; I didn't
check earlier), extra executions of maven-jar-plugin have been used to create jars at different
phases in the build lifecycle.

These have typically not specified an execution id, but should have specified "default-jar"
to override the default execution of maven-jar-plugin. They have worked in the past because
maven-jar-plugin didn't check to verify if an artifact was built/attached multiple times (without
using a classifier), but will not work when a newer version of maven-jar-plugin is used (>3.0),
which is more strict about checking.

This is a problem for any downstream packagers which are using newer versions of build plugins
(due to dependency convergence) and will become a problem when Hadoop moves to a newer version
of the jar plugin (with ASF Parent POM 18, for example).

[These are the ones I've found|https://lists.apache.org/thread.html/2c9d9ea5448a3ed22743916d20e40a9e589bfa383c8ea65f35cb3f0d@%3Cuser.hadoop.apache.org%3E].

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message