Hi Dan I know I'm pulling up a old thread here, sorry for that, but (as you may already know) the provided fix caused problems which is currently commented out since ages:
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-10-0-tp5714768p5715311.html Would you have time to look into this? In worst case we should better revert this in case we can't fix it properly IMHO. Babak dk...@apache.org wrote > On Friday, May 18, 2012 09:18:26 AM Willem Jiang wrote: >> It sounds good. >> When we get it done, we need to update the release manager page for >> adding the profile when doing the release. > > Shouldn't need to. I updated the tooling pom.xml to build the manual for > most of the profiles where it would be needed. The release, deploy, and > apache-release profiles being among them. Thus, nothing really to update > docs wise. :-) > > In anycase, "mvn -T 8 -Pfastinstall" now completes more often than not. > :-) > > > Dan > > >> >> On 5/17/12 9:39 PM, Daniel Kulp wrote: >> > I've discovered that the manual building is what is causing the Camel >> > parallel builds to completely fail. If I do: >> > >> > $ mvn -Pfastinstall -P '!build.manual' -T 8 >> > >> > to turn that off, then the parallel build actually works. (when the >> > repository update stuff in the install plugin doesn't barf, separate >> > issue) That kind of brings up the question: should we build the manual >> > by default? Since it requires things like prince to be installed, it's >> > really not that useful "out of the box". I'm kind of wondering if it >> > make sense to NOT have it build by default, but have it built during >> > certain profiles (release, deploy, etc...). >> > >> > Thoughts? > -- > Daniel Kulp > dkulp@ > - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com -- View this message in context: http://camel.465427.n5.nabble.com/Building-the-manual-tp5711396p5726497.html Sent from the Camel Development mailing list archive at Nabble.com.
