Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com
 designates 209.85.214.182 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: We will not be able to update our websites...
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: 
 <CAPoyBqR+2PTQUzkq2G2GM8tseLyYNDjd_=XaGKyrj9Rr8d8sEA@mail.gmail.com>
Date: Tue, 18 Dec 2012 12:43:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A08154D1-56DB-40A7-9F59-E19663E5F63A@dslextreme.com>
References: 
 <CAE9L6G28XspybPGWDrEvQp5Aszum5fu4xKpPw36zXz_Ui0Ffuw@mail.gmail.com>
 <CAE9L6G2eeYa0v-86gL-XAxVpWhFJo-SJHrZeAtqveRTDE=kDAQ@mail.gmail.com>
 <20121214214054.GF20488@dusk.harfang.homelinux.org>
 <CAE9L6G0DxhweWVaDkkRUdJ_mNAp+oAtC9k_9xT+J4MFXKtUT3w@mail.gmail.com>
 <20121214220725.GH20488@dusk.harfang.homelinux.org>
 <CAE9L6G3ZvgC4kH9Nd-nmqKxyC4dNg9mH7ZNWMnb5tvn_Vdma2w@mail.gmail.com>
 <CAPoyBqSWnRbdbmF9-rG_iGDcEh9iomV+-_kNG=imx1D+3nSzqA@mail.gmail.com>
 <CAE9L6G1ZjMwG09C8MLwAFMhNQ_bHgPRukbN7qroxxg+ZuTjVqA@mail.gmail.com>
 <CAPoyBqTGn3d-NgqMOh6e4XwkTaoRLpF288tMF5prU6K0sSAtJQ@mail.gmail.com>
 <CAPoyBqTV9dxKwb24Muzfnwvh+HL6GwuA5RfrBDzUGPp62Q1SHg@mail.gmail.com>
 <27696813-A824-48B0-B8D2-A4890E492574@dslextreme.com>
 <1DA172AB-7EBA-4D82-8267-AD9CB4B0530E@dslextreme.com>
 <CAPoyBqQp1cEF0feOF2ns9fzogXNr0vuxjMzMhf=Qz-FU48Q2qQ@mail.gmail.com>
 <CAPoyBqRwGdKk=OZtXPbo7mV5JsuaMiuNo9YZva_tg0k5x6RO=w@mail.gmail.com>
 <CAPoyBqR_Q93ikaCmKcs4XKNSqw_gfQvBxTwj6NNLChCPieBi5Q@mail.gmail.com>
 <CAPoyBqQNR8P+b
 3xNM-kLvFoq9WAV9-y8dzUXY3wrMLP87zcNqQ@mail.gmail.com>
 <2CED3B63-FFFB-4E31-B0F7-A0CE6965CC15@dslextreme.com>
 <CAPoyBqQeT1Jx3QgJkqLpM9Zj2zu4Ge-Xs4PXYUer4AbBfLv8sQ@mail.gmail.com>
 <88030D83-4CEF-40F6-BA85-1E83664C57B7@dslextreme.com>
 <CAPoyBqR+2PTQUzkq2G2GM8tseLyYNDjd_=XaGKyrj9Rr8d8sEA@mail.gmail.com>
To: "Commons Developers List" <dev@commons.apache.org>


On Dec 18, 2012, at 12:18 PM, Olivier Lamy wrote:

> 2012/12/18 Ralph Goers <ralph.goers@dslextreme.com>:
>>=20
>> On Dec 18, 2012, at 9:10 AM, Olivier Lamy wrote:
>>=20
>>> 2012/12/18 Ralph Goers <ralph.goers@dslextreme.com>:
>>>> I still don't understand why you are committing the subprojects to =
svn.  That is not required.  Just use stage-deploy to deploy to a local =
directory on your computer, then copy that under where you have the =
production web site checked out and check it in.  See =
http://wiki.apache.org/logging/ManagingTheWebSite
>>>>=20
>>> As I can see in section "Managing Sub-project Sites" this doc says
>>> "Make sure all that is added to svn and commit it."
>>> So subsites must be checked in (here I configure this to be done tru =
a
>>> maven plugin and not manually)
>>> Infra will be able to use as production web site:
>>> http://svn.apache.org/repos/asf/commons/cms-site/trunk/ (or
>>> =
https://svn.apache.org/repos/infra/websites/production/commons/content/
>>> but this one still doesn't exist, I will ping infra on the jira =
entry
>>> for their preference).
>>=20
>> Step 6 is referring to checking it in directly to =
https://svn.apache.org/repos/infra/websites/production/logging/content/ =
in the subdirectory that is listed in extpaths.txt, not some other =
subversion location.  If you look under log4j, for example, you will see =
a directory for each release and a directory that is a symlink to the =
current release (for Log4j 2 the 2.x directory links to log4j-2.0-beta3.
>>=20
>>>=20
>>> So if you want sub-project sites available AFAIK this (check in all
>>> content) must be done (or I misunderstand something: -)).
>>>=20
>>> Makes sense ?
>>=20
>> Not really.
> So maybe I misunderstood what you want to do.
>=20
> What I understood:
> 1) main site is build from
> http://svn.apache.org/repos/asf/commons/proper/commons-site/trunk/
> (and marked as cms content so possible to modify files via the cms ui)
> technically a buildbot job run the maven build and commit the
> generated site to
> http://svn.apache.org/repos/asf/commons/cms-site/trunk/ (this svn path
> will serve as infra for web site content staging then live) (note I
> did the change for infra requirement on sources structure)
> 2) due to #1 sub project content (take lang) must be committed to
> http://svn.apache.org/repos/asf/commons/cms-site/trunk/lang

This step is not necessary.  sub-project content can be committed =
directly to =
https://svn.apache.org/repos/infra/websites/production/commons/content/lan=
g/lang-n.n or =
https://svn.apache.org/repos/infra/websites/production/commons/content/pro=
per/lang/lang-n.n depending on what is in extpaths.txt

> 3) as lang is not generated by cms it must be added to extpaths file.

This is true, unless it resides under a directory that was declared in =
extpaths.txt, (for example, "proper" as in the second url above.

> 4) committing sub project content will be done using the maven
> scm-publish plugin (that's what I started to do)

I don't do this.  I do mvn site:stage-deploy =
-DstaginngSiteURL=3Dfile:///Users/rgoers/log4j  for my Log4j 2 web site. =
I zip it and publish it at p.a.o/~rgoers/log4j2 for review during a =
release and then I do a "cp -r ~/log4j/*" to where I want it to go under =
where I have the production web site checked out on my machine. After it =
is copied I remove the link from the old release and create a link to =
the new release and then do an svn commit.

>=20
> Regarding your point on versionned  subsites, I don't such structure
> here (no commons.a.o/lang-2.x)

Correct. We are doing this in logging because it makes it easy to deploy =
a new release of the web site.

>=20
> So let me know what is your plan ?
> I proposed to help but it looks I don't know exactly what is the plan
> so that will be a bit complicated for me.

The plan would be to follow what is published in the logging wiki link.  =
I'm not sure why you think it is complicated. It should be simpler than =
what you are doing.

Ralph=

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