batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: generating site is broken
Date Wed, 06 Jan 2016 14:54:58 GMT
Having those 2 trunks is simply a reflection of the reality - the site lifecycle and the project
lifecycle are simply different.

It is currently not clear to me how to maintain the batchee site because it seems to not work
like the other projects I’m involved in.

LieGrue,
strub



> Am 06.01.2016 um 15:38 schrieb Romain Manni-Bucau <rmannibucau@gmail.com>:
> 
> Far from a computer ATM but IIRC we use CMS - through the plugin
> https://github.com/apache/incubator-batchee/blob/master/siteDeploy.sh -and
> IMO it is important to deploy WITH the release which doesnt prevent to fic
> the site manually using svn - already done few times.
> 
> Side note: if we can avoid to split site and project in 2 trunks like
> sirona it is better and avoids to make it hard to deploy and easy to not
> update IMO
> Le 6 janv. 2016 15:20, "Mark Struberg" <struberg@yahoo.de> a écrit :
> 
>> Hi!
>> 
>> I tried to re-run the site generation but it blurped at me.
>> I understand that we might run the JavaDoc from maven, but why do we
>> publish the whole site with it? The site lifecycle is usually way different
>> than the project release cycles. And it’s just much easier to use Apache
>> CMS imo.
>> 
>> Any thoughts?
>> 
>> LieGrue,
>> strub
>> 
>> 
>> 


Mime
View raw message