[ https://issues.apache.org/jira/browse/MEAR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194816#comment-17194816 ]
Hudson commented on MEAR-278: ----------------------------- Build succeeded in Jenkins: Maven » Maven TLP » maven-ear-plugin » master #14 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-ear-plugin/job/master/14/ > Ear plugin includes the same artifact twice if used without clean > ----------------------------------------------------------------- > > Key: MEAR-278 > URL: https://issues.apache.org/jira/browse/MEAR-278 > Project: Maven Ear Plugin > Issue Type: Bug > Affects Versions: 3.0.1 > Reporter: Fabian Meier > Assignee: Robert Scholte > Priority: Major > Labels: infosupport > Fix For: 3.1.0 > > Attachments: test-ear.zip > > Time Spent: 10m > Remaining Estimate: 0h > > The problem of > https://stackoverflow.com/questions/47436946/maven-ear-plugin-doubled-artifact-when-not-using-clean > still persists. If you rebuild an ear after changing dependency versions, the > new dependencies are included along with the old ones, leading to an > inconsistent ear. The attached Maven project shows this behaviour. It was > first build with "install", where log4j was in version 1.2.8. After changing > the version to 1.2.17, the project was "installed" again, leading to an ear > that contains both log4j versions simultaneously. -- This message was sent by Atlassian Jira (v8.3.4#803005)