+1 Best, Christian
Sent from a mobile device Am 17.05.2012 15:50 schrieb "Claus Ibsen" <claus.ib...@gmail.com>: > On Thu, May 17, 2012 at 3:39 PM, Daniel Kulp <dk...@apache.org> 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? > > > > +1 > > I dont think having the manual build during normal brings much value > to the table. > So I think it should be fine to disable it, and have it build during > the release process etc. > > > > -- > > Daniel Kulp > > dk...@apache.org - http://dankulp.com/blog > > Talend Community Coder - http://coders.talend.com > > > > > > -- > Claus Ibsen > ----------------- > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ >
