Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: error (athena.apache.org: local policy)
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: [VOTE] Release Maven 3.1.1
Date: Thu, 19 Sep 2013 23:46:47 +0200
Message-ID: <1645485.CZ31zp0AO6@herve-desktop>
User-Agent: KMail/4.10.5 (Linux/3.8.0-30-generic; KDE/4.10.5; x86_64; ; )
In-Reply-To: <CF58C700-8D3E-4C21-8312-541EC2552537@tesla.io>
References: <9CF1ED7B-CEC0-49A0-A060-384F67715D71@tesla.io>
 <2865358.Hgo1csq7L1@herve-desktop>
 <CF58C700-8D3E-4C21-8312-541EC2552537@tesla.io>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

ah ok, staging to http://maven.staging.apache.org/

no, this url is for CMS staging only, which does not contain/support co=
mponent=20
included sites: see  http://maven.staging.apache.org/ref/ for example, =
which=20
does not exist. In fact, everything from extpaths.txt isn't published i=
n CMS=20
staging site (nor svn area)

CMS staging is only for Maven project main site, which is published by =
CMS.


Maven core staging site, like any other component staging area, is done=
 in CMS=20
production area protected by extpaths.txt, with a -LATEST convention:=20=

versionned release documentation is done with "svn cp"

This is the only way I found to integrate with CMS + svnpubsub solution=
 in as=20
much natural way as possible

Le jeudi 19 septembre 2013 14:35:16 Jason van Zyl a =E9crit :
> A button on the CMS page that says "Staging Site" and it produces a s=
tandard
> URL for a staging site that can be used for all core releases.
> On Sep 19, 2013, at 1:19 PM, Herv=E9 BOUTEMY <herve.boutemy@free.fr> =
wrote:
> > what do you call "a standard staging location"?
> > what more automation do you expect?
> >=20
> > Le jeudi 19 septembre 2013 11:02:46 Jason van Zyl a =E9crit :
> >> Do you think we can make a small addition to have it publish to a
> >> standard
> >> staging location? Is that hard to add to the tool? Would help us r=
each a
> >> state of more automation.
> >>=20
> >> I'll follow those steps for the time being.
> >>=20
> >> On Sep 19, 2013, at 10:19 AM, Herv=E9 BOUTEMY <herve.boutemy@free.=
fr>=20
wrote:
> >>> it does not use CMS
> >>> I split the instructions in 2 parts to make things as clear as po=
ssible:
> >>>=20
> >>> 1. mvn -Preporting site site:stage
> >>> =3D local HTML generation and staging of multiple modules into on=
e local
> >>> staging area
> >>>=20
> >>> 2. mvn scm-publish:publish-scm
> >>> publish local staging area to website svn area, which distributes=
 it to
> >>> live http server through svnpubsub
> >>>=20
> >>> Regards,
> >>>=20
> >>> Herv=E9
> >>>=20
> >>> Le jeudi 19 septembre 2013 07:00:13 Jason van Zyl a =E9crit :
> >>>> Are you just manually copying that or is there an option on the =
CMS to
> >>>> make
> >>>> the staging site?
> >>>>=20
> >>>> On Sep 18, 2013, at 10:18 PM, Herv=E9 BOUTEMY <herve.boutemy@fre=
e.fr>
> >=20
> > wrote:
> >>>>> I didn't have time to test this release for the moment
> >>>>>=20
> >>>>> but I updated a few days ago Maven core release instructions [1=
] to
> >>>>> stage
> >>>>> core reference documentation:
> >>>>> http://maven.apache.org/ref/3-LATEST/
> >>>>> Actual state is the staging from previous release vote: it shou=
ld be
> >>>>> updated from actual tag, but I don't have time for the moment
> >>>>>=20
> >>>>> Please take a few minutes to run the commands from your release=

> >>>>> directory.
> >>>>>=20
> >>>>> Regards,
> >>>>>=20
> >>>>> Herv=E9
> >>>>>=20
> >>>>> [1]
> >>>>> http://maven.apache.org/developers/release/maven-core-release.h=
tml#Sta
> >>>>> ge
> >>>>> _
> >>>>> the_Latest_Documentation>
> >>>>>=20
> >>>>> Le mardi 17 septembre 2013 11:39:17 Jason van Zyl a =E9crit :
> >>>>>> Hi,
> >>>>>>=20
> >>>>>> Maven Core ITs are good, and the license/notice issue has been=

> >>>>>> resolved
> >>>>>> so
> >>>>>> I'm rolling 3.1.1 again.
> >>>>>>=20
> >>>>>> Here is a link to Jira with 6 issues resolved:
> >>>>>> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=3D=
10500&ver
> >>>>>> si
> >>>>>> on
> >>>>>> =3D18 968
> >>>>>>=20
> >>>>>> Staging repo:
> >>>>>> https://repository.apache.org/content/repositories/maven-065/
> >>>>>>=20
> >>>>>> The distributable binaries and sources for testing can be foun=
d here:
> >>>>>> https://repository.apache.org/content/repositories/maven-065/o=
rg/apac
> >>>>>> he
> >>>>>> /m
> >>>>>> ave n/apache-maven/3.1.1/
> >>>>>>=20
> >>>>>> Specifically the zip, tarball, and source archives can be foun=
d here:
> >>>>>> https://repository.apache.org/content/repositories/maven-065/o=
rg/apac
> >>>>>> he
> >>>>>> /m
> >>>>>> ave n/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip
> >>>>>> https://repository.apache.org/content/repositories/maven-065/o=
rg/apac
> >>>>>> he
> >>>>>> /m
> >>>>>> av
> >>>>>> en/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz
> >>>>>> https://repository.apache.org/content/repositories/maven-065/o=
rg/apac
> >>>>>> he
> >>>>>> /m
> >>>>>> av
> >>>>>> en/apache-maven/3.1.1/apache-maven-3.1.1-src.zip
> >>>>>> https://repository.apache.org/content/repositories/maven-065/o=
rg/apac
> >>>>>> he
> >>>>>> /m
> >>>>>> av
> >>>>>> en/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz
> >>>>>>=20
> >>>>>> Source release checksum(s):
> >>>>>> apache-maven-3.1.1-src.zip sha1:
> >>>>>> 2251357aa47129674df578e787504b72cd57ed4d
> >>>>>>=20
> >>>>>> Staging site:
> >>>>>> http://people.apache.org/~jvanzyl/maven-3.1.1/
> >>>>>>=20
> >>>>>> Vote open for 72 hours.
> >>>>>>=20
> >>>>>> [ ] +1
> >>>>>> [ ] +0
> >>>>>> [ ] -1
> >>>>>>=20
> >>>>>> Thanks,
> >>>>>>=20
> >>>>>> The Maven Team
> >>>>>> Thanks,
> >>>>>=20
> >>>>> ---------------------------------------------------------------=
------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>=20
> >>>> Thanks,
> >>>>=20
> >>>> Jason
> >>>>=20
> >>>> ----------------------------------------------------------
> >>>> Jason van Zyl
> >>>> Founder,  Apache Maven
> >>>> http://twitter.com/jvanzyl
> >>>> ---------------------------------------------------------
> >>>=20
> >>> -----------------------------------------------------------------=
----
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>=20
> >> Thanks,
> >>=20
> >> Jason
> >>=20
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder,  Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >=20
> > -------------------------------------------------------------------=
--
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>=20
> Thanks,
>=20
> Jason
>=20
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------

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