struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <grobme...@gmail.com>
Subject Re: Apache CMS / svnpubsub
Date Sat, 15 Dec 2012 08:12:55 GMT
Hi all,

I just created the Infra issue:
https://issues.apache.org/jira/browse/INFRA-5659

Before I have asked on the infra list if the plan using "mvn site" for
the main site and committing the subsites manually would work. It
seems it does, so I pushed it now.

Cheers
Christian


On Wed, Dec 12, 2012 at 8:39 AM, Lukasz Lenart <lukaszlenart@apache.org> wrote:
> 2012/12/10 Christian Grobmeier <grobmeier@gmail.com>:
>> Looking at our main site, I would say there is an option to use the
>> CMS for it. With your (Lukasz) CMS snippet it should be easy to update
>> it. But at the moment we were working on fluido and the use of maven.
>> I didn't consider the svnpubsub.
>>
>> Here is the current main site:
>> http://svn.apache.org/repos/asf/struts/site/
>>
>> I have heard that the ASF CMS can perform a maven build. That way we
>> would just check our sources into the svn folder above and CMS would
>> build it for us.
>>
>> Decision 1: Use ASF CMS with nice markdown editing features or try to
>> continue with the maven build for the MAIN website? I am not sure if
>> the latter option will work - need infra for that
>
> We should follow the least intrusive path - use Maven if we can, using
> MD is painful as we must migrate the whole content
>
>> I think the thin with the different version docs of the Struts1/2
>> website can be solved with extpath. We have similar in logging. It
>> looks like that:
>> http://svn.apache.org/repos/asf/logging/site/cms/trunk/content/extpaths.txt
>>
>> Here is where we checkin our subsites (generated locally by mvn):
>> https://svn.apache.org/repos/infra/websites/production/logging/content/
>>
>> The CMS cares on everything except what is in the extpath folders.
>> This is developers duty. In Struts land we would need to add an new
>> extpath to the CMS, create a name matching folder and commit manually
>> the release website to there.
>
> +1
>
>> Decision 2: Do we want to use the manual process or do we want to
>> migrate verything to the ASF CMS?
>>
>> In my opinion, I would try to let Maven build the main site and
>> manually care on the version-websites with extpath. It should be the
>> easiest way to use the new requirements with Struts.
>
> +1
>
> I would rather wait for -1, if absent, go ahead :-)
>
>
> Regards
> --
> Ɓukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>



-- 
http://www.grobmeier.de
https://www.timeandbill.de

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message