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 (nike.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: Subject: [STOPPED] [VOTE] Release Apache Maven Archetype 2.3
Date: Sat, 07 Mar 2015 16:32:32 +0100
Message-ID: <9264072.9sFZtG8X8h@herve-desktop>
User-Agent: KMail/4.13.3 (Linux/3.13.0-46-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <54FB0D08.3030305@gmx.de>
References: 
 <CALhtWkeGMDLdaHZi0+2eHuZZBcmvCM_0Lu6iLhg1TS1Cd_3KFg@mail.gmail.com>
 <1544017.gfW0Tx880t@herve-desktop> <54FB0D08.3030305@gmx.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

it's good to undesrtand the details: yes, install vs verify...

Notice that it's a good thing (TM) to check releases during vote with v=
erify=20
instead of install, so the local repository doesn't get polluted by loc=
al=20
build of a release that will later have an official build on central

should we change Jankins configuration with verify instead of install?

Regards,

Herv=E9

Le samedi 7 mars 2015 15:36:56 Karl Heinz Marbaise a =E9crit :
> Hi Herv=E9,
>=20
> what made me mad was that our buildservers haven't alarmed us on such=

> problem...
>=20
> After diving a little bit into it i have found out the real differenc=
e
> between my usage on our build servers / in the bug description and my=
 usage:
>=20
> The build servers use: mvn -Prun-its clean install
> I have used:           mvn -Prun-its clean verify (i use it allways)
>=20
> If i use mvn -Prun-its clean verify the maven-invoker-plugin (version=

> 1.7) doesn't install all artifacts in the local integration test
> repository despite the fact of using the `install` goal, which seems =
the
> real problem. version 1.9 looks ok.
>=20
> If you use mvn -Prun-its clean install it will be installed during th=
e
> module build in the users local repository...and will be accessible
> during the integration tests.
>=20
> This is the reason why it has not been itched us yet...
>=20
>=20
> Kind regards
> Karl Heinz Marbaise
>=20
> On 3/7/15 3:12 PM, Herv=E9 BOUTEMY wrote:
> > ok, thank you for the precision: in this case, this is really a
> > showstopper
> >=20
> > the bug is more strange: it affects distribution but not git checko=
ut :/
> >=20
> > hopefully, newer m-invoker-p version seems ok with distribution
> >=20
> > let's try...
> >=20
> > Regards,
> >=20
> > Herv=E9
> >=20
> > Le samedi 7 mars 2015 13:53:09 Karl Heinz Marbaise a =E9crit :
> >> Hi Herv=E9 ,
> >>=20
> >> On 3/7/15 12:16 PM, Herv=E9 BOUTEMY wrote:
> >>> like Benson, I wanted to understand why we didn't find the issue =
before
> >>> the
> >>> release (I built the git HEAD without any issue)
> >>=20
> >> I have added the appropriate log files for Maven 3.0.5, 3.1.1, 3.2=
.5
> >> where i have always the same issue with Maven Invoker 1.7....just =
for
> >> the record and for the history...
> >>=20
> >> If the bug had only itched Maven 2.2.1 i would have ignored but it=

> >> itched all Maven versions...
> >>=20
> >>> looking at the build logs, it seems that it's only an issue when =
built
> >>> with
> >>> Maven 2.2.1 (which I didn't test), and the bug seems more in m-in=
voker-p
> >>> than in archetype
> >>=20
> >> Of course i wrote so....but unfortunately not only Maven 2.2.1 all=
 other
> >> maven versions as well...
> >>=20
> >>> then, personally, I wouldn't have cancelled the vote...
> >>>=20
> >>> that's really a good thing (TM) that we stop Maven 2.2.1 support =
for
> >>> plugins! at least, this cancelled release clearly shows one thing=
 we
> >>> gain
> >>> from it.
> >>>=20
> >>> Regards,
> >>>=20
> >>> Herv=E9
> >>>=20
> >>> Le vendredi 6 mars 2015 18:19:08 Karl Heinz Marbaise a =E9crit :
> >>>> Hi Benson,
> >>>>=20
> >>>> I have attached the appropriate log files to the JIRA ticket...
> >>>>=20
> >>>> Kind regards
> >>>> Karl Heinz Marbaise
> >>>>=20
> >>>> On 3/6/15 3:22 PM, Benson Margulies wrote:
> >>>>> I'll respin, but I wonder why it failed to bite me.
> >>>>>=20
> >>>>> On Fri, Mar 6, 2015 at 2:59 AM, Karl Heinz Marbaise
> >>>>> <khmarbaise@gmx.de>
> >>>=20
> >>> wrote:
> >>>>>> Hi Benson,
> >>>>>>=20
> >>>>>> first the link to the release is unfortunately wrong...the cor=
rect
> >>>>>> link
> >>>>>> is:
> >>>>>>=20
> >>>>>> https://repository.apache.org/content/repositories/maven-1146/=
org/apa
> >>>>>> ch
> >>>>>> e/
> >>>>>> maven/archetype/maven-archetype/2.3/maven-archetype-2.3-source=
-releas
> >>>>>> e.
> >>>>>> zi
> >>>>>> p
> >>>>>>=20
> >>>>>> Checked SHA1 Ok...
> >>>>>>=20
> >>>>>> Next step checking with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.5 via m=
vn
> >>>>>> -Prun-its
> >>>>>> clean verify
> >>>>>>=20
> >>>>>> i have found that two integration tests are failing for all Ma=
ven
> >>>>>> versions:
> >>>>>>=20
> >>>>>> [ERROR] The following builds failed:
> >>>>>> [ERROR] *  build-archetype/pom.xml
> >>>>>> [ERROR] *  property-setting-cli/pom.xml
> >>>>>>=20
> >>>>>> After looking a little bit into it...i found out that if i cha=
nge the
> >>>>>> maven-invoker-plugin version in maven-archetype-plugin from 1.=
7 to
> >>>>>> 1.9
> >>>>>> it
> >>>>>> works without any issue. I have created an issue for that
> >>>>>> http://jira.codehaus.org/browse/ARCHETYPE-477 and fixed it in =
git
> >>>>>>=20
> >>>>>> Unfortunately that this issue is for all
> >>>>>> Maven versions i have to give: -1
> >>>>>>=20
> >>>>>> Cause this would result in a release package which can't be bu=
ilt
> >>>>>> without
> >>>>>> changing it....
> >>>>>>=20
> >>>>>> Kind regards
> >>>>>> Karl Heinz Marbaise
> >>>>>>=20
> >>>>>> On 3/6/15 1:21 AM, Benson Margulies wrote:
> >>>>>>> Hi,
> >>>>>>>=20
> >>>>>>> This is a vote to release Archetype 2.3, intended as the last=

> >>>>>>> version
> >>>>>>> of Archetype built to support Maven 2.2.x.
> >>>>>>>=20
> >>>>>>> We solved some issues:
> >>>>>>>=20
> >>>>>>> Release Notes - Maven Archetype - Version 2.3
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>> ** Bug
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-345] - archetype:create-from-project do =
not
> >>>>>>>         process
> >>>>>>>=20
> >>>>>>> <jarModule> and <ejbModule> sections into EAR's pom.xml
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-397] - Required property default value i=
s not
> >>>>>>>=20
> >>>>>>> displayed correctly if a Velocity expression
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-413] - on linux adding <parent> element =
to
> >>>>>>>         generate
> >>>>>>>=20
> >>>>>>> pom.xml changes line endings to /r/n
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-429] - JIRA report in site only shows fi=
xes up
> >>>>>>>         to
> >>>>>>>=20
> >>>>>>> v2.1 of plugin
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-435] - Bad link to old docs in usage pag=
e
> >>>>>>>=20
> >>>>>>> ** Improvement
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-182] - Adding 'role-hint' for the defaul=
t
> >>>>>>>=20
> >>>>>>> Selector/Configurer/Queryer implementations
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-401] - use repo.maven.apache.org CNAME t=
o
> >>>>>>>         provide
> >>>>>>>=20
> >>>>>>> more stability
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-418] - use plugin annotations
> >>>>>>>         * [ARCHETYPE-428] - Improve Generate project in batch=
 mode
> >>>>>>>         doc
> >>>>>>>         page
> >>>>>>>         * [ARCHETYPE-465] - Upgrade to maven-parent version 2=
6
> >>>>>>>         * [ARCHETYPE-466] - Upgrade maven-invoker 2.0.11 to 2=
.1.1
> >>>>>>>         * [ARCHETYPE-467] - Removed unused maven-war-plugin
> >>>>>>>         dependency.
> >>>>>>>         * [ARCHETYPE-468] - Upgrade maven-plugin-testing-harn=
ess to
> >>>>>>>         1.3
> >>>>>>>=20
> >>>>>>> ** Task
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-431] - Only include Apache Maven archety=
pes in
> >>>>>>>=20
> >>>>>>> internal archetype catalog
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-432] - Update distributionManagement in =
POM
> >>>>>>>         * [ARCHETYPE-471] - Make a final Maven 2.2.1 release
> >>>>>>>=20
> >>>>>>> ** Wish
> >>>>>>>=20
> >>>>>>>         * [ARCHETYPE-464] - Upgrade Plugin Required Maven Ver=
sion to
> >>>>>>>         2.2.1
> >>>>>>>=20
> >>>>>>> There are still a couple of issues left in JIRA:
> >>>>>>>=20
> >>>>>>> http://jira.codehaus.org/browse/ARCHETYPE-460?jql=3Dproject%2=
0%3D%20AR
> >>>>>>> CH
> >>>>>>> ET
> >>>>>>> YPE%20AND%20resolution%20%3D%20Unresolved%20AND%20status%20%3=
D%20Ope
> >>>>>>> n%
> >>>>>>> 20
> >>>>>>> ORDER%20BY%20priority%20DESC%2C%20key%20DESC
> >>>>>>>=20
> >>>>>>> Staging repo:
> >>>>>>>=20
> >>>>>>> https://repository.apache.org/content/repositories/maven-1146=
/conten
> >>>>>>> t/
> >>>>>>> or
> >>>>>>> g/apache/maven/archetype/maven-archetype/2.3/maven-archetype-=
2.3-sou
> >>>>>>> rc
> >>>>>>> e-
> >>>>>>> release.zip>>
> >>>>>>=20
> >>>>>> https://repository.apache.org/content/repositories/maven-1146/=
org/apa
> >>>>>> ch
> >>>>>> e/
> >>>>>> maven/archetype/maven-archetype/2.3/maven-archetype-2.3-source=
-releas
> >>>>>> e.
> >>>>>> zi
> >>>>>> p>>
> >>>>>>=20
> >>>>>>> https://repository.apache.org/content/repositories/maven-1146=
/conten
> >>>>>>> t/
> >>>>>>> or
> >>>>>>> g/apache/maven/archetype/maven-archetype/2.3/maven-archetype-=
2.3-sou
> >>>>>>> rc
> >>>>>>> e-
> >>>>>>> release.zip
> >>>>>>>=20
> >>>>>>> Source release checksum(s):
> >>>>>>> [NAME-OF]-source-release.zip sha1:
> >>>>>>> 842a4a5a9aa478883e6bef0c195bf0f943b440a5
> >>>>>>>=20
> >>>>>>> Staging site:
> >>>>>>> http://maven.apache.org/archetype-archives/archetype-LATEST
> >>>>>>>=20
> >>>>>>> Guide to testing staged releases:
> >>>>>>> http://maven.apache.org/guides/development/guide-testing-rele=
ases.ht
> >>>>>>> ml
> >>>>>>>=20
> >>>>>>> Vote open for 72 hours.
> >>>>>>>=20
> >>>>>>> [ ] +1
> >>>>>>> [ ] +0
> >>>>>>> [ ] -1
> >>>>=20
> >>>> ----------------------------------------------------------------=
-----
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>=20
> >>> -----------------------------------------------------------------=
----
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
>=20
> ---------------------------------------------------------------------=

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


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