[
https://issues.apache.org/jira/browse/MNG-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284279#comment-16284279
]
Robert Scholte commented on MNG-6300:
-------------------------------------
It was kind of tricky to discover the issue, because it looks like any plugin
interaction might already change the result.
But this seems to be the root cause:
{noformat}
be223808939d75152d7157db33d45f230114555e is the first bad commit
commit be223808939d75152d7157db33d45f230114555e
Author: Anton Tanasenko <atg.sleepl...@gmail.com>
Date: Wed May 18 18:40:28 2016 +0300
Add a ProjectArtifactsCache similar to PluginArtifactsCache
Signed-off-by: Jason van Zyl <ja...@vanzyl.ca>
{noformat}
Must be fixed with the next release.
> 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)
