Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of freeman.fang@gmail.com
 designates 209.85.210.45 as permitted sender)
Message-Id: <05CF5750-D6EE-4271-88A7-4061E8F52631@gmail.com>
From: Freeman Fang <freeman.fang@gmail.com>
To: dev@camel.apache.org
In-Reply-To: <20270088.m8JIX1mU5m@dilbert.dankulp.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-5-388631784
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Building the manual.....
Date: Fri, 18 May 2012 15:20:00 +0800
References: <20270088.m8JIX1mU5m@dilbert.dankulp.com>

--Apple-Mail-5-388631784
Content-Type: text/plain;
	charset=UTF-8;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

+1

Freeman
On 2012-5-17, at =E4=B8=8B=E5=8D=889:39, 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 =20=

> issue)
> That kind of brings up the question:  should we build the manual by =20=

> default?
> Since it requires things like prince to be installed, it's really =20
> not that
> useful "out of the box".   I'm kind of wondering if it make sense to =20=

> NOT
> have it build by default, but have it built during certain profiles
> (release, deploy, etc...).
>
> Thoughts?
>
> --=20
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042


--Apple-Mail-5-388631784--