Yes, the logic seems to blindly build all other modules in the reactor,
IIRC. I wasn't sure of the reasoning for that, and didn't want to incur
too much collateral damage, so I opted to simply keep failing forks from
killing the present build. There's a way to disable this forking, I
believe it's disableOfflineLinks or similar...
On 5/1/10 11:24 AM, Benjamin Bentmann wrote:
John Casey wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-037/
Staging site:
http://maven.apache.org/plugins/maven-javadoc-plugin-2.7/
+1
Regarding MJAVADOC-275: Both the example project and Maven's trunk still
make the plugin output "The goal
'org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc' has not be
previously called for the project" for modules that have no dependency
on the projects being forked by javadoc, e.g. while building maven-model
javadoc tries to build maven-core. That is to says there is still
something fishy in the way other projects are forked. But anyways, at
least version 2.7 does not fail the build because of this.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
