Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <AANLkTi=qWEpytdber155AQpQkUobbaTEK2boQNrwWYZy@mail.gmail.com>
References: <AANLkTimv1Atg+GxEBXA8B9TzfXq47Uxy4H=Q=ebNyF8J@mail.gmail.com>
	<E0D1910851D44FE0BC714746A2DB848B@phoenix>
	<AANLkTikKS+mm_yr_c=gLL3B-AAXv4KpVhqgCgXH9SBe1@mail.gmail.com>
	<AANLkTinupFeRmQ0YEHJNorr9bgEh618bQa=L_fosA-42@mail.gmail.com>
	<AANLkTikM7Dz8YZus_SWvA0t5SkqCoBcB9qb7iynoYCUy@mail.gmail.com>
	<AANLkTi=qWEpytdber155AQpQkUobbaTEK2boQNrwWYZy@mail.gmail.com>
Date: Thu, 13 Jan 2011 09:56:47 -0500
Message-ID: <AANLkTikcrkN7oLpV+1eY1Ofs1dM1ss5oZm7k1LBamyAc@mail.gmail.com>
Subject: Re: 2x docs
From: Wes Wannemacher <wesw@wantii.com>
To: Struts Developers List <dev@struts.apache.org>, lukasz.lenart@gmail.com
Content-Type: multipart/alternative; boundary=0015175cd590e22fa40499bb8644

--0015175cd590e22fa40499bb8644
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I just logged in and checked, I don't have any cron jobs configured.

My original gripe, which might be what you're trying to get to Lukasz, is
that 2.x is a symlink that points to the latest release... However, when th=
e
"export magic" happens, the docs get overwritten with whatever is currently
in Confluence. So, here is a scenario. Lukasz ran the release for 2.2.1,
everything is good. We're now at 2.2.2-SNAPSHOT from a source perspective.
Now, Lukasz adds a new feature/configuration param/etc. and updates
confluence. At some point, confluence auto-exports, and there is some other
job that transfers that export over to people.a.o. Remember, 2.x is a
symlink to 2.2.1, so by the time the next release rolls around, the docs fo=
r
2.2.1 are going to include all of the updates between the release of 2.2.1
and 2.2.2. Then, things roll forward, leaving the same problem with
subsequent releases.

I believe my original suggestion was to make 2.x a legitimate directory and
that part of the release process involved a manual step of renaming 2.x to
the current release, i.e. -

`mv 2.x 2.2.2`

And then making a new 2.x folder and granting appropriate permissions, i.e.
-

`mkdir 2.x ; chmod 775 2.x`

I can't remember the original discussion, but it appears that we left it
as-is.

On Thu, Jan 13, 2011 at 6:53 AM, Lukasz Lenart <lukasz.lenart@googlemail.co=
m
> wrote:

> 2011/1/13 Maurizio Cucchiara <maurizio.cucchiara@gmail.com>:
> > Lukasz,
> > I don't know whether is a crontab output or what else, but as far as I
> > can understand it's only a symlink in site root of S2:
> >
> > [mcucchiara@minotaur:/www/struts.apache.org]$ ll 2.x
> > lrwxr-xr-x  1 rgielen  struts  - 5 Aug 16 10:13 2.x@ -> 2.2.1
>
> But the Docs are on cwiki.apache.org host, where can be exported to
> some folder, then some how we must grab them and put on
> people.apache.org
> The symlink is Rene's workaround ;-)
>
> Regards
> --
> =C5=81ukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Kapitu=C5=82a Javarsovia http://javarsovia.pl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


--=20
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

--0015175cd590e22fa40499bb8644--