You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/04/30 14:00:13 UTC

[jira] [Closed] (MJAVADOC-490) Aggregate goal fails if artifacts not installed

     [ https://issues.apache.org/jira/browse/MJAVADOC-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MJAVADOC-490.
-----------------------------------
      Assignee: Robert Scholte
    Resolution: Pending Closed

I doubt this is still an issue, {{mvn verify site}} is the standard nowadays. If that doesn't work, please provide a small smaple project so I can reproduce it and if required reopen this ticket.
For now I'll close it.

> Aggregate goal fails if artifacts not installed
> -----------------------------------------------
>
>                 Key: MJAVADOC-490
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-490
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>          Components: javadoc
>    Affects Versions: 2.10.4
>            Reporter: Shannon Carey
>            Assignee: Robert Scholte
>            Priority: Major
>
> Using the javadoc aggregate report causes release:perform to fail if the modules were not already installed into the local repository.
> During release:perform's execution of "deploy site-deploy", when report:aggregate runs it appears to fork executions on all of the reactor modules ("Forking mymodule 0.0.1"). When it gets to a module which has a dependency on another module, it cannot find it locally (since that module has not yet been installed), tries to download it from Nexus, and ultimately fails with "... Could not resolve dependencies for project ... The following artifacts could not be resolved ..."
> The only way I can think of to fix this is to add "install" to the "preparationGoals" of release:prepare so that the modules are already installed before release:perform is run. However, this violates the self-containment of release:perform's deploy build, and is generally confusing and difficult to diagnose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)