It sounds good.
When we get it done, we need to update the release manager page for adding the profile when doing the release.


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?



--
Willem
----------------------------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
         http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang

Reply via email to