[MRELEASE-926] Multi project release fails if site declared in pom.xml

[jira-importer]

Nicolai Marck Ødum opened MRELEASE-926 and commented

I can do
mvn release:prepare
mvn release:perform

If i include
<site>
<id>site</id>
<name>My site server</name>
<url>scpexe://mysite.com/var/www/html</url>
</site>

in the parent pom I can do a
mvn release:prepare
but mvn release:perform fails

[INFO] [INFO] Reactor Summary:
[INFO] [INFO]
[INFO] [INFO] My parent .......................................... FAILURE [ 7.363 s]
[INFO] [INFO] common ............................................. SKIPPED
[INFO] [INFO] Web Application Project ............................ SKIPPED
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 7.723 s
[INFO] [INFO] Finished at: 2015-10-13T11:06:32+02:00
[INFO] [INFO] Final Memory: 32M/393M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project my-parent: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on project my-webapp: Could not resolve dependencies for project example:my-webapp:war:1.0.9: Could not find artifact example:my-common:jar:1.0.9 in repo (https://myrepo.com/content/groups/public/)

---

Affects: 2.5.2

Attachments:

• example.tar.gz (3.22 kB)
• result.txt (211.67 kB)

1 votes, 4 watchers

[jira-importer]

Nicolai Marck Ødum commented

Simple example that illustrate the problem

[jira-importer]

Michael Osipov commented

This demo project is pointless because it runs in your environment (Nexus, Subversion) only. Rather add debug output and remove sensitive information.

[jira-importer]

Nicolai Marck Ødum commented

Result of:

/usr/share/apache-maven-3.3.3/bin/mvn -X release:perform > /tmp/result.txt

[jira-importer]

Karl Heinz Marbaise commented

The example project does not work, cause it contains a dependency example:my-common:1.0.10-SNAPSHOT which is not part of the example and which fails a simple smoke test (mvn clean package)...

The example result.txt contains the same issue: {[INFO] Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project my-webapp: Could not resolve dependencies for project example:my-webapp:war:1.0.19: Could not find artifact example:my-common:jar:1.0.18 in my_repo (https://myrepo.com/content/groups/public/)} ...

[jira-importer]

Karl Heinz Marbaise commented

The problem in your example is the dependency which could not be found:

example:my-webapp:war:1.0.9: Could not find artifact example:my-common:jar:1.0.9 in ...

which fails the build.

[jira-importer]

Nicolai Marck Ødum commented

You are right - but my-common artifact is released too in the process because it's declared as a module in the parent pom.I have done some more research into this and it boils down to the javadoc aggregate report.
I am able to make it work if I include

<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.3</version>
<reportSets>
<reportSet>
<id>default</id>
<reports>
<report>javadoc</report>
<report>test-javadoc</report>
</reports>
</reportSet>
<reportSet>
<id>aggregate</id>
<reports />
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>

The Documentation from javadoc plugin https://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html says

<reportSet>
<id>aggregate</id>
<configuration>
<!-- Specific configuration for the aggregate report -->
...
</configuration>
<reports>
<report>aggregate</report>
</reports>
</reportSet>
So is it possible for release plugin to deploy the artifacts defined by modules first before it calls the javadoc:aggreate goal ?

[jira-importer]

Nicolai Marck Ødum commented

This is a problem related to javadoc:aggregate and modules that are released as part of the parent pom release.

[jira-importer]

Sébastien Piller commented

I have the same issue with a multi-module project.

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project myproj-parent: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal on project submodule: Could not resolve dependencies for project com.acme:submodule:jar:7.0.0-RC01: Could not find artifact com.acme:othersubmodule:jar:7.0.0-RC01

The weird thing is it happens not in every project, but only one. I can't find what is going on, the logs are not very usefull, but I keep searching...

Same structure, same parent-pom, same JDK/Maven/Plugins etc. version, and two behaviors ...

Any workaround or explaination will be greatly appreciated!