jira-importer commented on issue #573: URL: https://github.com/apache/maven-javadoc-plugin/issues/573#issuecomment-2957336383
**[Brett Randall](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brett_s_r)** commented Sorry I can't provide a test-case project, but this issue appears to have struck a multi-module project here: Apache Maven 2.2.1 (r801777; 2009-08-07 05:16:01+1000) Java version: 1.6.0_16 Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre Default locale: en_AU, platform encoding: UTF-8 OS name: "linux" version: "2.6.31-17-generic" arch: "amd64" Family: "unix" org.apache.maven.plugins:maven-javadoc-plugin:2.6.1 org.apache.maven.plugins:maven-release-plugin:2.0-beta-9 I picked up javadoc 2.6.1 when I linked to a corporate POM. When I overrode this the project's top-level parent POM to go back to javadoc plugin 2.6, the release then succeeds. My failure occured during the mvn release:perform phase of a release, with error message similar to the OP - Javadoc plugin complaining about dependencies. In my case Module B _does_ depend on Module A, with Module A being built before it in the reactor. So this felt like some sort of reactor problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
