Re: MSITE-560 branch

2011-03-25 Thread Kristian Rosenvold
Cool, way to go! Kristian Den 26. mars 2011 kl. 03:52 skrev "Hervé BOUTEMY" : > merge done, MSITE-560 closed: ITs stay unmodified and working > > I'll create report-exec module in Maven shared later, after maven-site-plugin > 3.0-beta-4 release > > Regards,

Re: MSITE-560 branch

2011-03-25 Thread Hervé BOUTEMY
merge done, MSITE-560 closed: ITs stay unmodified and working I'll create report-exec module in Maven shared later, after maven-site-plugin 3.0-beta-4 release Regards, Hervé Le vendredi 25 mars 2011, Dennis Lundberg a écrit : > On 2011-03-24 10:07, Olivier Lamy wrote: > > Hel

Re: MSITE-560 branch

2011-03-25 Thread Dennis Lundberg
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

Re: MSITE-560 branch

2011-03-24 Thread Hervé BOUTEMY
+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

Re: MSITE-560 branch

2011-03-24 Thread Lukas Theussl
missing merge Do we move forward and : * move the report-exec module to maven shared * move/merge this branch to site-3.x branch Both fine with me as long as * it's properly documented * the ITs are reviewed (eg some ITs are skipped on the MSITE-560-m2x build, and some ITs have not been m

Re: MSITE-560 branch

2011-03-24 Thread Kristian Rosenvold
+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

MSITE-560 branch

2011-03-24 Thread Olivier Lamy
move forward and : * move the report-exec module to maven shared * move/merge this branch to site-3.x branch So WDYT ? Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy [1] https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-site-plugin-3.x-MSITE-560/ [2

Re: MSITE-560

2011-03-15 Thread Hervé BOUTEMY
di 14 mars 2011, Hervé BOUTEMY a écrit : > it works!!! > > the bad news is that a new Maven 2.2.x release is necessary. > And I still have to tweak a little bit for deploy tasks: I didn't really > try for the moment. > > But the actual MSITE-560 branch works both with

Re: MSITE-560

2011-03-14 Thread Hervé BOUTEMY
it works!!! the bad news is that a new Maven 2.2.x release is necessary. And I still have to tweak a little bit for deploy tasks: I didn't really try for the moment. But the actual MSITE-560 branch works both with Maven 3 and latest 2.2.2-RC1- SNAPSHOT. Regards Hervé Le samedi 12 mars

Re: MSITE-560

2011-03-12 Thread Hervé BOUTEMY
his idea has been on my mind for a while as well. Thanks for putting > some code in there so that we can test and discuss! > > After fiddling with the MSITE-560 branch a bit I see two major concerns. > The changes I made on the branch was to change mavenVersion to 2.2.1 and > ad

Re: MSITE-560

2011-03-11 Thread Dennis Lundberg
ince Maven 3 specific libraries are picked. I tried to add these libraries > into a profile, without success. > > Can somebody have a look and help, please? This idea has been on my mind for a while as well. Thanks for putting some code in there so that we can test and discuss! After fiddli

MSITE-560

2011-03-01 Thread Hervé BOUTEMY
Hi, I tried to have a unique maven-site-plugin version compatible with both Maven 2 and 3. I think I updated the code to be compatible. But I have a problem: there are classloading issues when run with Maven 2, since Maven 3 specific libraries are picked. I tried to add these libraries into a p