You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2020/09/12 17:52:00 UTC

[jira] [Issue Comment Deleted] (MEAR-278) Ear plugin includes the same artifact twice if used without clean

     [ https://issues.apache.org/jira/browse/MEAR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MEAR-278:
-------------------------------
    Comment: was deleted

(was: Sehr geehrte Damen und Herren,

ich bin ab 15. Juni wieder im Haus.

Viele Grüße
Fabian Meier (ik3-mv)
)

> 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)