[
https://issues.apache.org/jira/browse/MNG-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301428#comment-16301428
]
Hudson commented on MNG-6300:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x #1683 (See
[https://builds.apache.org/job/maven-3.x/1683/])
[MNG-6300] Multi module release creates empty directories in war file
(rfscholte:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=98af937bc6298e82e489b5f0cd3fb0a1c3d37109])
* (edit) maven-core/src/main/java/org/apache/maven/plugin/CacheUtils.java
* (add)
maven-core/src/test/java/org/apache/maven/lifecycle/internal/LifecycleDependencyResolverTest.java
* (edit)
maven-core/src/test/java/org/apache/maven/AbstractCoreMavenComponentTestCase.java
* (add)
maven-core/src/main/java/org/apache/maven/project/artifact/DefaultProjectArtifactsCache.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginDescriptorCache.java
* (add) maven-core/src/test/projects/lifecycle-dependency-resolver/war/pom.xml
* (edit) maven-core/src/main/java/org/apache/maven/RepositoryUtils.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginArtifactsCache.java
* (delete)
maven-core/src/main/java/org/apache/maven/plugin/ProjectArtifactsCache.java
* (add)
maven-core/src/main/java/org/apache/maven/project/artifact/ProjectArtifactsCache.java
* (add) maven-core/src/test/projects/lifecycle-dependency-resolver/pom.xml
* (edit)
maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleDependencyResolver.java
* (delete)
maven-core/src/main/java/org/apache/maven/plugin/DefaultProjectArtifactsCache.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/DefaultPluginRealmCache.java
* (add) maven-core/src/test/projects/lifecycle-dependency-resolver/lib/pom.xml
> 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
> Assignee: Robert Scholte
> 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)
