Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Fedora Linux, Maven 2.0.6
-
Number of attachments :
Description
If have a multi-module project, the javadoc aggregate does not find inter-module dependencies:
pom.xml
| -->module1 |
| -->module2 |
module 1 depends on module 2
The javadoc plugin is added to the build lifecycle attached to the install phase. When I run "mvn install" I get a "Failed to resolve artifact." error message looking for module 2.
Attachments
Issue Links
| This issue relates to: | ||||
| MJAVADOC-137 | javadoc:javadoc always runs as "aggregator" |
|
|
|
| MENFORCER-11 | enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it. |
|
|
|
| This issue is related to: | ||||
| MJAVADOC-116 | Impossible to aggregate javadoc if snapshot never built |
|
|
|
| MJAVADOC-111 | Can't release when I use javadoc aggregate/groups |
|
|
|
| This issue depends upon: | ||||
| MNG-2277 | aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue |
|
|
|
| MNG-3260 | 2.1: aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue |
|
|
|
It appears this issue occurs for any plugin that has
@requiresDependencyResolution
and
@aggregator
So the problem is not with the javadoc plugin itself.