[jira] [Created] (MNG-5807) Both classes and shaded jar exposed as dependency from artifact in multimodule build

["Eugene Lucash (JIRA)" <ji...@apache.org>]

Eugene Lucash created MNG-5807:
----------------------------------

             Summary: Both classes and shaded jar exposed as dependency from artifact in multimodule build
                 Key: MNG-5807
                 URL: https://issues.apache.org/jira/browse/MNG-5807
             Project: Maven
          Issue Type: Bug
    Affects Versions: 3.3.1
         Environment: Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T13:10:27-07:00)
Maven home: /usr/local/Cellar/maven/3.3.1/libexec
Java version: 1.8.0_25, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
            Reporter: Eugene Lucash


After upgrade from 3.2.x to 3.3.1 my project experienced build failure.
During multi-module build, where couple of module has dependency on another module. The dependency itself is an annotation processor module which builds shaded all-in-one jar (with relocated dependencies) which becomes main artifact of that module. It worked well in 3.2.x, but in 3.3.1, the dependent modules' classpath receives both shaded and original/classes dependencies.

The dependent module fails to build due to duplicate processor runs (files already generated etc). Interesting is that if I resume build from the failed module (using `-rf`) then it would succeed as only shaded jar will be available then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)