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

["Tibor Digana (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MJAVADOC-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425859#comment-16425859 ] 

Tibor Digana commented on MJAVADOC-490:
---------------------------------------

My assembly plugin is not able to find jar file however it exists and my issue happens even without release plugin. It is enough to run
{{install post-site -Dwagon.webdav.continueOnFailure=true -P release,generate-ddl -e -DskipTests -DskipITs}}
I use {{install}} many times. So my issue is not related to missing jar file in local repo. It is more about something weird in MavenProject model in combination with {{javadoc:aggregate}} which runs within site reporting and {{assembly}} plugin which has {{assembly.xml}}:

{code:xml}
    <dependencySets>
        <dependencySet>
            <outputDirectory>WEB-INF/lib</outputDirectory>
            <useProjectArtifact>true</useProjectArtifact>
            <useTransitiveFiltering>false</useTransitiveFiltering>
            <scope>test</scope>
            <includes>
                <include>*:audit-domain:jar:without-validation</include>
            </includes>
        </dependencySet>
    </dependencySets>
{code}


> 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
>            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
(v7.6.3#76005)