Hello,
Yes, it's expected behaviour: forking happens when preparing the plugin,
before running report generation. Skip happens at the beginning of report
generation, just to not do it.
Notice the situation will get better with m-site-p 3.4, with
http://jira.codehaus.org/browse/MSITE-454 fixed
Thanks a lot!
Maybe you know what time 3.4 will be released?
OFF maybe you know is there any way to get JIRA account to Vote/Watch
issues?
On 16 June 2014 13:09, Hervé BOUTEMY herve.bout...@free.fr wrote:
Hello,
Yes, it's expected behaviour: forking happens when preparing the plugin,
Le lundi 16 juin 2014 13:19:59 Maxim Solodovnik a écrit :
Thanks a lot!
Maybe you know what time 3.4 will be released?
I should be doing it if a few weeks: I have still a few improvements I want to
do before releasing
OFF maybe you know is there any way to get JIRA account to Vote/Watch
Thanks a lot!
On 16 June 2014 23:53, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le lundi 16 juin 2014 13:19:59 Maxim Solodovnik a écrit :
Thanks a lot!
Maybe you know what time 3.4 will be released?
I should be doing it if a few weeks: I have still a few improvements I
want to
do
Hello All,
I'm currently observing weird behavior
I'm executing javadoc plugin (goals: javadoc, aggregate) during my build
which provokes forking.
That is expected
Now I'm skipping execution of javadoc (using skiptrue/skip but,
surprisingly, Forking still happens :(
Maybe anyone knows if it is
