[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-07-11 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on MJAVADOC-444:
-

DiJu519 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-404299254
 
 
   @khmarbaise @busbey 
   
   I just rebased this change locally to master it and it built successfully. 
   
   mvn clean verify failed the first time, similar to the error you posted 
@khmarbaise , but a second rebuild went through fine. 
   
   I think there's something behind the scenes with artifact resolution issues 
going on. I've seen this non-deterministic behavior lately while using mvn.


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

khmarbaise 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-375459148
 
 
   So unfortunately the CI build has failed please take a detail look here: 
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-444/1/console
   


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

khmarbaise 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-375458144
 
 
   So now I try to see what our CI says...


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

khmarbaise 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-375454271
 
 
   @busbey Hi, can you please remove the `@version $Id$` entries from your 
changes...


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

khmarbaise 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-375454271
 
 
   @busbey Hi, can you please remove the `@version $Id$` entries from your 
file...


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

busbey 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-375428544
 
 
   Hi @abudaev!
   
   Your best bet is to bring the issue up on the [users@maven mailing 
list](https://lists.apache.org/list.html?us...@maven.apache.org) or open a new 
issue with the details.


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

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 life 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 
true. 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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MJAVADOC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
true. 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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

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


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

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 how to fix this trouble ->
   
   [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
   


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on MJAVADOC-444:
-

busbey 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-375367133
 
 
   @abudaev this change hasn't been merged into the project source yet, so it's 
unlikely to be in a release in the short term.
   
   For more info, esp to watch for updates, I'd recommend subscribing to 
[MJAVADOC-444](https://issues.apache.org/jira/browse/MJAVADOC-444) on the 
project JIRA.


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-22 Thread ASF GitHub Bot (JIRA)

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

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-375363117
 
 
   Can you release with goal ASAP?)


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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-05 Thread Sean Busbey (JIRA)

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

Sean Busbey commented on MJAVADOC-444:
--

PR has now been updated with docs and an it, modeled after the work for 
MJAVADOC-369 which added the no-fork versions of the javadoc and javadoc-test 
goals.

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


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-01 Thread Sean Busbey (JIRA)

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

Sean Busbey commented on MJAVADOC-444:
--

linking a PR I put together that implements this.

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


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-01 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/MJAVADOC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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:
us...@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)


[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

2018-03-01 Thread Sean Busbey (JIRA)

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

Sean Busbey commented on MJAVADOC-444:
--

this would help immensely for our builds over in Apache HBase. we build 4 
aggregate docs (user and internal facing for main and test) and right now that 
means 4 additional times forking a build that we don't need.

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