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, 22 Mar 2018 18:31:00 GMT

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

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

abudaev commented on issue #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#issuecomment-375409708
 
 
   @busbey maybe you know how to fix this trouble without your PR ->
   
   [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single
(create distr) on project aggragator-module: Failed to create assembly: Error adding file
'javadoc-aggragate:module1:jar:1.0-SNAPSHOT' to archive: \trouble\module1\target\classes isn't
a file. -> [Help 1]
   
   example project structure 
   https://github.com/abudaev/trouble
   mvn verify -P parrent-module
   
   I think that it happened on maven live cycle miracles: fork, phases and etc. I'am trying
many methods: different phases on assembly and javadoc plugins, set properties on aggregator
project like this <maven.javadoc.skip>true<maven.javadoc.skip>. No works. I'm
ready to cry

----------------------------------------------------------------
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