maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal
Date Thu, 01 Mar 2018 20:18:05 GMT

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

ASF GitHub Bot commented on MJAVADOC-444:
-----------------------------------------

busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and aggregate-test-no-fork
for non-forking versions of aggregate goals.
URL: https://github.com/apache/maven-javadoc-plugin/pull/2
 
 
   
   Follows the same pattern as JavadocNoForkReport with the aggregate goals.
   
   Tested out locally by installing a SNAPSHOT version and then moving my project over to
it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add an 'aggregated-no-fork' goal
> --------------------------------
>
>                 Key: MJAVADOC-444
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-444
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.10.3
>            Reporter: Karl Heinz Marbaise
>            Priority: Critical
>
> Currently you can call maven-javadoc-plugin via {{mvn clean package javadoc:aggregate}}
which results in deleting all previously created artifacts in {{target}} folder. So it would
be helpful having a separate goal without forking the life cycle.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message