Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Fri, 8 Dec 2017 21:47:00 +0000 (UTC)
From: "Robert Scholte (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13116132.1509785405000.421608.1512769620364@Atlassian.JIRA>
In-Reply-To: <JIRA.13116132.1509785405000@Atlassian.JIRA>
References: <JIRA.13116132.1509785405000@Atlassian.JIRA> <JIRA.13116132.1509785405806@jira-lw-us.apache.org>
Subject: [jira] [Updated] (MNG-6300) Multi module release creates empty
 directories in war file instead of jars
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 08 Dec 2017 21:47:05 -0000


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

Robert Scholte updated MNG-6300:
--------------------------------
    Fix Version/s: 3.5.3

> Multi module release creates empty directories in war file instead of jars
> --------------------------------------------------------------------------
>
>                 Key: MNG-6300
>                 URL: https://issues.apache.org/jira/browse/MNG-6300
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.2
>         Environment: Linux, Oracle java 1.8.0_152
>            Reporter: Andreas Kurth
>            Priority: Critical
>             Fix For: 3.5.3
>
>         Attachments: build.log, mm.zip
>
>
> After updating to maven 3.5.2 we encounter the following reproducible bug with multi module builds.
> If one of the modules is a war module and depends on another module, the dependency module will not be included as a jar file in WEB-INF/lib of the war file, but as an empty directory instead. Non module dependencies will be included correctly.
> This bug does occur when the following conditions are met:
> - running release:prepare/release:perform
> - <distributionManagement><site> element is present, so that release goals are "deploy site-deploy"
> - <reporting> element contains javadoc-maven-plugin
> Please note that when running "mvn install" or "mvn deploy" the resulting war file is ok, while "mvn release:perform" creates corrupt files as described. Also, if javadoc-maven-plugin is not present in <reporting> block, the war file is fine, too.
> I have no idea whether this bug is maven core or rather release-plugin or even javadoc-plugin related, so I file it here. I prepared a minimal self contained example and attach it as mm.zip. To run the example, the following steps are needed:
> {code}
> cd /tmp
> unzip /path/to/mm.zip
> cd mm
> git init
> git add pom.xml mm-lib mm-war .gitignore
> git commit
> mvn release:prepare
> mvn release:perform
> {code}
> After building the resulting corrupt war file can be found here:
> repo/com/example/mm/mm-war/1.0.0/mm-war-1.0.0.war


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)