[jira] (MJAVADOC-369) New goals javadoc-no-fork and test-javadoc-no-fork which will not invoke generate-*-sources

["Mirko Friedenhagen (JIRA)" <ji...@codehaus.org>]

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

Mirko Friedenhagen reassigned MJAVADOC-369:
-------------------------------------------

    Assignee: Mirko Friedenhagen

> New goals javadoc-no-fork and test-javadoc-no-fork which will not invoke generate-*-sources
> -------------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-369
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-369
>             Project: Maven Javadoc Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.9
>            Reporter: Mirko Friedenhagen
>            Assignee: Mirko Friedenhagen
>         Attachments: mjavadoc-369.patch
>
>
> * We have a lot of projects in our CI system (Jenkins) where we run {{mvn clean deploy site-deploy}}.
> * Because of this, the phase {{generate-sources}} resp. {{generate-test-sources}} does not need to rerun. It might even give a different result from the previous run during the default lifecycle.
> * Attached is a patch (including a IT) which will introduce two new goals, {{javadoc-no-fork}} and {{test-javadoc-no-fork}}, which will just skip the fork during site-run.
> In our case, e.g. {{enforcer:enforce}}, {{jacoco:prepare-agent}} and a homegrown configuration plugin are executed over and over again, which:
> * leads to confusion when application developers look on the console and 
> * slows down the builds.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)