xec module to maven shared
>>> * move/merge this branch to site-3.x branch
>>>
>>> So WDYT ?
>>
>> +1 to both proposals.
>>
>> I'll leave the decision about when to move code to a shared module and
>> when do the merge the MSITE-560 branch
1] and [2]. But looks to be
> > only missing merge
> >
> > Do we move forward and :
> > * move the report-exec module to maven shared
> > * move/merge this branch to site-3.x branch
> >
> > So WDYT ?
>
> +1 to both proposals.
>
> I'll leave
e code to a shared module and
when do the merge the MSITE-560 branch into the 3.x branch up to you guys.
>
> Thanks,
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1 to create a report-exec module in shared
but only *after* 3.0-beta-4 release, since the actual test in MSITE-560 branch
doesn't have any UT or IT, and using it in maven-pdf-plugin before releasing a
1.0 version would help being sure of the 1.0 version
For the moment, having the code i
erged to MSITE-560 branch )
Thanks to the French mafia! :)
-Lukas
So WDYT ?
Thanks,
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1 as long as the tests pass ;)
Merci !
Kristian
Den 24.03.2011 10:07, skrev Olivier Lamy:
Hello,
I think we are in a good way with having only one branch/trunk for the
maven-site plugin for maven2 and 3 (thanks and kudo herve for
obstinacy ! as usual French OpenSource mafia rocks :-) ).
It
Hello,
I think we are in a good way with having only one branch/trunk for the
maven-site plugin for maven2 and 3 (thanks and kudo herve for
obstinacy ! as usual French OpenSource mafia rocks :-) ).
It looks there are still one it failure [1] and [2]. But looks to be
only missing merge
Do we move
