You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ponymail.apache.org by hu...@apache.org on 2020/08/24 12:01:27 UTC
[incubator-ponymail-unit-tests] branch master updated: Add
"multi-import test" and corpus
This is an automated email from the ASF dual-hosted git repository.
humbedooh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-ponymail-unit-tests.git
The following commit(s) were added to refs/heads/master by this push:
new 9000487 Add "multi-import test" and corpus
9000487 is described below
commit 90004871405a69fb8e93d4ef210249154214f039
Author: Daniel Gruno <hu...@apache.org>
AuthorDate: Mon Aug 24 14:00:59 2020 +0200
Add "multi-import test" and corpus
---
corpus/maven_dev_2017_listsao.mbox | 184521 +++++++++++++++++++++++++++
corpus/maven_dev_2017_mailarchivesao.mbox | 179211 ++++++++++++++++++++++++++
tools/collate-mboxes.py | 34 +
yaml/generators-dkim-multimbox.yaml | 6380 +
4 files changed, 370146 insertions(+)
diff --git a/corpus/maven_dev_2017_listsao.mbox b/corpus/maven_dev_2017_listsao.mbox
new file mode 100644
index 0000000..6709ff0
--- /dev/null
+++ b/corpus/maven_dev_2017_listsao.mbox
@@ -0,0 +1,184521 @@
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id CE429200D4A
+ for <ar...@cust-asf2.ponee.io>; Tue, 28 Nov 2017 16:32:37 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id CCE42160C07; Tue, 28 Nov 2017 15:32:37 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 44DE1160C01
+ for <ar...@cust-asf.ponee.io>; Tue, 28 Nov 2017 16:32:37 +0100 (CET)
+Received: (qmail 39964 invoked by uid 500); 28 Nov 2017 15:32:36 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 39953 invoked by uid 99); 28 Nov 2017 15:32:36 -0000
+Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Nov 2017 15:32:36 +0000
+Received: from BALKIEL (unknown [141.115.66.19])
+ by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 44F081A008D
+ for <de...@maven.apache.org>; Tue, 28 Nov 2017 15:32:34 +0000 (UTC)
+From: "Eric Barboni" <sk...@apache.org>
+To: "'Maven Developers List'" <de...@maven.apache.org>
+References: <CA...@mail.gmail.com> <72...@st.informatik.tu-darmstadt.de>
+In-Reply-To: <72...@st.informatik.tu-darmstadt.de>
+Subject: RE: [VOTE] Release Maven Indexer 6.0.0
+Date: Tue, 28 Nov 2017 16:32:36 +0100
+Message-ID: <00...@apache.org>
+MIME-Version: 1.0
+Content-Type: text/plain;
+ charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
+X-Mailer: Microsoft Outlook 16.0
+Thread-Index: AQIeECWaWT2zmNiQ1SyoLdaRymvPXQFfq/1CoomdeZA=
+Content-Language: fr
+archived-at: Tue, 28 Nov 2017 15:32:38 -0000
+
++1 (non-binding)
+
+The blocked plugin work well with indexer 6.0.0
+
+Not sure it is important:
+The generated web site seems to follow the former versioning scheme..
+
+Best Regards
+Eric
+
+-----Message d'origine-----
+De : Andreas Sewe [mailto:sewe@st.informatik.tu-darmstadt.de]=20
+Envoy=C3=A9 : mardi 28 novembre 2017 16:25
+=C3=80 : dev@maven.apache.org
+Objet : Re: [VOTE] Release Maven Indexer 6.0.0
+
+Tam=C3=A1s Cserven=C3=A1k wrote:
+> [VOTE] Release Maven Indexer 6.0.0
+
+Tested this in two applications: a Maven plugin and a Spring =
+application. In both cases, I experienced no trouble.
+
+Thanks for doing the release, Tam=C3=A1s.
+
+Best wishes,
+
+Andreas
+
+
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 50310200D25
+ for <ar...@cust-asf2.ponee.io>; Sun, 22 Oct 2017 10:22:26 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 4E828160BD7; Sun, 22 Oct 2017 08:22:26 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 939AB1609C8
+ for <ar...@cust-asf.ponee.io>; Sun, 22 Oct 2017 10:22:25 +0200 (CEST)
+Received: (qmail 67794 invoked by uid 500); 22 Oct 2017 08:22:24 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 67782 invoked by uid 99); 22 Oct 2017 08:22:24 -0000
+Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Oct 2017 08:22:24 +0000
+Received: from [192.168.1.13] (p3E9D2FBA.dip0.t-ipconnect.de [62.157.47.186])
+ by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id CD8A31A042E;
+ Sun, 22 Oct 2017 08:22:21 +0000 (UTC)
+Subject: Re: Maven Docker Images
+To: Maven Developers List <de...@maven.apache.org>,
+ Manfred Moser <ma...@simpligility.com>
+References: <CA...@mail.gmail.com>
+ <17...@giga>
+ <CA...@mail.gmail.com>
+ <24...@giga>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <20...@dd17332.kasserver.com>
+From: Michael Osipov <mi...@apache.org>
+Message-ID: <01...@apache.org>
+Date: Sun, 22 Oct 2017 10:22:16 +0200
+User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
+ Thunderbird/52.4.0
+MIME-Version: 1.0
+In-Reply-To: <20...@dd17332.kasserver.com>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-US
+Content-Transfer-Encoding: 7bit
+archived-at: Sun, 22 Oct 2017 08:22:26 -0000
+
+Am 2017-10-22 um 04:24 schrieb Manfred Moser:
+> Following up on that remark and my earlier remark that we should NOT make this official .. here are my remarks:
+>
+> - so far the only binaries we assemble and call official are the tar.gz and zip archives (and even that is a gray line since official there are only sources from Apache)
+> - we do NOT support (by calling them official) any other binaries such as
+> - linux distro versions
+> - osx package versions (brews, ports)
+> - windows packages
+> - sdkman
+> - and many others
+> - the complexity of the docker images is greater than any of the above since it includes those factors..
+>
+> Here are a few issues why I would object to this being the official images
+>
+> - only openjdk and ibm java, no oracle java, no others such as Zulu or whatever
+> - limited os selection (only alpine and debian and windows from what I can tell), no centos, no ubuntu
+> - binaries are download from a mirror rather than the actual apache servers (alternatively maybe could use Central)
+>
+> These above factors imho show that there is a selection that has been made and I do not think we as the Apache Maven project should make this selection.
+>
+> As such I would suggest to keep it as is.
+>
+> An open source project from an individual that provides Maven binaries on Docker images. Just happens to be the case that the same person is also a Maven PMC (great btw!).
+>
+> If we make this part of the officially supplied binaries we could also think about
+>
+> - making binaries for various Linux distros in the first place (then we wouldnt even need docker images since it could be a one line to install an official Maven distro on them)
+> - supplying binaries to SDKMan, ports, brew, chocolatey and so on
+> - pull all mojohaus plugins into Apache (they are mostly the same committers..)
+> - pull other Maven projects in as desired
+>
+> You see where this leads... a LOT of work. In my opinion as the Apache Maven project we should focus on just that. Maven itself, our current plugins and related projects. We all know thats already more work than we can reasonably shoulder.. I see no reason to add more.
+>
+
+
+Perfect, you read my mind.
++2
+
+> Carlos Sanchez wrote on 2017-10-21 03:59:
+>
+>> BTW there are possibly more than one image build for each maven version.
+>> For a variety of reasons, like security issues in OS or to upgrade JDK or
+>> because docker rebuilds it, so it is not feasible to vote each of them.
+>
+>
+> ---------------------------------------------------------------------
+> 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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 69D94200D68
+ for <ar...@cust-asf2.ponee.io>; Thu, 28 Dec 2017 19:41:52 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 680E9160C1F; Thu, 28 Dec 2017 18:41:52 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id AE12D160C00
+ for <ar...@cust-asf.ponee.io>; Thu, 28 Dec 2017 19:41:51 +0100 (CET)
+Received: (qmail 12365 invoked by uid 500); 28 Dec 2017 18:41:50 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 12350 invoked by uid 99); 28 Dec 2017 18:41:50 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2017 18:41:50 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AFF4E18057F;
+ Thu, 28 Dec 2017 18:41:49 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.701
+X-Spam-Level:
+X-Spam-Status: No, score=-0.701 tagged_above=-999 required=6.31
+ tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id CxWJJtHy2p7J; Thu, 28 Dec 2017 18:41:48 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.18])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6F1685F39D;
+ Thu, 28 Dec 2017 18:41:47 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.local ([92.204.46.47]) by mail.gmx.com
+ (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id
+ 0Mey7N-1eJOpu1aaP-00OXHr; Thu, 28 Dec 2017 19:41:39 +0100
+Reply-To: info@soebes.de
+Subject: Re: second fix for MNG-6330 [regression] Parents relativePath not
+ verified anymore
+To: Robert Scholte <rf...@apache.org>,
+ Maven Developers List <de...@maven.apache.org>
+Cc: Stephen Connolly <st...@gmail.com>
+References: <op...@desktop-2khsk44.mshome.net>
+ <71...@gmx.de>
+ <op...@desktop-2khsk44.mshome.net>
+ <a0...@gmx.de>
+ <op...@desktop-2khsk44.mshome.net>
+From: Karl Heinz Marbaise <kh...@gmx.de>
+Message-ID: <02...@gmx.de>
+Date: Thu, 28 Dec 2017 19:41:39 +0100
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.5.0
+MIME-Version: 1.0
+In-Reply-To: <op...@desktop-2khsk44.mshome.net>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 8bit
+X-Provags-ID: V03:K0:iDkP3LwwdT2xJ3c21T4YndRwlVc68VRzG2zBrb1jN0K4Fk3wH05
+ kL9Fw2VFst+MPJBNhKDBuzT0k9//AOPlve4zhkEb45i5o5fHz60cFqxyUdrx48c2Tbc89L3
+ 7qfqr9UHFEYD2O+qB3YiUdLvYzK7Zwh62XUkdiJktpMqeuK3mAAHHcoNARwRmAB/DukwzbC
+ gnvI1J5Wrw7ETzFykzKvQ==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:WGQaTK6ua1k=:2JsrpSJdUfcsNzTXR2C2es
+ F+S3prAw2RKeFk3tdNAU/kPdkLkgWTxz2hvwY/z0Ojk4ejqa4l8b3bJ/PYA0MXlnAsKoXOJxQ
+ yQ/4S+jeFna5/7wIqCdvkyt4cCxkMBg2T2d31I7EceDXx4ChYIjo+IJMiQUHIP3v7b7ALmGJJ
+ gtHXIs8UpVCHJKeXJcIwNBlZ6j4mgrB6Is0CH3RRIvd+XQju4Nc9oQF2wyoRKfo+fpwredEbH
+ VnDwe36AZ5PQITo1OYGTLUMQAOltMnk8kpibmbzWcaaGTONEg5ADUUBfq8bi0+fzlm2RxEXnP
+ oYfKGqOAQewlS7eZhl4EAG9h81fjGs3+xI8Ap1Ebcwt2nfOQSGSeqCv3a0KYjfPxvSlV3UQo+
+ Tr7fS7cYll2Td/84TH0dCEH4hM6fRCaAy1698NZmoDwvokzYPYDSomSk6GOcl3VbNO4AttG6p
+ JP/0uOOF8jMDydLYxiPvwtLdDT7YM8FujmSgiP8cfLWxQW02HJecT09F99dHSEO+Fm5INRnSq
+ zgeUMPmCgWmNZv2kP3qqTOa5Hk2SzDx/nGTc7C09kqvXaQ25f0P14ZMJg2oa/+3wPopcY5tiw
+ i0RUuUY3FWByCMkkMhO+uUJnjA/rtCUvSXhlFO6LxgnmJ+qgINQ0SrTxlKAuObgjMUFa9ZOkV
+ +6YNkWT2PjujixKhate7TMcJcuyBnG4sAgspvDmPFQjtGK3cuBq3uiZ7N1w1sxEkbUPL4ZT7A
+ quGCiatKl1JmGAnsWJ/CALRawEPe3WoUZz/IrI0kRGcON7jKg3mYihKm6+BAkhIMj4EEX6lPr
+ XWPnLVC6r2MLilCA4GUyw2drFNjpeg9YzZD+jtev24rgsP+BmKi2QEh1Tu0H4UPSmWZusk6
+archived-at: Thu, 28 Dec 2017 18:41:52 -0000
+
+Hi Robert,
+
+So I have restarted the master build based on that and see if everything
+is fine..(which I expect otherwise the branch should have shown the two
+test errors as well)..
+
+Kind regards
+Karl Heinz
+On 28/12/17 19:34, Robert Scholte wrote:
+> Hi Karl Heinz,
+>
+> AFAIK you're hitting https://issues.apache.org/jira/browse/INFRA-15681
+>
+> thanks,
+> Robert
+>
+> On Thu, 28 Dec 2017 19:31:35 +0100, Karl Heinz Marbaise
+> <kh...@gmx.de> wrote:
+>
+>> Hi Robert,
+>>
+>> On 28/12/17 19:10, Robert Scholte wrote:
+>>> Hi Karl Heinz,
+>>> just looking for a +1 from another committer before I merge it back
+>>> to the master.
+>>
+>> Ah ok...So the first question is why is the master at the moment
+>> yellow with two failed tests ? Do you have any clue about that ?
+>>
+>>
+>> Kind regards
+>> Karl Heinz
+>>
+>>
+>>
+>>
+>>
+>>> thanks,
+>>> Robert
+>>> On Thu, 28 Dec 2017 18:55:15 +0100, Karl Heinz Marbaise
+>>> <kh...@gmx.de> wrote:
+>>>
+>>>> Hi Robert,
+>>>>
+>>>>
+>>>> On 28/12/17 17:58, Robert Scholte wrote:
+>>>>> Hi,
+>>>>> Looking for someone to confirm and second MNG-6330[1]
+>>>>
+>>>> how can I help here?
+>>>>
+>>>> Karl Heinz Marbaise
+>>>>
+>>>>> While working on the maven-release-plugin I discovered regression
+>>>>> introduced in Maven 3.5.0 by a change to the ReactorModelCache[2]
+>>>>> This only occurs when a parent was cached and another module points
+>>>>> to this parent, even though the relativePath for this parent
+>>>>> results in a non-existing pom file.
+>>>>> Change is a simple null-check[3]
+>>>>> Regression covered by integration test[4]
+>>>>> Jenkins is happy[5]
+>>>>> thanks,
+>>>>> Robert
+>>>>> [1] https://issues.apache.org/jira/browse/MNG-6330
+>>>>> [2] https://issues.apache.org/jira/browse/MNG-6030
+>>>>> [3]
+>>>>> https://github.com/apache/maven/commit/4eb5747e8229d0201b707052ce7f8ae2fe24eec2
+>>>>> [4]
+>>>>> https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=cfd0cc629c2dd496554c59c1680fb1d90b1311b3
+>>>>> [5]
+>>>>> https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6330_RelativePath/
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 3FCDE200CF3
+ for <ar...@cust-asf2.ponee.io>; Wed, 13 Sep 2017 19:34:48 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 3E9591609CA; Wed, 13 Sep 2017 17:34:48 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 847431609C3
+ for <ar...@cust-asf.ponee.io>; Wed, 13 Sep 2017 19:34:47 +0200 (CEST)
+Received: (qmail 19418 invoked by uid 500); 13 Sep 2017 17:34:46 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 19402 invoked by uid 99); 13 Sep 2017 17:34:46 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2017 17:34:46 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AC02E182CA2
+ for <de...@maven.apache.org>; Wed, 13 Sep 2017 17:34:45 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.721
+X-Spam-Level:
+X-Spam-Status: No, score=-0.721 tagged_above=-999 required=6.31
+ tests=[RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,
+ RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id zjKas5bgqG0l for <de...@maven.apache.org>;
+ Wed, 13 Sep 2017 17:34:44 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 983CC5FBB0
+ for <de...@maven.apache.org>; Wed, 13 Sep 2017 17:34:44 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.fritz.box ([178.12.88.173]) by
+ mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id
+ 0MSY2q-1e1yfQ085E-00RYhU for <de...@maven.apache.org>; Wed, 13 Sep 2017
+ 19:34:44 +0200
+Reply-To: Maven Developers List <de...@maven.apache.org>
+Subject: =?UTF-8?Q?[CANCEL]=c2=a0[VOTE]_Release_Apache_Maven_JMod_Plugin_ver?=
+ =?UTF-8?Q?sion_3.0.0-alpha-1_=28First_Public_Release=29?=
+From: Karl Heinz Marbaise <kh...@gmx.de>
+To: Maven Developers List <de...@maven.apache.org>
+References: <7f...@gmx.de>
+Message-ID: <04...@gmx.de>
+Date: Wed, 13 Sep 2017 19:34:43 +0200
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.2.1
+MIME-Version: 1.0
+In-Reply-To: <7f...@gmx.de>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 7bit
+X-Provags-ID: V03:K0:VyeStN9pfBtUEw1OUHwnN+Fskx3gGA6UI/u3tKNl1MoyMp7lMfV
+ 5f9lA+c64a8VM53VzW6oQGZE+ftvYMT1nb/h274i5XaRmrzwtW26sL3Ef8Eu2/aXPjw48z/
+ f/IoVWNQENObgpMd6W/POGe1qiVIPvb8TnE+KS58Nom4gBC0zRUQHOq/PGYcTBpi2fdMFhk
+ 5yer4NVuydwPmhrj80m3g==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:FW7Ya4bU1gc=:tYBIf+LsCaI8GBLfJLYXOm
+ XcoNBLVqBPN6yQEtgL0/QNGX+NV5WH4lz2CJqPE56FRdkF1ZxDqvRnVvDLioLaBB2Zg1abzAx
+ ugpdPgDj/TdspVebVBmeuAUvDN+qv2kfJBBzuX6eMdCr312EX+jRqi60fS+cRPrMFheBx5LQI
+ xWEXqwL2zJZkA5mnRWAMWXh/7nhHq4e8AxkctovPoJN280s+D8tQ2xEJrgebPojpB352Sqiy9
+ 0sfow4l1NjYdMBxrIpD4J8mkkgyk3yBtpV9lGETLmk64sRz+BmKYbBdM008f+367NWTaELiGK
+ VdsRsa6QKA3Tg/ZDjQX8BrTZHAwGU+pKIjIz0voyz+k58/8J9dvD0Y1X8aHdpvbzajr3C4voM
+ 6butIawKCCQyVt9eXlnMEHF2e+TaeqwFqEA1lKYuak7vRcQJrxfBWugInuCBljDcuqw5kFc5L
+ zhTk8LrVwQKrLWMnmGBvXFKwlFbrgdYIespe2eHX/BJ7M0QuF6fEjqr0AkkycmSpATrR2v5XU
+ MoD6lCcpkA8QV+tsez22aWMt2oOeaLt3fe6upAZVbkATFFGY8lPJTScSkJVcX4dnMUIT8vYR/
+ JfdU4FOPFrsEq6xMmeW1ZXX/UxcWVXuEK+/QaVnysDzb0TrRh8sVBnQ6ktHNje7uptiYKIrxr
+ taCZE9hs3NQTjbA8G5SymOTKimNj04X1J6nJuSQmGLC9aJkmJTRMBpD6B2spz91nRvCHJN2Zj
+ 2/c7Wr/ebb3j/LuO5rEDmRZKqAKuS6KeqJlGRLdxjcaTnVUs6xKQXGRCbYfC56xw5q1v+oazX
+ HP6ca1QNq8yL8tFcNo8IqGdggv6drtnwC3ikFHxTVk6KdUt7po=
+archived-at: Wed, 13 Sep 2017 17:34:48 -0000
+
+I will cancel the VOTE based on found issues..
+
+Kind regards
+Karl Heinz Marbaise
+
+On 09/09/17 15:52, Karl Heinz Marbaise wrote:
+> Hi,
+>
+> this is the VOTE for the first public release for Maven JMod Plugin...
+>
+> We solved 1 issues:
+> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321433&version=12341363
+>
+>
+> There are currently no issues left in JIRA.
+>
+> If you have any issue to report please open an issue in JIRA
+> https://issues.apache.org/jira/projects/MJMOD
+>
+> Staging repo:
+> https://repository.apache.org/content/repositories/maven-1361/
+>
+> https://repository.apache.org/content/repositories/maven-1361/org/apache/maven/plugins/maven-jmod-plugin/3.0.0-alpha-1/maven-jmod-plugin-3.0.0-alpha-1-source-release.zip
+>
+>
+> Source release checksum(s):
+> [NAME-OF]-source-release.zip sha1: 8002767f6cffc7bbbcf76a8e7f0c1799a42caf93
+>
+> Staging site:
+> https://maven.apache.org/plugins-archives/maven-jmod-plugin-LATEST/
+>
+> Guide to testing staged releases:
+> https://maven.apache.org/guides/development/guide-testing-releases.html
+>
+> Vote open for at least 72 hours.
+>
+> [ ] +1
+> [ ] +0
+> [ ] -1
+>
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 5E40C200D13
+ for <ar...@cust-asf2.ponee.io>; Sat, 30 Sep 2017 11:03:06 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 5CB6D1609D5; Sat, 30 Sep 2017 09:03:06 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id A34331609C8
+ for <ar...@cust-asf.ponee.io>; Sat, 30 Sep 2017 11:03:05 +0200 (CEST)
+Received: (qmail 53202 invoked by uid 500); 30 Sep 2017 09:03:04 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 53185 invoked by uid 99); 30 Sep 2017 09:03:04 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Sep 2017 09:03:04 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 79452C2E56;
+ Sat, 30 Sep 2017 09:03:03 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.201
+X-Spam-Level:
+X-Spam-Status: No, score=-0.201 tagged_above=-999 required=6.31
+ tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001]
+ autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id ge8Fg8EIdzB7; Sat, 30 Sep 2017 09:03:02 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DC61C5FCC1;
+ Sat, 30 Sep 2017 09:03:01 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.local ([92.204.69.53]) by mail.gmx.com
+ (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id
+ 0M5Lmp-1d7jlp1W9v-00zT6L; Sat, 30 Sep 2017 11:02:54 +0200
+Reply-To: info@soebes.de
+Subject: Re: [VOTE] Release Apache Doxia Sitetools version 1.7.5
+To: Maven Developers List <de...@maven.apache.org>,
+ Robert Scholte <rf...@apache.org>
+References: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+From: Karl Heinz Marbaise <kh...@gmx.de>
+Message-ID: <04...@gmx.de>
+Date: Sat, 30 Sep 2017 10:24:10 +0200
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.3.0
+MIME-Version: 1.0
+In-Reply-To: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 7bit
+X-Provags-ID: V03:K0:L8Du9h0M6M5IRBA7tEy6ho7HGkZ0fGXX77nbrhttdgS6HpnBc4I
+ ARwsJeku3ZTklb0N3kLcur2teSFZR5WY3XvMPdMzRsSKMnfFCv7XmFyE6mZS0BFMNrhPJeS
+ s3emnCbEgi3Ef8AxZu+2fyMu6xZnMOUmwhKlXIyZKaA6PCcBDkkTFMZobYRdQdMxgDkgXV0
+ /bzXPY6BNFZEEO4J2xgng==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:7tz+gQy7bmk=:5U7ce4R8Ev7QxW/F1HUx5B
+ uuVPv9NZ39UjIswUV6cmX64nv65IhVwM1y6UyHNzTICK+tMTdeyELuW6DyNqpsUAknQGyawrn
+ 9X5bmRHMd2FbCbsPX6hMJ7e9Z1e62gM4ypluSvaQqfxmRBVYVWz4Gwv4QyYO/X8s7YQQcGV8f
+ zBQm4kcFt5R6t74sM77rnNpR7RGv5NU28PE0Go0Q0dftnz54gmSZFsYabVQQ0ZEcnl1oNrAfn
+ 1seJbFNZ1nfLmuMoDEDKz49NmKhqNueSbtAo0UFwdOGTQSugrpL4tOPhoZezelzQwPTDThXSf
+ 7KNNXPvTBthO4Cj9hR78zNuVZzswpJyqvUl6zU87FvtkJ57GCARIFHWuFU1dL/Idqm3NUAxd5
+ Ah4z400ANauEwHp1DcaxfkNiNvKbfoiup7pjk624ucqEeSfId834Uv/GLfiJEdJuL5w2yxvd4
+ 0XoIIxqLVFhYNKdpDkwo0XMssIM03X6QvU1BGi+Wdpp3a8mqy9nZAkwLaPSkZVHwqbJ82/dsG
+ CZRxLOVrqyQwsVyrwM05LqE6bw3iAvPbhTMz1w56dD9nhmPPr+efUVPXp5YOp+u65RfOHNVYs
+ YpEwwatF/MqPyNjSigPuQiZfRirEfyoZbPyq8nZH9kkFs6HXB8UHSDWNCkAOHgotGmUsc0Juc
+ deow4yGjedlFFJH3iLgNQSJwt4r2Gu8L/QiNXgvy7X4qKxFWtMkWKPjyWO+/GTWLvixc4k3Ca
+ kuYYihdjR7NGw9tLYFA3mbyQQB3MjnyfHNx8EV/JV30tlVKvR5s6jlnlhc9c+x+OB+XiUPw6f
+ 7HIFMW+N8Qat0b0YIb02N9O3wstxaaLMtd75hfJdK7WmqWhUMmsoF6W8/bJrymRylgXcs/M
+archived-at: Sat, 30 Sep 2017 09:03:06 -0000
+
+Hi,
+
+Tested with several Maven Versions and JDK's on Mac OS:
+
+jdk1.7.0_79.jdk
+ apache-maven-3.0.5
+ apache-maven-3.1.1
+ apache-maven-3.2.5
+ apache-maven-3.3.1
+ apache-maven-3.3.9
+ apache-maven-3.5.0
+jdk1.8.0_131.jdk
+ apache-maven-3.0.5
+ apache-maven-3.1.1
+ apache-maven-3.2.5
+ apache-maven-3.3.1
+ apache-maven-3.3.9
+ apache-maven-3.5.0
+jdk1.8.0_144.jdk
+ apache-maven-3.0.5
+ apache-maven-3.1.1
+ apache-maven-3.2.5
+ apache-maven-3.3.1
+ apache-maven-3.3.9
+ apache-maven-3.5.0
+jdk1.9.0_ea+181.jdk
+ apache-maven-3.0.5
+ apache-maven-3.1.1
+ apache-maven-3.2.5
+ apache-maven-3.3.1
+ apache-maven-3.3.9
+ apache-maven-3.5.0
+
+without any issue...
+
++1 from me..
+
+Kind regards
+Karl Heinz Marbaise
+
+On 26/09/17 20:51, Robert Scholte wrote:
+> Hi,
+>
+> We solved 5 issues:
+> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12338982&styleName=Text
+>
+>
+> There are still a couple of issues left in JIRA:
+> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
+>
+>
+> Staging repo:
+> https://repository.apache.org/content/repositories/maven-1370/
+> https://repository.apache.org/content/repositories/maven-1370/org/apache/maven/doxia/doxia-sitetools/1.7.5/doxia-sitetools-1.7.5-source-release.zip
+>
+>
+> Source release checksum(s):
+> doxia-sitetools-1.7.5-source-release.zip sha1:
+> 9ab874120bd60f532c167a430d8e077c2914016d
+>
+> Staging site:
+> https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/
+>
+>
+> Guide to testing staged releases:
+> https://maven.apache.org/guides/development/guide-testing-releases.html
+>
+> Vote open for at least 72 hours.
+>
+> [ ] +1
+> [ ] +0
+> [ ] -1
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id A6B6B200CF2
+ for <ar...@cust-asf2.ponee.io>; Sat, 2 Sep 2017 14:06:42 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 9A2C5162CEB; Sat, 2 Sep 2017 12:06:42 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 8E3BD1678E9
+ for <ar...@cust-asf.ponee.io>; Sat, 2 Sep 2017 14:06:41 +0200 (CEST)
+Received: (qmail 19149 invoked by uid 500); 2 Sep 2017 12:06:34 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 19133 invoked by uid 99); 2 Sep 2017 12:06:34 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Sep 2017 12:06:34 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C9CF9C227B;
+ Sat, 2 Sep 2017 12:06:33 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.279
+X-Spam-Level:
+X-Spam-Status: No, score=0.279 tagged_above=-999 required=6.31
+ tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
+ RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024)
+ with ESMTP id ZbE7DZCl_yBc; Sat, 2 Sep 2017 12:06:27 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4D18260CE6;
+ Sat, 2 Sep 2017 12:06:27 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.local ([217.247.16.208]) by
+ mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id
+ 0M4GRv-1dWAfP3Gdf-00rrF8; Sat, 02 Sep 2017 14:06:20 +0200
+Reply-To: info@soebes.de
+Subject: Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.0
+To: Maven Developers List <de...@maven.apache.org>,
+ Robert Scholte <rf...@apache.org>
+References: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <60...@gmx.de>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+From: Karl Heinz Marbaise <kh...@gmx.de>
+Message-ID: <06...@gmx.de>
+Date: Sat, 2 Sep 2017 14:06:20 +0200
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.2.1
+MIME-Version: 1.0
+In-Reply-To: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 7bit
+X-Provags-ID: V03:K0:BADlIR/q4SJAYsUuE/ZLYbbVOGWYG0kPL1hTccF4H8+qJBp3GNP
+ lavZUL63bN3JLeV4CQbIy7pyuG+FY4VF+W0PAb8QpBOFhlkdnF0/X0h9caIU/gyK6q97blT
+ rLL7h9n00tnTBi87+fAeOJaHD37PDlR9Fu5YWvOnZKIr+0cWyFePPvGjX+c6ZMytixeBy/f
+ yGUXnCBZtdeMLHmMNViFA==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:Aq3U3u7HVeE=:lZNYOrB/y4K2oezQuzAPAr
+ pbd9QOaRAD954KUBU9njslVbPh5EIN2rND6cLqT/tX/bdogar/jcUIcweSo+BMWcpVCY6nTOu
+ pmG3o5cftQeo0iefvvlhX1MboBJ7j+B893YtnEMahEyh1rsG2BBrxhJzqK+7WXVYcSZM3mvnC
+ wn78l2zwvWj+eKc/maNM4jC67c1iF0AKwd/9tRE8Iyscmt2bidd/pcb+Ubbm2+DDXERlOcUwc
+ sYrZgRJsr1WpcPRY7FEU7qmEIo0+ssszCdTwJ/l1GFw6inoNq1V24pnlfLT6wyrDIjbfYpPUy
+ 45ILn6DD5n6Zv/VMdiqtAHHv+no/haRFGj7+4IbABHhbngRFPPz+pJISoqeOevaTtG5AydS29
+ zMl45jNqupcU6lkCiP/qWKB6A582lfWfvqkSoFOfa1Pc8E93dS1PYygmhqGcF8+EWQpeTHf4m
+ Xy16prLiLtBx0YgiHbLTqNXqKuwsk1wjfa6qVx2pujLjR9Y+ATY6mV1XZTrifr4N7f/qCq3rb
+ GYjVsQ1eIE6nWLo9QrIMdgzKdDsBGb0ffBAUgDNx1thwaRS5M4MjzIGYLKTVkCS3XxHiRdKDh
+ UZH9RyZ9nwFV8JAoiEM2Hp+FGsrATPQILXLTV+lI2s41hL+QUMo6fXXx78tUqx9MxtjsmO0jg
+ Ftu7Za8wgLMb3UyY3kIDKSfadGNYaM4+6t2AS7aK1+nZKc7ITHYp/Hgrq+WgpD5+KD6Wt0dhO
+ zt05wGM164tC6ZtoVcIMV9dc6Ru8C5pB4UZP76/qEKMOW142KTcAz5cIYnTRo4vWLFg154F1G
+ Qu8J56Bku6Bt0RPuFMQwYeoMJ8Hu+DMIS4EBpz2ou3Ub21YVvg=
+archived-at: Sat, 02 Sep 2017 12:06:42 -0000
+
+Hi Robert,
+
+On 02/09/17 13:30, Robert Scholte wrote:
+> Hi Karl Heinz,
+>
+> this is a problem with the error-prone-compiler[1], a specific
+> implementation of the compiler-api and also where this must be fixed.
+> You might wonder if it should be tested here, but now we are at least
+> aware that current error-prone-compiler is not Java9 compatible. It
+> should not be a blocker for the maven-compiler-plugin itself.
+
+Ok the question is what is exactly the purpose for this
+error-prone-compiler part in Maven-Compiler-Plugin (plexus compiler) and
+what kind of purpose does it fulfill?
+
+Apart from that: +1 from me for releasing maven-compiler-plugin...it
+fixes other issues...
+
+Kind regards
+Karl Heinz Marbaise
+
+>
+> thank,
+> Robert
+>
+> [1]
+> https://github.com/codehaus-plexus/plexus-compiler/tree/master/plexus-compilers/plexus-compiler-javac-errorprone
+>
+>
+>
+> On Sat, 02 Sep 2017 13:23:50 +0200, Karl Heinz Marbaise
+> <kh...@gmx.de> wrote:
+>
+>> Hi,
+>>
+>> I have tested the following combinations:
+>>
+>> jdk1.7.0_79.jdk
+>> apache-maven-3.0.5
+>> apache-maven-3.1.1
+>> apache-maven-3.2.5
+>> apache-maven-3.3.1
+>> apache-maven-3.3.9
+>> apache-maven-3.5.0
+>> jdk1.8.0_131.jdk
+>> apache-maven-3.0.5
+>> apache-maven-3.1.1
+>> apache-maven-3.2.5
+>> apache-maven-3.3.1
+>> apache-maven-3.3.9
+>> apache-maven-3.5.0
+>> jdk1.8.0_144.jdk
+>> apache-maven-3.0.5
+>> apache-maven-3.1.1
+>> apache-maven-3.2.5
+>> apache-maven-3.3.1
+>> apache-maven-3.3.9
+>> apache-maven-3.5.0
+>> jdk1.9.0_ea+181.jdk
+>> apache-maven-3.0.5 FAILED!!
+>> apache-maven-3.1.1 FAILED!!
+>> apache-maven-3.2.5 FAILED!!
+>> apache-maven-3.3.1 FAILED!!
+>> apache-maven-3.3.9 FAILED!!
+>> apache-maven-3.5.0 FAILED!!
+>>
+>>
+>> But the JDK1.9.0_ea+181 have show the following result (for all Maven
+>> versions):
+>>
+>> [ERROR] Failed to execute goal
+>> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
+>> (default-compile) on project error-prone-compiler: Fatal error
+>> compiling: CompilerException: InvocationTargetException:
+>> java.nio.file.NotDirectoryException:
+>> /Library/Java/JavaVirtualMachines/jdk1.9.0_ea+181.jdk/Contents/Home/lib/modules
+>> -> [Help 1]
+>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed
+>> to execute goal
+>> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
+>> (default-compile) on project error-prone-compiler: Fatal error compiling
+>> at
+>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
+>>
+>> at
+>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
+>> at
+>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
+>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
+>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
+>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
+>> at
+>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
+>> Method)
+>> at
+>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
+>>
+>> at
+>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
+>>
+>> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
+>> at
+>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
+>>
+>> at
+>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
+>>
+>> at
+>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
+>>
+>> at
+>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
+>> Caused by: org.apache.maven.plugin.MojoExecutionException:
+>> Fatal error compiling
+>> at
+>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1086)
+>>
+>> at
+>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:168)
+>>
+>> at
+>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
+>>
+>> at
+>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
+>>
+>> ... 19 more
+>> Caused by: org.codehaus.plexus.compiler.CompilerException
+>> at
+>> org.codehaus.plexus.compiler.javac.errorprone.JavacCompilerWithErrorProne.performCompile(JavacCompilerWithErrorProne.java:95)
+>>
+>> at
+>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1075)
+>>
+>> ... 22 more
+>> Caused by: java.lang.reflect.InvocationTargetException
+>> at
+>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
+>> Method)
+>> at
+>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
+>>
+>> at
+>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
+>>
+>> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
+>> at
+>> org.codehaus.plexus.compiler.javac.errorprone.JavacCompilerWithErrorProne.performCompile(JavacCompilerWithErrorProne.java:91)
+>>
+>> ... 23 more
+>> Caused by: java.io.UncheckedIOException:
+>> java.nio.file.NotDirectoryException:
+>> /Library/Java/JavaVirtualMachines/jdk1.9.0_ea+181.jdk/Contents/Home/lib/modules
+>>
+>> at
+>> com.sun.tools.javac.file.Locations$BootClassPathLocationHandler.lazy(Locations.java:725)
+>>
+>> at
+>> com.sun.tools.javac.file.Locations$BootClassPathLocationHandler.isDefault(Locations.java:559)
+>>
+>> at
+>> com.sun.tools.javac.file.Locations.isDefaultBootClassPath(Locations.java:129)
+>>
+>> at
+>> com.sun.tools.javac.file.BaseFileManager.isDefaultBootClassPath(BaseFileManager.java:149)
+>>
+>> at
+>> com.sun.tools.javac.main.Arguments.validate(Arguments.java:411)
+>> at com.sun.tools.javac.main.Main.compile(Main.java:218)
+>> at
+>> com.google.errorprone.BaseErrorProneCompiler.run(BaseErrorProneCompiler.java:187)
+>>
+>> at
+>> com.google.errorprone.BaseErrorProneCompiler.run(BaseErrorProneCompiler.java:98)
+>>
+>> at
+>> com.google.errorprone.ErrorProneCompiler.run(ErrorProneCompiler.java:128)
+>> at
+>> org.codehaus.plexus.compiler.javac.errorprone.JavacCompilerWithErrorProne$CompilerInvoker.compile(JavacCompilerWithErrorProne.java:222)
+>>
+>> ... 28 more
+>> Caused by: java.nio.file.NotDirectoryException:
+>> /Library/Java/JavaVirtualMachines/jdk1.9.0_ea+181.jdk/Contents/Home/lib/modules
+>>
+>> at
+>> java.base/sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:407)
+>>
+>> at
+>> java.base/java.nio.file.Files.newDirectoryStream(Files.java:465)
+>> at java.base/java.nio.file.Files.list(Files.java:3524)
+>> at
+>> com.sun.tools.javac.file.Locations$BootClassPathLocationHandler.systemClasses(Locations.java:678)
+>>
+>> at
+>> com.sun.tools.javac.file.Locations$BootClassPathLocationHandler.computePath(Locations.java:634)
+>>
+>> at
+>> com.sun.tools.javac.file.Locations$BootClassPathLocationHandler.lazy(Locations.java:722)
+>>
+>> ... 37 more
+>> [ERROR]
+>> [ERROR]
+>> [ERROR] For more information about the errors and possible
+>> solutions, please read the following articles:
+>> [ERROR] [Help 1]
+>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
+>> Running post-build script:
+>> /Users/kama/maven-release-checker/release-test/jdk1.9.0_ea+181.jdk/apache-maven-3.0.5/maven-compiler-plugin-3.7.0/target/it/error-prone-compiler/verify.groovy
+>>
+>>
+>>
+>> Based on what I can see here on MacOS: The modules in JDK 9 is a file
+>> and not directory...The question is this an MacOS only phenomenon ? Or
+>> is this a general situation?
+>>
+>> Kind regards
+>> Karl Heinz Marbaise
+>>
+>>
+>> On 01/09/17 15:50, Robert Scholte wrote:
+>>> Hi,
+>>> We solved 6 issues:
+>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341266&styleName=Text
+>>> There are still a couple of issues left in JIRA:
+>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317225%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
+>>> Staging repo:
+>>> https://repository.apache.org/content/repositories/maven-1359/
+>>> https://repository.apache.org/service/local/repositories/maven-1359/content/org/apache/maven/plugins/maven-compiler-plugin/3.7.0/maven-compiler-plugin-3.7.0-source-release.zip
+>>> Source release checksum(s):
+>>> maven-compiler-plugin-3.7.0-source-release.zip sha1:
+>>> 1148d8a1f89e6900afb0ca1dbf74f64932402cfd
+>>> Staging site:
+>>> https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/
+>>> Guide to testing staged releases:
+>>> https://maven.apache.org/guides/development/guide-testing-releases.html
+>>> Vote open for at least 72 hours.
+>>> [ ] +1
+>>> [ ] +0
+>>> [ ] -1
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 6EE2C200D0F
+ for <ar...@cust-asf2.ponee.io>; Fri, 29 Sep 2017 10:42:15 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 6D33A1609D1; Fri, 29 Sep 2017 08:42:15 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id B2B6A1609C5
+ for <ar...@cust-asf.ponee.io>; Fri, 29 Sep 2017 10:42:14 +0200 (CEST)
+Received: (qmail 64024 invoked by uid 500); 29 Sep 2017 08:42:13 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 64011 invoked by uid 99); 29 Sep 2017 08:42:13 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Sep 2017 08:42:13 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A528C1A05BB
+ for <de...@maven.apache.org>; Fri, 29 Sep 2017 08:42:12 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1.821
+X-Spam-Level:
+X-Spam-Status: No, score=-1.821 tagged_above=-999 required=6.31
+ tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3,
+ RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
+ RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001]
+ autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id EbDFVBDJ-Bxg for <de...@maven.apache.org>;
+ Fri, 29 Sep 2017 08:42:11 +0000 (UTC)
+Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 002E961037
+ for <de...@maven.apache.org>; Fri, 29 Sep 2017 08:42:10 +0000 (UTC)
+Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74])
+ by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id v8T8g0BS002527
+ (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK);
+ Fri, 29 Sep 2017 08:42:01 GMT
+Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235])
+ by userv0022.oracle.com (8.14.4/8.14.4) with ESMTP id v8T8g0eO006922
+ (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK);
+ Fri, 29 Sep 2017 08:42:00 GMT
+Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17])
+ by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id v8T8fxbF006405;
+ Fri, 29 Sep 2017 08:41:59 GMT
+Received: from dhcp-ukc1-twvpn-1-vpnpool-10-175-179-64.vpn.oracle.com (/10.175.179.64)
+ by default (Oracle Beehive Gateway v4.0)
+ with ESMTP ; Fri, 29 Sep 2017 01:41:59 -0700
+Subject: Re: [jira] (SUREFIRE-1424) javax.transaction.TransactionManager not
+ visible with Java9
+To: Enrico Olivelli <eo...@gmail.com>,
+ Maven Developers List <de...@maven.apache.org>
+Cc: "Tibor Digana (JIRA)" <ji...@apache.org>,
+ Stephane Nicoll <st...@gmail.com>
+References: <JI...@Atlassian.JIRA>
+ <JI...@jira-lw-us.apache.org>
+ <JI...@Atlassian.JIRA>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+From: Alan Bateman <Al...@oracle.com>
+Message-ID: <09...@oracle.com>
+Date: Fri, 29 Sep 2017 09:41:54 +0100
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
+ Gecko/20100101 Thunderbird/52.3.0
+MIME-Version: 1.0
+In-Reply-To: <CA...@mail.gmail.com>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Transfer-Encoding: 7bit
+Content-Language: en-US
+X-Source-IP: userv0022.oracle.com [156.151.31.74]
+archived-at: Fri, 29 Sep 2017 08:42:15 -0000
+
+On 29/09/2017 08:57, Enrico Olivelli wrote:
+> :
+>
+> 2) dealing with modules like java.sql which as not in java.base
+> (http://download.java.net/java/jdk9/docs/api/java.base-summary.html)
+> Currently I have no solution as there is no official maven dependency
+> for java.sql package
+>
+You shouldn't need to be concerned with the java.sql module. The only
+modules that you need to be concerned about are:
+
+java.corba
+java.transaction
+java.activation
+java.xml.bind
+java.xml.ws
+java.xml.ws.annotation
+
+and the java.se.ee aggregator.
+
+These modules are deprecated in Java SE and are proposed to be removed
+in a future release.
+
+Aside from java.corba, the 5 modules shared with Java EE are standalone
+technologies, each with one or more JSRs and its own download. Each of
+these projects used to be on java.net but moved to the Java EE github
+project recently. I don't know if the move to Eclipse will change
+anything there.
+
+In any case, each of the standalone versions can be deployed on the
+class path with JDK 9.
+
+In time they will be deployable as modules too and this will allow them
+to be deployed on the upgrade module path (--upgrade-module-path) to
+upgrade/override the module in the run-time image with the standalone or
+Java EE module. This will actually work with all except for the
+transaction API as there are a couple of issues to sort out there before
+it can be deployed as a module.
+
+As I understand it, the Spring folks in the JIRA issue are deploying the
+JTA JAR file on the class path. That should just work but is complicated
+by `--add-module=java.se.ee` as that will cause the java.transaction
+module to be resolved. You can't split the javax.transaction package
+between a module and the class path.
+
+For the surefire plugin then dropping the --add-modules should be looked
+at. You'll need to do that anyway once java.se.ee goes away. If the
+plugin relies on JAXB then adding a dependency on the standalone version
+should work.
+
+-Alan
+
+
+
+
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 3C3F5200D6B
+ for <ar...@cust-asf2.ponee.io>; Sun, 31 Dec 2017 13:28:35 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 3AE10160C24; Sun, 31 Dec 2017 12:28:35 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 5AA97160C09
+ for <ar...@cust-asf.ponee.io>; Sun, 31 Dec 2017 13:28:34 +0100 (CET)
+Received: (qmail 14960 invoked by uid 500); 31 Dec 2017 12:28:28 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 14947 invoked by uid 99); 31 Dec 2017 12:28:28 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Dec 2017 12:28:28 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CB933C0C19
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 12:28:27 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.701
+X-Spam-Level:
+X-Spam-Status: No, score=-0.701 tagged_above=-999 required=6.31
+ tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id Y5Hibzy9rNNT for <de...@maven.apache.org>;
+ Sun, 31 Dec 2017 12:28:25 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.17.22])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4D6225FAC4
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 12:28:25 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.local ([92.204.89.202]) by mail.gmx.com
+ (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id
+ 0Metpl-1eGQ9x01gf-00OW6F; Sun, 31 Dec 2017 13:28:24 +0100
+Reply-To: info@soebes.de
+Subject: Re: [IMPORTANT] Re: Git migration next steps
+To: Maven Developers List <de...@maven.apache.org>,
+ =?UTF-8?Q?Herv=c3=a9_BOUTEMY?= <he...@free.fr>
+References: <20...@spooler4-g27>
+ <CA...@mail.gmail.com>
+ <27...@giga> <51...@giga>
+From: Karl Heinz Marbaise <kh...@gmx.de>
+Message-ID: <0c...@gmx.de>
+Date: Sun, 31 Dec 2017 13:28:23 +0100
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.5.0
+MIME-Version: 1.0
+In-Reply-To: <51...@giga>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 8bit
+X-Provags-ID: V03:K0:iHvf3tBLMG58AwcfCd1lKq5wL+APAwoTJiIyEDbGp+1mp2t1EmQ
+ F8E7Cq9veic6YGGsPLw5hHmYVN9or/ZXYkPpTRtICCFmgiqs2E10v71mPwT0ibHjlXP249n
+ N9816Vrd3Y8MBfKQkZcBmD1IWLR/jtqqc2zLkWB8pqZPYBYorkuJ2XsG9HmNOWWxsKflLWe
+ 3coAV8Fav4UomTI9rnXng==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:UaYBrMvC7F0=:BW2Mgg3Eo9mcUhv0CT+hHA
+ TpFdC005iKZhuJSLtI4sLQ1EtQFNo4x7Rql6agJWr30B3u0Swg85k0b8+A/j31l0ylkQ2u84c
+ 5OnaQGG0LqVnauY7DNiSzgjxc22JiJTHDlRgy/JyrU0/4OVUrTAaF2vMsjRBvWjPn83cRtovN
+ 0/nB0KUZBajn1ugq7F4gu673OfcWZHOFvHNYTtq0p6e9tM3N56GiQBkYoP26M8RHsiTcPJUV0
+ fjY2pxVIYnLDg+v1pEGZk6TLNgrpwCcaIcbuhC0JspN0P2XrMaf9h7DomVeeHh9m7IQCfAZo7
+ FeXNAl/AnULUTAlXhrfai6N2rc5v9I8Oqqhs1WDopjWHAXWTPmkZxY57Q6dybh/51qWSvBkKn
+ DWFNaQzmWNFScoZiU8eMubidmLtSwLFLv+aPp4IRVNkcATD7xhrdmm/NFpoSIxXm+iS5MCCXD
+ I7645VlR7Y1eAP6porBQaTyFfRCHLx/mXMP/9gsFPlD1mv1ssacOkbgm2DNbWaS5Gn/R4OdEu
+ lPY3SVRn1fHkccAotQovJyYpN90GChAZb8OZj8Ni2LITRyikcGeLMuRmaCYGdUKmv4aycnWlu
+ 8q2OzOVi+9D4fd1wPoWgXuT3wvdZWE6LHSN5nS7D8e0uHbMraj9GzWrqCdmycV1IyzHyITGUL
+ sY706vealfvjxPdMVClMOCEfTzjq8oqiVxlNiT6qVT8SkJMpXZnIZzW3Ny0F24FgmBVV+zAzk
+ +sYHRNSuBRbqK1NksY5zi1DQ0GE0rOI+2d3fiAshjGVhh/MWYRvrDlwYO7gviQlRnyNgscX8u
+ CEetOrWSllBJwtcemhp/cCpIJfJWWGHszFfdJvQS8txYsrOFfk=
+archived-at: Sun, 31 Dec 2017 12:28:35 -0000
+
+Hi,
+
+On 31/12/17 12:44, Hervé BOUTEMY wrote:
+> another interesting case:
+> https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/
+>
+> when you look at each step logs from the stage view, you see no issue
+> but the build is marked as failed
+>
+> and if you look at the unit tests marked as failed:
+> https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/
+> lastCompletedBuild/testReport/
+
+The failures on the tests here are based on the issue with the "@" in
+the directory name (See
+https://issues.apache.org/jira/browse/SUREFIRE-1312)..
+
+Upgrading to surefire 2.20.1 will solve that problem..(Based on the
+current state of my experience)...
+
+See
+https://builds.apache.org/job/maven-box/job/maven-shared-utils/job/master/4/
+
+Kind regards
+Karl Heinz
+
+
+
+>
+> you don't know on which build (OS*JDK) the failures happen
+>
+> IMHO, in parallel to the javadoc IT failure investigation, this maven-shared-
+> utils gives us another interesting case to fix
+>
+> Regards,
+>
+> Hervé
+>
+> Le dimanche 31 décembre 2017, 11:49:59 CET Hervé BOUTEMY a écrit :
+>> Le dimanche 31 décembre 2017, 11:05:39 CET Stephen Connolly a écrit :
+>> [...]
+>>
+>>>>> what are all the open tasks links?
+>>>>
+>>>> was supposed to be fixed after Jenkins plugin upgrade this week
+>>>> @Stephen is this a known issue?
+>>>
+>>> I may have to tweak the shared lib also. It will be Tuesday before I turn
+>>> on my Mac
+>>
+>> perfect: have nice holidays, working on it next year is perfect :)
+>>
+>> [...]
+>>
+>>>>> Honestly the current jenkins result is complicated to use....
+>>>>
+>>>> when the reseult is a passing build, it's perfect, but I confirm that
+>>>> when
+>>>> there is a failure, it's a pain to understand where is the failure
+>>>> (which
+>>>> OS/
+>>>> jdk, which test)
+>>>> and eventually detect if there are false positives on some conditions...
+>>>
+>>> So there are two issues imho:
+>>>
+>>> 1. Fast fail kills other parallel executions in such a way that they
+>>> report
+>>> as failed. I’d like them to flag as aborted instead. That would make
+>>> identification from the stage view or blue ocean easier.
+>>
+>> yes, this would be a good first enhancement
+>>
+>>> 2. The parallel logs. This is a pipeline design decision. You are better
+>>> off viewing logs through stage view or blue ocean.
+>>
+>> last time I tried, I did not find output clear: but perhaps it was on
+>> aborted builds marked as failed... I'll have to try with that issue in
+>> mind.
+>>>>> And as far I can see SNAPSHOT are not anymore deployed whereas they
+>>>>> were
+>>>>> deployed previously.
+>>>>> IMHO it's very convenient as some users test our fixes....
+>>>>
+>>>> @Stephen adding auto-deploy for master branch could make sense, isn't
+>>>> it?
+>>>
+>>> I really think auto-deploy of snapshots is an anti-pattern. If we want it
+>>> to be for CI only in a CI dedicated repo, I can find that acceptable...
+>>> but
+>>> otherwise I really hate the idea.
+>>
+>> I don't understand: a SNAPSHOT-dedicated repository is like a mini
+>> continuous deployment. We have a SNAPSHOT-dedicated repository exactly for
+>> that, configured as repositories and distributionManagement in Apache
+>> Parent POM http://maven.apache.org/pom/asf/
+>>
+>> I understand there are issues if we auto-deploy from branches, since we have
+>> no version scheme to make a difference in the SNAPSHOT repo for every
+>> branch: that's why I restrict the auto-deployment to master.
+>>
+>> But it's the first time I hear about issues with a SNAPSHOT repo to make
+>> SNAPSHOTs public (as SNAPSHOTs, ie advertized as latest & non-reproducible,
+>> to test early): the only issues I understood was about people wanting to
+>> make these reproducible, then avoid SNAPSHOT and call it "continuous
+>> delivery" (which IMHO adds a lot of unused releases that you can't delete
+>> if you don't master precisely who your consumers are: then in such open
+>> situation, you get a bloated repo...)
+>>
+>> Regards,
+>>
+>> Hervé
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id A82D9200D68
+ for <ar...@cust-asf2.ponee.io>; Thu, 28 Dec 2017 21:17:01 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id A608C160C1F; Thu, 28 Dec 2017 20:17:01 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id C607C160C00
+ for <ar...@cust-asf.ponee.io>; Thu, 28 Dec 2017 21:17:00 +0100 (CET)
+Received: (qmail 54255 invoked by uid 500); 28 Dec 2017 20:16:59 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 54244 invoked by uid 99); 28 Dec 2017 20:16:59 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Dec 2017 20:16:59 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id F188A1A0E76
+ for <de...@maven.apache.org>; Thu, 28 Dec 2017 20:16:58 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.701
+X-Spam-Level:
+X-Spam-Status: No, score=-0.701 tagged_above=-999 required=6.31
+ tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id NS8GLhPSgQRu for <de...@maven.apache.org>;
+ Thu, 28 Dec 2017 20:16:57 +0000 (UTC)
+Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id CC7A85F396
+ for <de...@maven.apache.org>; Thu, 28 Dec 2017 20:16:56 +0000 (UTC)
+Received: from Karl-Heinzs-MacBook-Pro.local ([92.204.46.47]) by mail.gmx.com
+ (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id
+ 0Md3li-1eDXSl1WBW-00IEDj; Thu, 28 Dec 2017 21:16:49 +0100
+Reply-To: info@soebes.de
+Subject: Re: plexus-archiver / plexus-util Issue
+To: Stephen Connolly <st...@gmail.com>,
+ Maven Developers List <de...@maven.apache.org>, info@soebes.de
+References: <95...@gmx.de>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <23...@gmx.de>
+ <CA...@mail.gmail.com>
+ <1c...@gmx.de>
+ <CA...@mail.gmail.com>
+From: Karl Heinz Marbaise <kh...@gmx.de>
+Message-ID: <0c...@gmx.de>
+Date: Thu, 28 Dec 2017 21:16:48 +0100
+User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
+ Gecko/20100101 Thunderbird/52.5.0
+MIME-Version: 1.0
+In-Reply-To: <CA...@mail.gmail.com>
+Content-Type: text/plain; charset=utf-8; format=flowed
+Content-Language: en-GB
+Content-Transfer-Encoding: 8bit
+X-Provags-ID: V03:K0:dVGX7oktciP1fwFj4l5sifNRnbSzWWApvhMLKe2W/XUzcOpFAf2
+ /39HAn8JYzqhPMpjwUa8dknxL3aNjH5PhC9NbIgtJBbGkEJA2NsgRrLoeehjg6zqLnw+RrW
+ E6kCBuRczZ2dfIk9sPtPMoZhalG4+Lv49TKtEsvcpf/At8ap/hyxJdY1h9QpAf+tYtnWSsc
+ 4uN2wnl0AUwmQvZSl92pQ==
+X-UI-Out-Filterresults: notjunk:1;V01:K0:Z1gvNe4a5wA=:+sG6KinJEqS3RKY4BZ8L3w
+ 71pSNaVTekZqNyk+RPjFoKkRtaDP2T2gROAPSV/dCC0BRkfb6s+T1/g23spvzzxtfqayXBXzX
+ dUM5J5v6dep6Kz7xBgEH5zH12W+819laLZ96BgMBDEWcy6eumXJEQTfj/QQypVC3ExJuU+b8z
+ zzEk0FFTzLXwCYxp3bizTSU30Dcthp8CUfcctM3O5PgDNuzndcde9NrdEE8InDcGKc7Wtv3kB
+ Mzx+JYDlYnr3pJ8heGmzrx/UydP/aKNSfVp4pW9SDmTzTFAVPmFC2ybdoB7/aIXP9fKXiROLg
+ aSi705FnFreUkKuI0tH2BMrdSrTDNVNbjpjcxYj7ypsDWWX/t2fReNthQqU0vexYILudcDZMg
+ /rSf4gUfqzpyrfZWg0x1bghLPg+8Cy9TbJ4Pyd59YzfhkSCo9XHw0E74KGvbsdvlXQe6zwSiP
+ 50r2bhPBfGjP1zlf1M8TsfoRCnELSgJos6TSNcChgMnT8EhmkWE6upJqwoAaw+G8ogOg+i3Yh
+ eeh3tfABFygpLT8D/gOpLcKnEePYb6c6COjC7I4D8Ax2igKk7bNMg/XefzRnbeGvbvgSAPI35
+ 57C0h6fJrwGfAOV+SKrIuZ1B/BjQRuPOglwA0M4+lopafLYZmXCwT4IwsxM1Kg1uCoUVOSikK
+ To0UdpxY+rX0aJ8U+KgrabtwxCS/9+TiDh3ZamPMNR2IZFFl4scQ2hR8lMipROszu+lgw8xdM
+ KMZnIbQ/Z8Mwn+fis3CBQSWmEjPRj6tWKWBkS5hUurtbg6cop+OzyOv87tMTcpt4YaqBFS/Ht
+ iLGR1FwJNSEaDW1U2QGbKWt4kkBYG+PRkDasQ4vxeXoKOB2ZS1H0pyiWt9ZHaTaGqwLwjzP5p
+ Tn/QGn0wJlQOsxuW066atWt0Vo1aHWRpPSntzKwByr+j9oomwe76HZzAO48qim24tuUACjSde
+ hGSs6hNionA==
+archived-at: Thu, 28 Dec 2017 20:17:01 -0000
+
+Hi,
+
+On 28/12/17 20:46, Stephen Connolly wrote:
+> But shouldn’t we be copying the last modified time stamp always anyway
+
+I'm the same opinion...but that means in consequence that the test in
+plexus-archiver is not correct...cause it's waiting for a change in the
+last-modified time ...
+
+Hm...
+
+Kind regards
+Karl Heinz Marbaise
+
+
+>
+> On Thu 28 Dec 2017 at 14:52, Karl Heinz Marbaise <khmarbaise@gmx.de
+> <ma...@gmx.de>> wrote:
+>
+> Hi,
+>
+> after diving more into this..
+>
+> I found that if I upgrade plexus-utils to 3.1.0 in plexus-archiver the
+> tests in plexus-archiver stuck completely...as I already observed (which
+> I though was another cause)...
+>
+> https://travis-ci.org/codehaus-plexus/plexus-archiver/jobs/321821294
+>
+> So more diving into the details I realized that the following code in
+> plexus-utils causes the issue:
+>
+> FileUtils.java:
+>
+> private static void doCopyFile( File source, File destination )
+> throws IOException
+> {
+> // offload to operating system if supported
+> if ( Java7Detector.isJava7() )
+> {
+> doCopyFileUsingNewIO( source, destination );
+> }
+> else
+> {
+> doCopyFileUsingLegacyIO( source, destination );
+> }
+> }
+>
+> The real issue is located in the implementation of doCopyFileUsingNewIO
+> which uses:
+>
+>
+>
+> public static File copy( File source, File target )
+> throws IOException
+> {
+> Path copy = Files.copy( source.toPath(), target.toPath(),
+> StandardCopyOption.REPLACE_EXISTING,
+> StandardCopyOption.COPY_ATTRIBUTES,
+> LinkOption.NOFOLLOW_LINKS );
+> return copy.toFile();
+> }
+>
+> and If I correctly understand the whole thing is the real cause of that
+> based on the usage of StandardCopyOption.COPY_ATTRIBUTES which includes
+> copying of the last-modified of the file...which means not to change the
+> last-modified entry of the file and in result that is the reason of not
+> changing it and the stucking of the unit test in plexus-archiver...(see
+> travis build above)..
+>
+>
+> After I have changed that and only use
+>
+> public static File copy( File source, File target )
+> throws IOException
+> {
+> Path copy = Files.copy( source.toPath(), target.toPath(),
+> StandardCopyOption.REPLACE_EXISTING,
+> LinkOption.NOFOLLOW_LINKS );
+> return copy.toFile();
+> }
+>
+> it looks like working (see branch issue-fix):
+>
+> What Do you think?
+>
+> Kind regards
+> Karl Heinz Marbaise
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id AAF4D200D79
+ for <ar...@cust-asf2.ponee.io>; Sun, 31 Dec 2017 01:02:35 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id A98DA160C35; Sun, 31 Dec 2017 00:02:35 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 787AF160C22
+ for <ar...@cust-asf.ponee.io>; Sun, 31 Dec 2017 01:02:34 +0100 (CET)
+Received: (qmail 2351 invoked by uid 500); 31 Dec 2017 00:02:33 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 2340 invoked by uid 99); 31 Dec 2017 00:02:33 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Dec 2017 00:02:33 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A59D01805C8
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 00:02:32 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id s3RuiDsQkTp7 for <de...@maven.apache.org>;
+ Sun, 31 Dec 2017 00:02:29 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 644005F3CC
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 00:02:28 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d30 with ME
+ id sQ2M1w00S20Ufdy03Q2MtE; Sun, 31 Dec 2017 01:02:22 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Sun, 31 Dec 2017 01:02:22 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Cc: sconnolly@cloudbees.com
+Subject: Re: [IMPORTANT] Re: Git migration next steps
+Date: Sun, 31 Dec 2017 01:02:21 +0100
+Message-ID: <10...@giga>
+In-Reply-To: <CA...@mail.gmail.com>
+References: <20...@spooler4-g27> <19...@giga> <CA...@mail.gmail.com>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Sun, 31 Dec 2017 00:02:35 -0000
+
+Le dimanche 31 d=E9cembre 2017, 00:04:59 CET Olivier Lamy a =E9crit :
+> works fine (on my machine :-) )
+> OSX + java 1.8.0_121
+ok, I had a deeper look: the IT expects a warning that exists with Java 8=20
+(missing @param) but not Java 7 (more permissive on documentation)
+I added a serialwarn: this causes a warning in Java 7 also, then fixes the =
+IT
+
+There is no issue on my machine any more :)
+
+>=20
+> Well TBH I'm a bit lost with Jenkins result display....
+> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-jav=
+ado
+> c-plugin/job/master/
+>=20
+> what are all the open tasks links?
+was supposed to be fixed after Jenkins plugin upgrade this week
+@Stephen is this a known issue?
+
+>=20
+> I'm even more lost If I look at a build result
+> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-jav=
+ado
+> c-plugin/job/master/3/ changes are duplicated
+> junit result says failure
+> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-jav=
+ado
+> c-plugin/job/master/3/testReport/ but looking at failed test result says
+> passed
+> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-jav=
+ado
+> c-plugin/job/master/3/testReport/org.apache.maven.plugins.javadoc/Javadoc=
+Rep
+> ortTest/testJavadocResources/
+>=20
+> As I can understand all build logs (linux/windows with different jdks) are
+> totally mixed up all together
+> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-jav=
+ado
+> c-plugin/job/master/3/consoleFull TBH it a really big pain to read!! I do=
+n't
+> want to spend hours on that..... So after wasting a bit of time it looks
+> the build is failing on windows only
+it seems it's another completely unrelated issue to mine, which was related=
+ to=20
+Java 7 not getting any warning on an IT that expected a warning
+
+>=20
+> [windows-jdk8] [WARNING] The following builds failed:[windows-jdk8]
+> [WARNING] * detectLinks\pom.xml
+>=20
+>=20
+> [windows-jdk7] [WARNING] The following builds failed:
+>=20
+> [windows-jdk7] [WARNING] * detectLinks\pom.xml
+>=20
+>=20
+> Honestly the current jenkins result is complicated to use....
+when the reseult is a passing build, it's perfect, but I confirm that when=
+=20
+there is a failure, it's a pain to understand where is the failure (which O=
+S/
+jdk, which test)
+and eventually detect if there are false positives on some conditions...
+
+> And as far I can see SNAPSHOT are not anymore deployed whereas they were
+> deployed previously.
+> IMHO it's very convenient as some users test our fixes....
+@Stephen adding auto-deploy for master branch could make sense, isn't it?
+
+>=20
+> @herve do you have any logs regarding the build failing for you.
+>=20
+> On 30 December 2017 at 20:51, Herv=E9 BOUTEMY <he...@free.fr> wro=
+te:
+> > merge done: can you check it's as you expected?
+> >=20
+> > notice that if you have failing IT on MJAVADOC-508 like I have locally,
+> > it's
+> > not the merge but it was already present before
+> >=20
+> > @Olivier: I don't know in which conditions you tested MJAVADOC-508, but=
+ it
+> > is
+> > failing for me: Linux+Java 7
+> >=20
+> > Regards,
+> >=20
+> > Herv=E9
+> >=20
+> > Le jeudi 28 d=E9cembre 2017, 09:48:31 CET Herv=E9 BOUTEMY a =E9crit :
+> > > on maven-javadoc-plugin: what about merging master2 branch into maste=
+r,
+> >=20
+> > like
+> >=20
+> > > if it was a PR?
+> > > In general, I don't like this way of doing PR merges (I prefer rebasi=
+ng
+> >=20
+> > or
+> >=20
+> > > cherry picking, to avoid the merge commit and the parallel branches
+> >=20
+> > staying
+> >=20
+> > > for ever in the repo), but since this way of merging PRs is often used
+> > > by
+> > > the team, let's use this technique on the current case where it makes
+> > > our
+> > > life easier
+> > >=20
+> > > Regards,
+> > >=20
+> > > Herv=E9
+> > >=20
+> > > Le dimanche 24 d=E9cembre 2017, 13:04:56 CET Robert Scholte a =E9crit=
+ :
+> > > > I did the assumption that you can isolate all maven-javadoc-plugin
+> > > > commits.
+> > > > If it is for all maven-plugins or nothing, then it is a different
+> >=20
+> > story.
+> >=20
+> > > > On Sun, 24 Dec 2017 10:54:16 +0100, <he...@free.fr> wrote:
+> > > > > I'd suggest to try the process to a personal personal repo on Git=
+Hub
+> >=20
+> > to
+> >=20
+> > > > > see if you're able to get a better result before involving manual
+> >=20
+> > work
+> >=20
+> > > > > from INFRA (on more than 60 repos...)
+> > > > >=20
+> > > > > (it's sad to see nobody try to explain what's happenning or impro=
+ve
+> >=20
+> > the
+> >=20
+> > > > > documented commands, just get to a conclusion: re-do everything a=
+nd
+> > > > > pray)
+> > > > >=20
+> > > > > Regards,
+> > > > >=20
+> > > > > Herv=E9
+> > > > >=20
+> > > > > ----- Mail original -----
+> > > > > De: "Karl Heinz Marbaise" <kh...@gmx.de>
+> > > > > =C0: "Maven Developers List" <de...@maven.apache.org>, "Robert Scho=
+lte"
+> > > > > <rf...@apache.org>
+> > > > > Envoy=E9: Dimanche 24 D=E9cembre 2017 10:47:43
+> > > > > Objet: Re: [IMPORTANT] Re: Git migration next steps
+> > > > >=20
+> > > > > Hi,
+> > > > >=20
+> > > > > On 24/12/17 10:40, Robert Scholte wrote:
+> > > > >> How about a hard reset or dropping the repo and doing it all over
+> > > > >> again?
+> > > > >=20
+> > > > > If I correctly seen that ..there had no commit yet on the new git
+> > > > > repos..
+> > > > >=20
+> > > > > So I think it would be the easiest way to do as Robert suggest ..=
+=2Eto
+> > > > > redo migration for those repos..
+> > > > >=20
+> > > > > Kind regards
+> > > > > Karl Heinz
+> > > > >=20
+> > > > >> On Wed, 20 Dec 2017 10:42:36 +0100, Herv=E9 BOUTEMY
+> > > > >>=20
+> > > > >> <he...@free.fr> wrote:
+> > > > >>> INFRA-15679 fixed by infra team
+> > > > >>> then I re-run migrate-plugins.sh script to split the svn2git
+> >=20
+> > mirror to
+> >=20
+> > > > >>> per-
+> > > > >>> plugin git repo
+> > > > >>> and I pushed "master2" branches for m-javadoc-p, m-site-p and
+> >=20
+> > m-pdf-p,
+> >=20
+> > > > >>> which
+> > > > >>> were the 3 plugins which suffered from missing commits
+> > > > >>>=20
+> > > > >>> on m-site-p and m-pdf-p, I'll cherry pick the unique commit that
+> >=20
+> > was
+> >=20
+> > > > >>> missed:
+> > > > >>> not a big deal
+> > > > >>>=20
+> > > > >>> on m-javadoc-p, the situation is more coplex, since there was a
+> > > > >>> release
+> > > > >>>=20
+> > > > >>> I also noticed that I forgot to push tags when importing: I
+> >=20
+> > started to
+> >=20
+> > > > >>> do "git
+> > > > >>> push --tags", but the result does not look as I expected: it
+> >=20
+> > creates a
+> >=20
+> > > > >>> lot of
+> > > > >>> parallel branches
+> > > > >>>=20
+> > > > >>> I'll need help from git experts: what is happening?
+> > > > >>>=20
+> > > > >>> I stopped the tags push half the way, we'll need to decide what=
+ to
+> > > > >>> do...
+> > > > >>> (I knew I was not a git expert and there was a risk for somethi=
+ng
+> > > > >>> weird like
+> > > > >>> what's currently happening...)
+> > > > >>>=20
+> > > > >>> Any hint?
+> > > > >>>=20
+> > > > >>> Regards,
+> > > > >>>=20
+> > > > >>> Herv=E9
+> > > > >>>=20
+> > > > >>> Le samedi 16 d=E9cembre 2017, 16:28:48 CET Herv=E9 BOUTEMY a =
+=E9crit :
+> > > > >>>> ok, I was confused by the different takes at m-javadoc-p 3.0.0
+> > > > >>>>=20
+> > > > >>>> yes, svn2git mirror is stuck [1] at r1815675
+> > > > >>>>=20
+> > > > >>>> I just opened an INFRA Jira issue
+> > > > >>>> https://issues.apache.org/jira/browse/INFRA-15679
+> > > > >>>>=20
+> > > > >>>> once the svn2git mirror will be updated, we'll have to re-run =
+the
+> > > > >>>> split
+> > > > >>>> scripts and cherry pick the missing commits
+> > > > >>>>=20
+> > > > >>>> Regards,
+> > > > >>>>=20
+> > > > >>>> Herv=E9
+> > > > >>>>=20
+> > > > >>>> [1] https://github.com/apache/maven-plugins/commits/trunk
+> > > > >>>>=20
+> > > > >>>> Le samedi 16 d=E9cembre 2017, 13:01:05 CET Robert Scholte a =
+=E9crit :
+> > > > >>>> > I was triggered by some failing unit tests, which should have
+> >=20
+> > been
+> >=20
+> > > > >>>> solved
+> > > > >>>>=20
+> > > > >>>> > in maven-javadoc-plugin-3.0.0
+> > > > >>>> >=20
+> > > > >>>> > My last commit according to GIT was november 18th
+> > > > >>>> > My last commit according to SVN was december 3rd
+> > > > >>>> >=20
+> > > > >>>> > comparing svnlog with gitlog most of these commits are lost:
+> > > > >>>> >=20
+> > > > >>>> > moved to git
+> > > > >>>> > ----
+> > > > >>>> > [maven-release-plugin] prepare for next development iteration
+> > > > >>>> > ----
+> > > > >>>> > [maven-release-plugin] prepare release
+> >=20
+> > maven-javadoc-plugin-3.0.0
+> >=20
+> > > > >>>> > ----
+> > > > >>>> > [MJAVADOC-498] "module not found" when Java 9 module-info
+> >=20
+> > present
+> >=20
+> > > > >>>> > Support aggrated javadoc
+> > > > >>>> > ----
+> > > > >>>> > Skip several unittests for Java9
+> > > > >>>> > ----
+> > > > >>>> > JDK-8032205 was closed as not an issue, so not solved in Jav=
+a9.
+> > > > >>>> > Need to review the conclusion
+> > > > >>>> > ----
+> > > > >>>> > Upgrade mockito to remove warning about illegal reflective
+> >=20
+> > access
+> >=20
+> > > > >>>> > ----
+> > > > >>>> > Improve TestJavadocReportTest#testTestJavadoc
+> > > > >>>> > J8 warns and continues with missing dependency, J9 fails.
+> > > > >>>> > In fact test was wrong: dependency should have been on
+> > > > >>>> > classpath
+> > > > >>>> > ----
+> > > > >>>> > unittest should prefer JAVA_HOME when executing from cmdline
+> > > > >>>> > When running with Java9+ no need to switch from jre to jdk
+> > > > >>>> > directory
+> > > > >>>> > (jep220)
+> > > > >>>> > ----
+> > > > >>>> > MJAVADOC-502 Update DEFAULT_JAVA_API_LINKS
+> > > > >>>> > ----
+> > > > >>>> > session is required parameter, so cannot be null. Fix related
+> > > > >>>>=20
+> > > > >>>> unittests
+> > > > >>>>=20
+> > > > >>>> > ----
+> > > > >>>> > Add project/artifact key to set of sourcePaths to recognize
+> >=20
+> > reactor
+> >=20
+> > > > >>>> > projects versus dependencies
+> > > > >>>> > ----
+> > > > >>>> > Group sets of sourcepaths per project, in prepare of usage of
+> > > > >>>> > module-source-path.
+> > > > >>>> > ----
+> > > > >>>> > Switch from List to Collection to make it easier to use Sets
+> >=20
+> > when
+> >=20
+> > > > >>>> > preferred
+> > > > >>>> > ----
+> > > > >>>> > [maven-release-plugin] prepare for next development iteration
+> > > > >>>> > ----
+> > > > >>>> > [maven-release-plugin] prepare release
+> >=20
+> > maven-javadoc-plugin-3.0.0
+> >=20
+> > > > >>>> > ----
+> > > > >>>> >=20
+> > > > >>>> >=20
+> > > > >>>> >=20
+> > > > >>>> >=20
+> > > > >>>> > On Sat, 16 Dec 2017 12:53:23 +0100, Herv=E9 BOUTEMY
+> > > > >>>>=20
+> > > > >>>> <he...@free.fr>
+> > > > >>>>=20
+> > > > >>>> > wrote:
+> > > > >>>> > > looking at commits@ content https://lists.apache.org/list.
+> >=20
+> > html?
+> >=20
+> > > > >>>> > > commits@maven.apache.org with subject containing
+> > > > >>>>=20
+> > > > >>>> "maven/plugins/trunk"
+> > > > >>>>=20
+> > > > >>>> > > and plugins svn2git mirror
+> > > > >>>> > > https://github.com/apache/maven-plugins/commits/
+> > > > >>>> > > trunk
+> > > > >>>> > >=20
+> > > > >>>> > > only 1 commit is missing: my latest commit on
+> >=20
+> > maven-site-plugin
+> >=20
+> > > > >>>> > > (the last commit for Git migration is not useful)
+> > > > >>>> > >=20
+> > > > >>>> > >=20
+> > > > >>>> > > Same on shared showed no missing commit.
+> > > > >>>> > >=20
+> > > > >>>> > >=20
+> > > > >>>> > > what latest commit of maven-javadoc-plugin are you looking
+> >=20
+> > for?
+> >=20
+> > > > >>>> > > Regards,
+> > > > >>>> > >=20
+> > > > >>>> > > Herv=E9
+> > > > >>>> > >=20
+> > > > >>>> > > Le samedi 16 d=E9cembre 2017, 11:56:31 CET Robert Scholte a
+> >=20
+> > =E9crit :
+> > > > >>>> > >> For everybody just a warning I faced today:
+> > > > >>>> > >> If you switch to the git repos, please make sure all comm=
+its
+> >=20
+> > are
+> >=20
+> > > > >>>> > >> migrated.
+> > > > >>>> > >> I noticed the latest commits of the maven-javadoc-plugin =
+got
+> > > > >>>>=20
+> > > > >>>> lost.
+> > > > >>>>=20
+> > > > >>>> > >> thanks,
+> > > > >>>> > >> Robert
+> > > > >>>> > >>=20
+> > > > >>>> > >> On Sat, 09 Dec 2017 17:06:09 +0100, Stephen Connolly
+> > > > >>>> > >>=20
+> > > > >>>> > >> <st...@gmail.com> wrote:
+> > > > >>>> > >> > I see we have a large number of repos now on gitbox ;-)
+> > > > >>>> > >> >=20
+> > > > >>>> > >> > On Thu 7 Dec 2017 at 07:00, Herv=E9 BOUTEMY
+> > > > >>>>=20
+> > > > >>>> <he...@free.fr>
+> > > > >>>>=20
+> > > > >>>> > >> wrote:
+> > > > >>>> > >> >> ok, I didn't update my repo clone: now the run-its
+> >=20
+> > profile is
+> >=20
+> > > > >>>> > >> activated
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> then the plan should just confirm "it works!" :)
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> and find which jobs are special, like maven-dist-tool
+> >=20
+> > (which
+> >=20
+> > > > >>>> has to
+> > > > >>>>=20
+> > > > >>>> > >> be
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> scheduled daily instead of code change, and one platfo=
+rm
+> > > > >>>> > >> >> only)
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> Regards,
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> Herv=E9
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> Le mercredi 6 d=E9cembre 2017, 23:58:45 CET Stephen
+> >=20
+> > Connolly a
+> >=20
+> > > > >>>> =E9crit :
+> > > > >>>> > >> >> > On Wed 6 Dec 2017 at 22:38, Herv=E9 BOUTEMY
+> > > > >>>>=20
+> > > > >>>> <he...@free.fr>
+> > > > >>>>=20
+> > > > >>>> > >> >> wrote:
+> > > > >>>> > >> >> > > Now that we have 2 ASF Organization Jenkins jobs (=
+one
+> >=20
+> > for
+> >=20
+> > > > >>>> gitbox
+> > > > >>>>=20
+> > > > >>>> > >> [1]
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> and
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > one
+> > > > >>>> > >> >> > > for git-wip: thank you Stephen) and that it looks
+> >=20
+> > quite
+> >=20
+> > > > >>>> > >> successful,
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> let's
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > plan
+> > > > >>>> > >> >> > > the next steps.
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > Here is what I see:
+> > > > >>>> > >> >> > > 1. removal of hand-defined Jenkins jobs that are n=
+ow
+> > > > >>>>=20
+> > > > >>>> duplicates
+> > > > >>>>=20
+> > > > >>>> > >> >> > > 2. preparation of the 60 new empty git repos for
+> >=20
+> > shared &
+> >=20
+> > > > >>>> > >> >> > > plugins
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > 3. migration of the 1 shared component and 1 plugin
+> >=20
+> > using
+> >=20
+> > > > >>>> > >> >> migrate-*.sh
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > scripts
+> > > > >>>> > >> >> > > [3] to test and eventually rework the Jenkinsfile =
+(I
+> > > > >>>>=20
+> > > > >>>> suppose it
+> > > > >>>>=20
+> > > > >>>> > >> will
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> > > require
+> > > > >>>> > >> >> > > some little change, to run add "run-its" profile)
+> > > > >>>> > >> >> >=20
+> > > > >>>> > >> >> > As far as I recall, I added -P+run-its already
+> > > > >>>> > >> >> >=20
+> > > > >>>> > >> >> > For the plugin, I'd like to do the job for
+> > > > >>>>=20
+> > > > >>>> maven-site-plugin,
+> > > > >>>>=20
+> > > > >>>> > >> since we
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> > > expect
+> > > > >>>> > >> >> > > to release it soon.
+> > > > >>>> > >> >> > > For the shared component, I don't know if there is=
+ a
+> >=20
+> > best
+> >=20
+> > > > >>>> > >> candidate
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> > > 4. once previous step is ok, do the full migration:
+> > > > >>>> > >> >> > > if
+> > > > >>>>=20
+> > > > >>>> there are
+> > > > >>>>=20
+> > > > >>>> > >> >> > > volunteers
+> > > > >>>> > >> >> > > for helping, that would be great, since populating=
+ 60
+> >=20
+> > git
+> >=20
+> > > > >>>> repos
+> > > > >>>>=20
+> > > > >>>> > >> >> won't
+> > > > >>>> > >> >> be
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > really fun...
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > And as part of 60 empty git repos creation, I prop=
+ose
+> >=20
+> > to
+> >=20
+> > > > >>>> migrate
+> > > > >>>>=20
+> > > > >>>> > >> the
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> > > "Google
+> > > > >>>> > >> >> > > repo manifest" maven-aggregator [4] to ASF: my
+> >=20
+> > personal
+> >=20
+> > > > >>>> use has
+> > > > >>>>=20
+> > > > >>>> > >> been
+> > > > >>>> > >>=20
+> > > > >>>> > >> >> quite
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > successful, I hope it's the same for others. Perha=
+ps
+> > > > >>>>=20
+> > > > >>>> there are
+> > > > >>>>=20
+> > > > >>>> > >> >> better
+> > > > >>>> > >> >>=20
+> > > > >>>> > >> >> > > ideas
+> > > > >>>> > >> >> > > for its name: maven-aggregator
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > Any other idea? any objection?
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > Regards,
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > Herv=E9
+> > > > >>>> > >> >> > >=20
+> > > > >>>> > >> >> > > [1]
+> > > > >>>>=20
+> > > > >>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
+> > > > >>>>=20
+> > > > >>>> > >> >> > > [2]
+> > > > >>>>=20
+> > > > >>>> https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/
+> > > > >>>>=20
+> > > > >>>> > >> >> > > [3]
+> > > > >>>> > >>=20
+> > > > >>>> > >> https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/
+> >=20
+> > git/
+> >=20
+> > > > >>>> > >> >> > > [4] https://github.com/hboutemy/maven-aggregator
+> > > > >=20
+> > > > > ------------------------------------------------------------
+> >=20
+> > ---------
+> >=20
+> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > > >=20
+> > > > >=20
+> > > > > ------------------------------------------------------------
+> >=20
+> > ---------
+> >=20
+> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > >=20
+> > > > -------------------------------------------------------------------=
+=2D-
+> > > > 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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id DECBA200D17
+ for <ar...@cust-asf2.ponee.io>; Sun, 8 Oct 2017 19:28:11 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id DD56A1609E6; Sun, 8 Oct 2017 17:28:11 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 0673F1609D3
+ for <ar...@cust-asf.ponee.io>; Sun, 8 Oct 2017 19:28:10 +0200 (CEST)
+Received: (qmail 16055 invoked by uid 500); 8 Oct 2017 17:28:10 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 15999 invoked by uid 99); 8 Oct 2017 17:28:09 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Oct 2017 17:28:09 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0136018B4D9
+ for <de...@maven.apache.org>; Sun, 8 Oct 2017 17:28:09 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1.3
+X-Spam-Level:
+X-Spam-Status: No, score=-1.3 tagged_above=-999 required=6.31
+ tests=[KAM_LAZY_DOMAIN_SECURITY=1, KAM_NUMSUBJECT=0.5,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id pBHVut_s8vfa for <de...@maven.apache.org>;
+ Sun, 8 Oct 2017 17:28:05 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp13.smtpout.orange.fr [80.12.242.135])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 28ADA5FD1B
+ for <de...@maven.apache.org>; Sun, 8 Oct 2017 17:28:05 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d74 with ME
+ id K5U31w00E20Ufdy035U3W2; Sun, 08 Oct 2017 19:28:04 +0200
+X-ME-Helo: giga.localnet
+X-ME-Date: Sun, 08 Oct 2017 19:28:04 +0200
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: Jenkins and Maven 3.0.5 or JDK 7
+Date: Sun, 08 Oct 2017 19:28:03 +0200
+Message-ID: <10...@giga>
+User-Agent: KMail/5.2.3 (Linux/4.10.0-35-generic; KDE/5.31.0; x86_64; ; )
+In-Reply-To: <CA...@mail.gmail.com>
+References: <10...@giga> <30...@giga> <CA...@mail.gmail.com>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="UTF-8"
+archived-at: Sun, 08 Oct 2017 17:28:12 -0000
+
+I don't get the technical details
+but IIUC, you're able to do a PoC with our available git repositories of=20
+Jenkins job maintenance (easy job creation + easy Jenkinsfile maintenance),=
+ and=20
+you're confident that it can scale to the size we're expecting when we're=20
+splitting the current aggregator svn to many small git repos
+
+that's it?
+
+Regards,
+
+Herv=C3=A9
+
+Le dimanche 8 octobre 2017, 16:21:10 CEST Stephen Connolly a =C3=A9crit :
+> On Sun 8 Oct 2017 at 03:55, Herv=C3=A9 BOUTEMY <he...@free.fr> wr=
+ote:
+> > TLDR; =3D
+> > Perhaps we can start with 2 proofs of concept:
+> > 1. full git clone + Jenkins jobs for the 7 existing git repos (with 6
+> > additional ones in 2 days)
+> > 2. git split of one of the aggregator svn trunk: skins or doxia-tools c=
+an
+> > be
+> > easy choices since they are light, where plugins or shared are perhaps =
+too
+> > heavy. The one working on this PoC will make his choice
+> >=20
+> > then more detailed answer inline that lead to this PoCs proposal
+> >=20
+> > Regards,
+> >=20
+> > Herv=C3=A9
+> >=20
+> > Le dimanche 8 octobre 2017, 00:02:10 CEST Tibor Digana a =C3=A9crit :
+> > > I don't think the devs would work on all artifacts(projects) a time.
+> >=20
+> > sure, I think I'm one of the few people working on near everything (with
+> > rare
+> > exceptions like Surefire, as you noticed :) )
+> > but for usual contributor, there is no issue
+> >=20
+> > I'm not a git expert, then I don't know if easy "full Maven clone" is
+> > better
+> > done with a shell script or some git modules
+> >=20
+> > > If the naming convention of repo for a plugin would be artifactId, li=
+ke
+> > > /maven-clean-plugin, then even easy to figure out which one to clone.
+> > > The most likely the dev would just clone one repo she/he is interested
+> > > in
+> > > at the moment, i.e. repository /maven-clean-plugin, let's say.
+> > > It's good to avoid any shared files across them, even I don't think d=
+evs
+> > > share some in svn today. The release process would be quite usual, i.=
+e.
+> >=20
+> > one
+> >=20
+> > > repo =3D one project, and new devs already have these experiences whi=
+ch
+> >=20
+> > will
+> >=20
+> > > be simple for them to adapt faster.
+> >=20
+> > +1
+> > the only drawback I see currently is that there is no natural grouping,
+> > then
+> > we have a flat lit of near 100 git repos without the current structure
+> > (plugins, shared components, skins, ...): I think components structure =
+is
+> > useful for maintenability
+> > but not really a complete showstopper
+> > and perhaps the "Maven full clone" tooling can re-create some grouping =
+to
+> > keep
+> > visible structure
+> >=20
+> > Now, someone has to know how to create per-component git repo with tags
+> > (either by reworking exiting git mirrors, either by restarting from svn=
+),
+> > and
+> > that's not me :)
+> >=20
+> > given the volume (adding 70 git repos for Maven), we'll have to tell in=
+fra
+> > about it.
+> >=20
+> > Then there is the Jenkins jobs configuration:
+> > - we need easy Jenkinsfile in each repo
+>=20
+> so we create a shared Groovy library like the Jenkins project does and the
+> Jenkinsfile becomes `buildPlugin` for all except core
+>=20
+> > - we need easy 80 jobs creation (no, I won't manually create 80 jobs
+> > personally)
+>=20
+> So I will add SCMNavigator functionality to the ASF git-Jenkins plugin and
+> we just define an org-folder for Maven and all git repos with a Jenkinsfi=
+le
+> will be auto-maintained.
+>=20
+> > And once again, infra will have to be in the loop (at Jenkins side this
+> > time),
+> > since I fear the load on Jenkins master node won't be light: perhaps
+> > that's
+> > where Jenkins folders will be useful, but I'm not a Jenkins expert eith=
+er.
+>=20
+> If we use an org folder integrated with GitPubSub I do not think they will
+> be overly concerned
+>=20
+> > If everything seems feasible to split our svn code into 1 git repo per-
+> > component, which will bring us to "full Maven code" being near 100 repo=
+s,
+> > I'm
+> > ok with it.
+> > We'll need the help of misc experts on Jenkins and git to prepare things
+> > at
+> > this scale.
+>=20
+> I think one repo per release root is the way to go.
+>=20
+> We should start by drawing up a list and amalgamation where appropriate:
+>=20
+> Eg
+>=20
+> * does it make sense to release maven-deploy-plugin and
+> maven-install-plugin independently? Seems we most often make mirroring
+> changes to both, and perhaps it would be better if we forced that model?
+> (Don=E2=80=99t answer in this thread, just pointing out an example)
+>=20
+> > ---------------------------------------------------------------------
+> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > For additional commands, e-mail: dev-help@maven.apache.org
+> >=20
+> > --
+>=20
+> Sent from my phone
+
+
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id E165D200D26
+ for <ar...@cust-asf2.ponee.io>; Fri, 6 Oct 2017 07:32:29 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id DFDCB160BDA; Fri, 6 Oct 2017 05:32:29 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 304751609E2
+ for <ar...@cust-asf.ponee.io>; Fri, 6 Oct 2017 07:32:29 +0200 (CEST)
+Received: (qmail 53153 invoked by uid 500); 6 Oct 2017 05:32:28 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 53142 invoked by uid 99); 6 Oct 2017 05:32:27 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Oct 2017 05:32:27 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 00AD3180A46
+ for <de...@maven.apache.org>; Fri, 6 Oct 2017 05:32:27 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1.3
+X-Spam-Level:
+X-Spam-Status: No, score=-1.3 tagged_above=-999 required=6.31
+ tests=[KAM_LAZY_DOMAIN_SECURITY=1, KAM_NUMSUBJECT=0.5,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id Dv6juqI0NPsH for <de...@maven.apache.org>;
+ Fri, 6 Oct 2017 05:32:25 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp11.smtpout.orange.fr [80.12.242.133])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 68DB65FBEB
+ for <de...@maven.apache.org>; Fri, 6 Oct 2017 05:32:25 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d34 with ME
+ id J5YH1w00Q20Ufdy035YJZ4; Fri, 06 Oct 2017 07:32:18 +0200
+X-ME-Helo: giga.localnet
+X-ME-Date: Fri, 06 Oct 2017 07:32:18 +0200
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Jenkins and Maven 3.0.5 or JDK 7
+Date: Fri, 06 Oct 2017 07:32:17 +0200
+Message-ID: <10...@giga>
+User-Agent: KMail/5.2.3 (Linux/4.10.0-35-generic; KDE/5.31.0; x86_64; ; )
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Fri, 06 Oct 2017 05:32:30 -0000
+
+I just fixed a few failing jobs [1] to have again a usable Jenkins.
+
+Now I'm facing some issues, I suppose caused by newer Jenkins versions:
+=2D Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.MXParser=
+ [2]
+=2D I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes=20
+failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while th=
+e=20
+build JVM is Java 8)
+
+Should we drop Maven 3.0.5 builds and JDK 7?
+Notice I didn't check which is the minimum Maven version required...
+
+Or perhaps simply don't use the Jenkins Maven plugin with this Maven 3.0.5 =
+or=20
+JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 + lat=
+est=20
+Maven, and other configurations as scripted jobs?
+
+We need to define our common strategy and have a consistent configuration f=
+or =20
+every job understood by everybody
+
+Regards,
+
+Herv=E9
+
+[1] https://builds.apache.org/view/M-R/view/Maven/
+
+[2] https://builds.apache.org/view/M-R/view/Maven/job/maven-plugin-tools-jd=
+k-1.7/162/console
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 504F8200D3E
+ for <ar...@cust-asf2.ponee.io>; Thu, 16 Nov 2017 08:51:32 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 4EDEE160BE6; Thu, 16 Nov 2017 07:51:32 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 951AD160BE5
+ for <ar...@cust-asf.ponee.io>; Thu, 16 Nov 2017 08:51:31 +0100 (CET)
+Received: (qmail 47830 invoked by uid 500); 16 Nov 2017 07:51:25 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 47819 invoked by uid 99); 16 Nov 2017 07:51:25 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2017 07:51:25 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 4105B1A0CAC
+ for <de...@maven.apache.org>; Thu, 16 Nov 2017 07:51:24 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id 8FLBapodrXAY for <de...@maven.apache.org>;
+ Thu, 16 Nov 2017 07:51:22 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B875C5F299
+ for <de...@maven.apache.org>; Thu, 16 Nov 2017 07:51:21 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d53 with ME
+ id aXrD1w00A20Ufdy03XrDG9; Thu, 16 Nov 2017 08:51:13 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Thu, 16 Nov 2017 08:51:13 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: dev@maven.apache.org
+Subject: Re: Maven resolver branch consolidation
+Date: Thu, 16 Nov 2017 08:51:13 +0100
+Message-ID: <11...@giga>
+In-Reply-To: <79...@giga>
+References: <20...@dd17332.kasserver.com> <85...@apache.org> <79...@giga>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Thu, 16 Nov 2017 07:51:32 -0000
+
+I just pushed an update of dependencies image that shows the external maven-
+resolver-provider (in yellow) inside the reactor dependency graph (in blue)
+
+That shows the chicken and egg issue on releasing we'll have on API breakin=
+g=20
+change. People always building from source (like Debian) will have the issu=
+e=20
+also.
+
+=46or demos, which are not really published during the release (just as=20
+documentation), disabling the module in the build when necessary is suffici=
+ent,=20
+won't change many things. For ant tasks, disabling the module will not publ=
+ish=20
+the artifact: this will have a visible impact.
+
+Regards,
+
+Herv=E9
+
+Le mercredi 15 novembre 2017, 23:05:14 CET Herv=E9 BOUTEMY a =E9crit :
+> it seems I have not been clear: I'll try to explain better
+>=20
+> 1. maven-resolver-ant-tasks depends on maven-resolver-provider (from Maven
+> core)
+> 2. maven-resolver-provider (then Maven core) depends on maven-resolver
+>=20
+> if we put maven-resolver-ant-tasks in the same reactor than maven-resolve=
+r,
+> we can't release any maven-resolver API change that breaks maven-resolver-
+> provider
+>=20
+> example: if we move maven-resolver code to org.apache.maven java package =
+in
+> maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
+> 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new java
+> package. Then try to release anything: you can't, unless you don't try to
+> release maven- resolver-ant-tasks
+>=20
+> (the consequence on version consistency is another way to describe the
+> issue, but that is more subtle, then I chose to describe the most visible
+> issue, with API breaking change)
+>=20
+> IMHO, another consequence could be: maven-resolver-ant-tasks would perhaps
+> better be versionned like maven-resolver-provider
+>=20
+>=20
+> Merging resolver-demos is really the great big idea: with that merge,
+> modifying maven-rresolver can immediately be tested with demos: that'll be
+> so much easier to make changes to maven-resolver code!
+>=20
+> Regards,
+>=20
+> Herv=E9
+>=20
+> Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a =E9crit :
+> > Why -1 on the Ant tasks?
+> >=20
+> > Am 2017-11-15 um 00:50 schrieb Herv=E9 BOUTEMY:
+> > > I answered on the mailing list and on the 2 Jira issues
+> > > In summary, +1 to merge demos, -1 to merge ant-tasks
+> > >=20
+> > > Regards,
+> > >=20
+> > > Herv=E9
+> > >=20
+> > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a =E9crit :
+> > >> Any feedback or should I just go ahead with the cleanup?
+> > >>=20
+> > >> Manfred
+> > >>=20
+> > >> Manfred Moser wrote on 2017-11-08 21:35:
+> > >>> Hi all,
+> > >>>=20
+> > >>> I have started and made good progress on getting Maven resolver all
+> > >>> into
+> > >>> the master branch instead of having master, demos and ant-tasks in
+> > >>> separate branches.
+> > >>>=20
+> > >>> Details are tracked in
+> > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
+> > >>>=20
+> > >>> All of it is now in a new branch called master-all for you to see.
+> > >>>=20
+> > >>> I am now wondering what the next steps are. I added what I think
+> > >>> should
+> > >>> happen next in the issue in a comment and would appreciate any input
+> > >>> on
+> > >>> the current setup and next steps.
+> > >>>=20
+> > >>> Any help would be appreciated.
+> > >>>=20
+> > >>> manfred
+> > >>=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 1C3E9200D31
+ for <ar...@cust-asf2.ponee.io>; Sat, 4 Nov 2017 14:56:18 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 1ACB0160BE7; Sat, 4 Nov 2017 13:56:18 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 60C1B160BD5
+ for <ar...@cust-asf.ponee.io>; Sat, 4 Nov 2017 14:56:17 +0100 (CET)
+Received: (qmail 36040 invoked by uid 500); 4 Nov 2017 13:56:16 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 36020 invoked by uid 99); 4 Nov 2017 13:56:16 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Nov 2017 13:56:16 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 60B9A1808C8
+ for <de...@maven.apache.org>; Sat, 4 Nov 2017 13:56:15 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id BWyxW5HiPSD5 for <de...@maven.apache.org>;
+ Sat, 4 Nov 2017 13:56:13 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 238F360F6C
+ for <de...@maven.apache.org>; Sat, 4 Nov 2017 13:56:13 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d42 with ME
+ id VpwC1w00720Ufdy03pwCpv; Sat, 04 Nov 2017 14:56:12 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Sat, 04 Nov 2017 14:56:12 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: migrating some code to Git
+Date: Sat, 04 Nov 2017 14:56:12 +0100
+Message-ID: <11...@giga>
+In-Reply-To: <51...@giga>
+References: <58...@giga> <36...@giga> <51...@giga>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Sat, 04 Nov 2017 13:56:18 -0000
+
+migration done [1]
+we now have 22 git repos (maven-resolver has 3 independant branches...)
+
+I'm waiting for feedback before creating maven-aggregator @ ASF (for Google=
+=20
+repo manifest)
+
+next big migrations will be shared and plugins once Stephen videos and=20
+solution on scaling Jenkins for our organization will be ready
+
+There a few cases to discuss:
+=2D Apache Resource Bundles: should IMHO be merged into one unique release:=
+ any=20
+taker?
+=2D Archetypes: split (wait for Jenkins) or not split (and do now)?
+=2D Maven and Doxia sites: need to see if CMS can checkout from Git, or eve=
+n if=20
+we should not use CMS any more to build but use Jenkins...
+
+Regards,
+
+Herv=E9
+
+[1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
+
+Le samedi 4 novembre 2017, 09:50:28 CET Herv=E9 BOUTEMY a =E9crit :
+> no objection: starting the migration of these 6 repos
+>=20
+> Regards,
+>=20
+> Herv=E9
+>=20
+> Le mercredi 1 novembre 2017, 12:09:58 CET Herv=E9 BOUTEMY a =E9crit :
+> > adding 2 more repos to the list:
+> > https://github.com/hboutemy/maven-doxia-converter
+> > https://github.com/hboutemy/maven-doxia-linkcheck
+> >=20
+> > Le mercredi 1 novembre 2017, 07:28:02 CET Herv=E9 BOUTEMY a =E9crit :
+> > > for lazy people, I took time to create the 4 repo on personal GitHub
+> > > space:
+> > > https://github.com/hboutemy/maven-apache-parent
+> > > https://github.com/hboutemy/maven-parent
+> > > https://github.com/hboutemy/maven-default-skin
+> > > https://github.com/hboutemy/maven-fluido-skin
+> > >=20
+> > > I won't do the same in the future for the 26 shared and 45 plugins,
+> > > since
+> > > manual repo creation is not fun...
+> > >=20
+> > > Regards,
+> > >=20
+> > > Herv=E9
+> > >=20
+> > > Le mardi 31 octobre 2017, 16:08:01 CET Herv=E9 BOUTEMY a =E9crit :
+> > > > As you probably noticed, I migrated maven-dist-tool [1] to git, usi=
+ng
+> > > > self-
+> > > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
+> > > > shell
+> > > > script [2] to populate them (after Sling example)
+> > > >=20
+> > > > It worked like a charm!
+> > > >=20
+> > > > If nobody objects, in 72h, I'll use migrate-pom.sh and
+> > > > migrate-skins.sh
+> > > > to
+> > > > create 4 new repos: maven-apache-parent, maven-parent,
+> > > > maven-default-skin
+> > > > and maven-fluido-skin
+> > > > Please take time to execute the scripts for yourself and check that
+> > > > the
+> > > > result is ok for you.
+> > > >=20
+> > > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts:
+> > > > I'm
+> > > > waiting for Jenkins integration results before trying to migrate th=
+is
+> > > > part,
+> > > > but you can also take time to check that the resulting git repos fr=
+om
+> > > > the
+> > > > scripts are good.
+> > > >=20
+> > > > Regards,
+> > > >=20
+> > > > Herv=E9
+> > > >=20
+> > > > [1] https://github.com/apache/maven-dist-tool/
+> > > >=20
+> > > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
+> > > >=20
+> > > > -------------------------------------------------------------------=
+=2D-
+> > > > 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
+>=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 5F85F200D5C
+ for <ar...@cust-asf2.ponee.io>; Fri, 15 Dec 2017 07:34:30 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 5DF1A160C14; Fri, 15 Dec 2017 06:34:30 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 7C668160C06
+ for <ar...@cust-asf.ponee.io>; Fri, 15 Dec 2017 07:34:29 +0100 (CET)
+Received: (qmail 43313 invoked by uid 500); 15 Dec 2017 06:34:28 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 43302 invoked by uid 99); 15 Dec 2017 06:34:27 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2017 06:34:27 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 760C4180A2E
+ for <de...@maven.apache.org>; Fri, 15 Dec 2017 06:34:27 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id mICLSdZOdXlS for <de...@maven.apache.org>;
+ Fri, 15 Dec 2017 06:34:25 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6575F5F366
+ for <de...@maven.apache.org>; Fri, 15 Dec 2017 06:34:24 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d54 with ME
+ id m6aJ1w00120Ufdy036aJkM; Fri, 15 Dec 2017 07:34:18 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Fri, 15 Dec 2017 07:34:18 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: Git migration next steps
+Date: Fri, 15 Dec 2017 07:34:17 +0100
+Message-ID: <11...@giga>
+In-Reply-To: <15...@giga>
+References: <19...@giga> <CA...@mail.gmail.com> <15...@giga>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Fri, 15 Dec 2017 06:34:30 -0000
+
+another strange thing [1]
+=2D what are the many "Open tasks"?
+=2D why are changes written 5 times?
+
+Regards
+
+Herv=E9
+
+[1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-s=
+ite-plugin/job/master/changes
+
+Le mercredi 13 d=E9cembre 2017, 05:58:28 CET Herv=E9 BOUTEMY a =E9crit :
+> thank you: one less issue
+>=20
+> a new finding: the Jira message points to the Jenkins build, why not
+> But it does not point to Git commit [1]
+>=20
+> the link to the git commit is very useful to track how the fix was done, =
+and
+> remains valid on a long period (which is not the case of the Jenkins buil=
+d)
+>=20
+> Is it possible to have this in our standard build, please?
+>=20
+> Regards,
+>=20
+> Herv=E9
+>=20
+> [1] https://issues.apache.org/jira/browse/DOXIASITETOOLS-182
+>=20
+> Le lundi 11 d=E9cembre 2017, 21:29:15 CET Stephen Connolly a =E9crit :
+> > On Sun 10 Dec 2017 at 09:59, Herv=E9 BOUTEMY <he...@free.fr> wr=
+ote:
+> > > here is a list of strange issues in CI jobs:
+> > >=20
+> > > - Doxia Sitetools is failing at checkout [1]
+> > >=20
+> > > - Maven core branches fail in maven-wip [2] while the multi-branch do=
+es
+> > > not
+> > > fail [3]: AFAIK, same Jenkins files are used, isn't it?
+> >=20
+> > Ubuntu-4 was having issues
+> >=20
+> > > Regards,
+> > >=20
+> > > Herv=E9
+> > >=20
+> > > [1]
+> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven=
+=2Ddo
+> > > xi
+> > > a-sitetools/job/master/4/console
+> > >=20
+> > > [2]
+> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/
+> > >=20
+> > > [3]
+> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfi=
+le/
+> > >=20
+> > > Le dimanche 10 d=E9cembre 2017, 06:29:20 CET Herv=E9 BOUTEMY a =E9cri=
+t :
+> > > > yes, and 83 maven-box CI jobs [1]
+> > > >=20
+> > > > some CI failures are not really expected, but in general, the result
+> > > > is
+> > >=20
+> > > good
+> > >=20
+> > > > it's time for everybody to check his favorite plugin or shared
+> > > > component
+> > >=20
+> > > and
+> > >=20
+> > > > do the little fixes: the global migration is done
+> > > >=20
+> > > > and it's time also to start reviewing PRs and merging: this was the
+> > > > big
+> > > > objective with Git migration
+> > > >=20
+> > > > Regards,
+> > > >=20
+> > > > Herv=E9
+> > > >=20
+> > > > [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
+> > > >=20
+> > > > Le samedi 9 d=E9cembre 2017, 17:06:09 CET Stephen Connolly a =E9cri=
+t :
+> > > > > I see we have a large number of repos now on gitbox ;-)
+> > > > >=20
+> > > > > On Thu 7 Dec 2017 at 07:00, Herv=E9 BOUTEMY <herve.boutemy@free.f=
+r>
+> > >=20
+> > > wrote:
+> > > > > > ok, I didn't update my repo clone: now the run-its profile is
+> > >=20
+> > > activated
+> > >=20
+> > > > > > then the plan should just confirm "it works!" :)
+> > > > > >=20
+> > > > > > and find which jobs are special, like maven-dist-tool (which has
+> > > > > > to
+> > >=20
+> > > be
+> > >=20
+> > > > > > scheduled daily instead of code change, and one platform only)
+> > > > > >=20
+> > > > > > Regards,
+> > > > > >=20
+> > > > > > Herv=E9
+> > > > > >=20
+> > > > > > Le mercredi 6 d=E9cembre 2017, 23:58:45 CET Stephen Connolly a =
+=E9crit=20
+:
+> > > > > > > On Wed 6 Dec 2017 at 22:38, Herv=E9 BOUTEMY
+> > > > > > > <he...@free.fr>
+> > >=20
+> > > wrote:
+> > > > > > > > Now that we have 2 ASF Organization Jenkins jobs (one for
+> > > > > > > > gitbox
+> > >=20
+> > > [1]
+> > >=20
+> > > > > > and
+> > > > > >=20
+> > > > > > > > one
+> > > > > > > > for git-wip: thank you Stephen) and that it looks quite
+> > >=20
+> > > successful,
+> > >=20
+> > > > > > let's
+> > > > > >=20
+> > > > > > > > plan
+> > > > > > > > the next steps.
+> > > > > > > >=20
+> > > > > > > > Here is what I see:
+> > > > > > > > 1. removal of hand-defined Jenkins jobs that are now
+> > > > > > > > duplicates
+> > > > > > > >=20
+> > > > > > > > 2. preparation of the 60 new empty git repos for shared &
+> > > > > > > > plugins
+> > > > > > > >=20
+> > > > > > > > 3. migration of the 1 shared component and 1 plugin using
+> > > > > > > > migrate-*.sh
+> > > > > > > > scripts
+> > > > > > > > [3] to test and eventually rework the Jenkinsfile (I suppose
+> > > > > > > > it
+> > >=20
+> > > will
+> > >=20
+> > > > > > > > require
+> > > > > > > > some little change, to run add "run-its" profile)
+> > > > > > >=20
+> > > > > > > As far as I recall, I added -P+run-its already
+> > > > > > >=20
+> > > > > > > For the plugin, I'd like to do the job for maven-site-plugin,
+> > >=20
+> > > since we
+> > >=20
+> > > > > > > > expect
+> > > > > > > > to release it soon.
+> > > > > > > > For the shared component, I don't know if there is a best
+> > >=20
+> > > candidate
+> > >=20
+> > > > > > > > 4. once previous step is ok, do the full migration: if there
+> > > > > > > > are
+> > > > > > > > volunteers
+> > > > > > > > for helping, that would be great, since populating 60 git
+> > > > > > > > repos
+> > > > > > > > won't
+> > > > > >=20
+> > > > > > be
+> > > > > >=20
+> > > > > > > > really fun...
+> > > > > > > >=20
+> > > > > > > > And as part of 60 empty git repos creation, I propose to
+> > > > > > > > migrate
+> > >=20
+> > > the
+> > >=20
+> > > > > > > > "Google
+> > > > > > > > repo manifest" maven-aggregator [4] to ASF: my personal use
+> > > > > > > > has
+> > >=20
+> > > been
+> > >=20
+> > > > > > quite
+> > > > > >=20
+> > > > > > > > successful, I hope it's the same for others. Perhaps there =
+are
+> > > > > > > > better
+> > > > > > > > ideas
+> > > > > > > > for its name: maven-aggregator
+> > > > > > > >=20
+> > > > > > > > Any other idea? any objection?
+> > > > > > > >=20
+> > > > > > > > Regards,
+> > > > > > > >=20
+> > > > > > > > Herv=E9
+> > > > > > > >=20
+> > > > > > > > [1]
+> > > > > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
+> > > > > > > >=20
+> > > > > > > > [2]
+> > > > > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/
+> > > > > > > >=20
+> > > > > > > > [3]
+> > >=20
+> > > https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
+> > >=20
+> > > > > > > > [4] https://github.com/hboutemy/maven-aggregator
+> > >=20
+> > > --------------------------------------------------------------------
+> > >=20
+> > > > > > > > -
+> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > > > > > >=20
+> > > > > > > > --
+> > > > > > >=20
+> > > > > > > Sent from my phone
+> > > > > >=20
+> > > > > > ---------------------------------------------------------------=
+=2D--
+> > > > > > --
+> > > > > > -
+> > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > > > >=20
+> > > > > > --
+> > > > >=20
+> > > > > Sent from my phone
+> > > >=20
+> > > > -------------------------------------------------------------------=
+=2D-
+> > > > 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
+> > > --
+> >=20
+> > Sent from my phone
+>=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 5E0A4200D0E
+ for <ar...@cust-asf2.ponee.io>; Tue, 12 Sep 2017 00:58:17 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 5CD5F1609C5; Mon, 11 Sep 2017 22:58:17 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id A17681609C4
+ for <ar...@cust-asf.ponee.io>; Tue, 12 Sep 2017 00:58:16 +0200 (CEST)
+Received: (qmail 283 invoked by uid 500); 11 Sep 2017 22:58:15 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 267 invoked by uid 99); 11 Sep 2017 22:58:15 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Sep 2017 22:58:15 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 032E6183CA8
+ for <de...@maven.apache.org>; Mon, 11 Sep 2017 22:58:15 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.8
+X-Spam-Level:
+X-Spam-Status: No, score=-0.8 tagged_above=-999 required=6.31
+ tests=[KAM_LAZY_DOMAIN_SECURITY=1, KAM_NUMSUBJECT=0.5,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8,
+ RCVD_IN_SORBS_SPAM=0.5] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id tdRixvTqaKmm for <de...@maven.apache.org>;
+ Mon, 11 Sep 2017 22:58:13 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp09.smtpout.orange.fr [80.12.242.131])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9DFAB5FC12
+ for <de...@maven.apache.org>; Mon, 11 Sep 2017 22:58:13 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d69 with ME
+ id 8Ny71w00P20Ufdy03Ny7Qw; Tue, 12 Sep 2017 00:58:07 +0200
+X-ME-Helo: giga.localnet
+X-ME-Date: Tue, 12 Sep 2017 00:58:07 +0200
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.2
+Date: Tue, 12 Sep 2017 00:58:07 +0200
+Message-ID: <11...@giga>
+User-Agent: KMail/5.2.3 (Linux/4.10.0-33-generic; KDE/5.31.0; x86_64; ; )
+In-Reply-To: <78...@gmx.de>
+References: <78...@gmx.de>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Mon, 11 Sep 2017 22:58:17 -0000
+
++1
+
+Regards,
+
+Herv=E9
+
+Le samedi 9 septembre 2017, 14:34:49 CEST Karl Heinz Marbaise a =E9crit :
+> Hi,
+>=20
+> We solved 7 issues:
+> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D123172=
+27&ve
+> rsion=3D12341254
+>=20
+> There are still a couple of issues left in JIRA:
+> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20MDEP%20AND%2=
+0reso
+> lution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%=
+2C%
+> 20updated%20DESC
+>=20
+> Staging repo:
+> https://repository.apache.org/content/repositories/maven-1360
+> https://repository.apache.org/content/repositories/maven-1360/org/apache/=
+mav
+> en/plugins/maven-dependency-plugin/3.0.2/maven-dependency-plugin-3.0.2-so=
+urc
+> e-release.zip
+>=20
+> Source release checksum(s):
+> maven-dependency-plugin-3.0.2-source-release.zip sha1:
+> 3c4aa716e28b241834d47d22e1ff5f6e62f16b9b
+>=20
+> Staging site:
+> https://maven.apache.org/plugins-archives/maven-dependency-plugin-LATEST/
+>=20
+> Guide to testing staged releases:
+> https://maven.apache.org/guides/development/guide-testing-releases.html
+>=20
+> Vote open for at least 72 hours.
+>=20
+> [ ] +1
+> [ ] +0
+> [ ] -1
+>=20
+> Kind regards
+> Karl Heinz Marbaise
+>=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 56F1C200D5F
+ for <ar...@cust-asf2.ponee.io>; Mon, 18 Dec 2017 08:42:39 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 555F9160C05; Mon, 18 Dec 2017 07:42:39 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 9AA01160BF9
+ for <ar...@cust-asf.ponee.io>; Mon, 18 Dec 2017 08:42:38 +0100 (CET)
+Received: (qmail 12441 invoked by uid 500); 18 Dec 2017 07:42:37 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 12430 invoked by uid 99); 18 Dec 2017 07:42:37 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Dec 2017 07:42:37 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BAC741A0A9A
+ for <de...@maven.apache.org>; Mon, 18 Dec 2017 07:42:36 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1.8
+X-Spam-Level:
+X-Spam-Status: No, score=-1.8 tagged_above=-999 required=6.31
+ tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001,
+ RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id LIQHBnVwqxFM for <de...@maven.apache.org>;
+ Mon, 18 Dec 2017 07:42:35 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp10.smtpout.orange.fr [80.12.242.132])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 41BD55F297
+ for <de...@maven.apache.org>; Mon, 18 Dec 2017 07:42:35 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d20 with ME
+ id nKiU1w00T20Ufdy03KiUaJ; Mon, 18 Dec 2017 08:42:28 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Mon, 18 Dec 2017 08:42:28 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: [FEEDBACK WANTED] edit button on a Maven site
+Date: Mon, 18 Dec 2017 08:42:28 +0100
+Message-ID: <11...@giga>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Mon, 18 Dec 2017 07:42:39 -0000
+
+Hi,
+
+I just managed to add an "edit" button in Maven generated sites, that will=
+=20
+help people find the source of the document.
+
+See an example here (the little icon near the version):
+http://maven.apache.org/skins-archives/maven-fluido-skin-LATEST/
+
+I wanted to publish it to Maven site through http://svn.apache.org/r1818489=
+=20
+but buildbot did not catch the SNAPSHOT m-site-p plugin: we'll have to wait=
+=20
+for the release (after Doxia then Doxia Sitetools releases: please vote).
+
+=46eedback appreciated on the new icon, its configuration, or any idea that=
+ could=20
+improve the feature.
+Don't hesitate to propose improvements as html changes: we'll see later how=
+ to=20
+get the update in the Velocity template that generated the html...
+
+Regards,
+
+Herv=E9
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 0B42A200D59
+ for <ar...@cust-asf2.ponee.io>; Sun, 10 Dec 2017 17:46:23 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 09ACD160C09; Sun, 10 Dec 2017 16:46:23 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 4E985160BF2
+ for <ar...@cust-asf.ponee.io>; Sun, 10 Dec 2017 17:46:22 +0100 (CET)
+Received: (qmail 97520 invoked by uid 500); 10 Dec 2017 16:46:21 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 97508 invoked by uid 99); 10 Dec 2017 16:46:21 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Dec 2017 16:46:21 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AB39FC3120
+ for <de...@maven.apache.org>; Sun, 10 Dec 2017 16:46:20 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 1.799
+X-Spam-Level: *
+X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001]
+ autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id Yv7RS4uyaXD1 for <de...@maven.apache.org>;
+ Sun, 10 Dec 2017 16:46:19 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B236E5F251
+ for <de...@maven.apache.org>; Sun, 10 Dec 2017 16:46:18 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d36 with ME
+ id kGmA1w00V20Ufdy03GmAkg; Sun, 10 Dec 2017 17:46:10 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Sun, 10 Dec 2017 17:46:10 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: merging MNG-6308 display packaging
+Date: Sun, 10 Dec 2017 17:46:10 +0100
+Message-ID: <12...@giga>
+In-Reply-To: <op...@desktop-2khsk44.mshome.net>
+References: <27...@giga> <op...@desktop-2khsk44.mshome.net>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Sun, 10 Dec 2017 16:46:23 -0000
+
+Le dimanche 10 d=E9cembre 2017, 11:06:32 CET Robert Scholte a =E9crit :
+> I still think it is ugly to use the HR for this kind of info.
+> If you *really* want this info, I'd prefer a new line, offering more space
+> for additional info.
+yes, I *really* want this info: the precise details on how to display it is=
+=20
+less important
+
+> Other option is to leave it as it is. If developers want it, they can put
+> it in the name.
+the idea is that ${project.packaging} drives the default build, before=20
+additional plugins bindings: it's useful to display it as it is a key info
+
+>=20
+> So -1 for me.
+how do you want to proceed to choose the best display?
+
+Regards,
+
+Herv=E9
+
+>=20
+> Robert
+>=20
+>=20
+> On Sun, 10 Dec 2017 11:01:41 +0100, Herv=E9 BOUTEMY <herve.boutemy@free.f=
+r>
+>=20
+> wrote:
+> > is there a seconder for this enhancement?
+> >=20
+> > CI:
+> > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
+> > job/MNG-6308_display_packaging/
+> >=20
+> > Jira issue: https://issues.apache.org/jira/browse/MNG-6308
+> >=20
+> > Regards,
+> >=20
+> > Herv=E9
+> >=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 5DA8F200D4B
+ for <ar...@cust-asf2.ponee.io>; Mon, 13 Nov 2017 05:08:30 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 5C298160C05; Mon, 13 Nov 2017 04:08:30 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 7A0D8160BF1
+ for <ar...@cust-asf.ponee.io>; Mon, 13 Nov 2017 05:08:29 +0100 (CET)
+Received: (qmail 99657 invoked by uid 500); 13 Nov 2017 04:08:28 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 99645 invoked by uid 99); 13 Nov 2017 04:08:27 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2017 04:08:27 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 203021A2BFE
+ for <de...@maven.apache.org>; Mon, 13 Nov 2017 04:08:27 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 2.98
+X-Spam-Level: **
+X-Spam-Status: No, score=2.98 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2,
+ KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
+ RCVD_IN_SORBS_SPAM=0.5] autolearn=disabled
+Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=talios-com.20150623.gappssmtp.com
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id 1ZGonNUC1UdU for <de...@maven.apache.org>;
+ Mon, 13 Nov 2017 04:08:26 +0000 (UTC)
+Received: from mail-pg0-f45.google.com (mail-pg0-f45.google.com [74.125.83.45])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9D7E95FE0E
+ for <de...@maven.apache.org>; Mon, 13 Nov 2017 04:08:25 +0000 (UTC)
+Received: by mail-pg0-f45.google.com with SMTP id z184so6396937pgd.13
+ for <de...@maven.apache.org>; Sun, 12 Nov 2017 20:08:25 -0800 (PST)
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=talios-com.20150623.gappssmtp.com; s=20150623;
+ h=from:to:subject:date:message-id:in-reply-to:references:mime-version;
+ bh=pYGS5EEGl48K2Gh3RMJad/IN8kxEpBDOBncMH4H20ok=;
+ b=G1SkE4+WtBS6U/S76l59c4/TVgfdkABDIb8guOVENMzM2nd3p+YlRQP5ZVc+uxmSyx
+ 0op++bpCWE4PFrUDOtRSlQGCXEQXDZgOLnQMYelyi6LfOOYRY1iwf6kz3tHDW89KI7mC
+ yyzHErngIGyGCch/WZEvvwgZlbMRi+6LnjUrA1LLhkuyXQjPVsOXtLlNWd8Qp+fSN7y7
+ 2jBzh4yooU+96vzP3ZibXnIHhXd5OkJR6WVQjpRyb54V8RUvsYIIaB7eQQkuTY3ysYeY
+ jobMnr2X9XtNfDzuqZMlHw+vrWh++IlBW8eyCD0NFZyp0T6i0j/pQnqQJ0heBqmlox1p
+ EVJw==
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=1e100.net; s=20161025;
+ h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to
+ :references:mime-version;
+ bh=pYGS5EEGl48K2Gh3RMJad/IN8kxEpBDOBncMH4H20ok=;
+ b=VAXDXsLALcGbJzx+mPkkGa1ZtRX76BTdz0e768UvOwUBwWH3iGLW0bM6G0Ke5MCh4N
+ Zhy8SQfuaJcW4iTyf0wlgGmwtpUXkr0HBeouESen7CLhreMBzBLLYPoi71Mb83Zs0raZ
+ 7Ab/kajGt2bi+0yMdXZSDqWiDhlyjuc03/+j1vVPEYVZohXIgJJUNFusxurKOWQY5KP2
+ UzHTDQ1K1D4vmh15BPOxRyZwpJybsUdzkDaXLnYoOBm3au6TiqkRTlvKF+jJQzGmKuaA
+ Xwc8elMBT2FcKAWhhu+CUTxvAquq5+us3ETOJF6IJTn7CCrVjeZAqV+EWAWqVtpe1VuI
+ ZHrw==
+X-Gm-Message-State: AJaThX5ZtMI/bi93z40rV9MlCthtAZ8kRih3bwG+f8sw6dT4zvyw7pB8
+ hjL4vwTTVSfaxwqMBRIcrmJStRwU08k=
+X-Google-Smtp-Source: AGs4zMaM4EynNF7mXdZQL8syFqDJaFxEHwJJX7AyWdvY3WvBSd80Q6bnrhB9wd2Q30tSV51+xavj0w==
+X-Received: by 10.159.230.13 with SMTP id u13mr7664115plq.226.1510546098096;
+ Sun, 12 Nov 2017 20:08:18 -0800 (PST)
+Received: from [10.0.202.87] ([113.197.65.22])
+ by smtp.gmail.com with ESMTPSA id v76sm29309861pfk.78.2017.11.12.20.08.16
+ for <de...@maven.apache.org>
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
+ Sun, 12 Nov 2017 20:08:17 -0800 (PST)
+From: "Mark Derricutt" <ma...@talios.com>
+To: "Maven Developers List" <de...@maven.apache.org>
+Subject: Re: Maven 4.0.0
+Date: Mon, 13 Nov 2017 17:08:13 +1300
+Message-ID: <12...@talios.com>
+In-Reply-To: <CA...@mail.gmail.com>
+References: <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+MIME-Version: 1.0
+Content-Type: multipart/signed;
+ boundary="=_MailMate_53A42549-AEA3-4C79-B51D-A4011F73C6A7_=";
+ micalg=pgp-sha1; protocol="application/pgp-signature"
+X-Mailer: MailMate (2.0BETAr6093)
+archived-at: Mon, 13 Nov 2017 04:08:30 -0000
+
+--=_MailMate_53A42549-AEA3-4C79-B51D-A4011F73C6A7_=
+Content-Type: multipart/alternative;
+ boundary="=_MailMate_712C9268-C9DD-480D-A1AF-C674F0B3420B_="
+
+
+--=_MailMate_712C9268-C9DD-480D-A1AF-C674F0B3420B_=
+Content-Type: text/plain; markup=markdown
+Content-Transfer-Encoding: quoted-printable
+
+On 12 Nov 2017, at 23:06, Stephen Connolly wrote:
+
+> That could end up duplicating the local repo cache... unless we default=
+ the
+> cache to ~/.m2/repository anyway... otoh a concurrency safe local repo
+> cache may mandate a new location... but double the downloads for inter-=
+op
+> with older Maven installs on the same machine seems not so good to me.
+
+If we're talking restructuring the local repo, I've long wanting to separ=
+ate out locally "mvn install"'d items from those downloaded, essentially =
+this would keep ( for the most part ) local SNAPSHOTs separate from anyth=
+ing downloaded.
+
+I guess what I really want there is a local releases/snaphshots repo sepa=
+ration, often it's handy to just blow away all snapshots and rebuild into=
+ a known state. It does make for more complexity tho.
+
+
+
+---
+"The ease with which a change can be implemented has no relevance at all =
+to whether it is the right change for the (Java) Platform for all time." =
+— Mark Reinhold.
+
+Mark Derricutt
+http://www.theoryinpractice.net
+http://www.chaliceofblood.net
+http://plus.google.com/+MarkDerricutt
+http://twitter.com/talios
+http://facebook.com/mderricutt
+
+--=_MailMate_712C9268-C9DD-480D-A1AF-C674F0B3420B_=
+Content-Type: text/html; charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
+>
+</head>
+<body>
+<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
+<p dir=3D"auto">On 12 Nov 2017, at 23:06, Stephen Connolly wrote:</p>
+
+<blockquote style=3D"border-left:2px solid #5855D5; color:#5855D5; margin=
+:0 0 5px; padding-left:5px">
+<p dir=3D"auto">That could end up duplicating the local repo cache... unl=
+ess we default the<br>
+cache to ~/.m2/repository anyway... otoh a concurrency safe local repo<br=
+>
+cache may mandate a new location... but double the downloads for inter-op=
+<br>
+with older Maven installs on the same machine seems not so good to me.</p=
+>
+</blockquote>
+
+<p dir=3D"auto">If we're talking restructuring the local repo, I've long =
+wanting to separate out locally "mvn install"'d items from those download=
+ed, essentially this would keep ( for the most part ) local SNAPSHOTs sep=
+arate from anything downloaded.</p>
+
+<p dir=3D"auto">I guess what I really want there is a local releases/snap=
+hshots repo separation, often it's handy to just blow away all snapshots =
+and rebuild into a known state. It does make for more complexity tho.</p=
+>
+
+<hr>
+
+<p dir=3D"auto">"The ease with which a change can be implemented has no r=
+elevance at all to whether it is the right change for the (Java) Platform=
+ for all time." =E2=80=94 Mark Reinhold.</p>
+
+<p dir=3D"auto">Mark Derricutt<br>
+<a href=3D"http://www.theoryinpractice.net">http://www.theoryinpractice.n=
+et</a><br>
+<a href=3D"http://www.chaliceofblood.net">http://www.chaliceofblood.net</=
+a><br>
+<a href=3D"http://plus.google.com/+MarkDerricutt">http://plus.google.com/=
++MarkDerricutt</a><br>
+<a href=3D"http://twitter.com/talios">http://twitter.com/talios</a><br>
+<a href=3D"http://facebook.com/mderricutt">http://facebook.com/mderricutt=
+</a></p>
+</div>
+</div>
+</body>
+</html>
+
+--=_MailMate_712C9268-C9DD-480D-A1AF-C674F0B3420B_=--
+
+--=_MailMate_53A42549-AEA3-4C79-B51D-A4011F73C6A7_=
+Content-Description: OpenPGP digital signature
+Content-Disposition: attachment; filename=signature.asc
+Content-Type: application/pgp-signature; name=signature.asc
+
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG/MacGPG2 v2
+
+iQFEBAEBAgAuFiEELdSKGMT2tCFlhLxk6NqDZHNO0kUFAloJGq0QHG1hcmtAdGFs
+aW9zLmNvbQAKCRDo2oNkc07SRf7DCACSUAZLOdIS0yA8Nb0pHNmxKUq4HGiLK6kc
+4p+5EQCA7KyLqCvUbUjBhaEX3tvvG0LX4ILfDZ1yTl6P4J/EEWpbFXSCuJW5OfRE
+zNF4W4WX1JtNCpoelVTXgMoGsknIFLhIRfLGNfk0hfsicnZR2YMYb6cXNLqG140t
+AkE2X6ZOIlAvqtLVwBuCTbcX28Ou5Qtws0mrvTWCfp1HXU0nfe4fSDvAqLKK1yBG
+Dx9Y/i310y+eE4iB9ujHNQgXUVMPVgdLfK2AtOm3lNfjP6u7BjjYKyvc7g4srEPC
+JwzTamCjYo3PQqEn6X7LtQbmicjaGeyc9nVL0f2SSnPTNeKqa426
+=Y7dx
+-----END PGP SIGNATURE-----
+
+--=_MailMate_53A42549-AEA3-4C79-B51D-A4011F73C6A7_=--
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 576EC200D6B
+ for <ar...@cust-asf2.ponee.io>; Sun, 31 Dec 2017 16:29:14 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 55D6F160C24; Sun, 31 Dec 2017 15:29:14 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 9C9F8160C09
+ for <ar...@cust-asf.ponee.io>; Sun, 31 Dec 2017 16:29:13 +0100 (CET)
+Received: (qmail 29410 invoked by uid 500); 31 Dec 2017 15:29:12 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 29399 invoked by uid 99); 31 Dec 2017 15:29:12 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Dec 2017 15:29:12 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CE6F31805E0
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 15:29:11 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1.3
+X-Spam-Level:
+X-Spam-Status: No, score=-1.3 tagged_above=-999 required=6.31
+ tests=[KAM_LAZY_DOMAIN_SECURITY=1, KAM_NUMSUBJECT=0.5,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id X-uGDivsfJdK for <de...@maven.apache.org>;
+ Sun, 31 Dec 2017 15:29:10 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id D2CA95FB9E
+ for <de...@maven.apache.org>; Sun, 31 Dec 2017 15:29:09 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d66 with ME
+ id sfV81w00Z20Ufdy03fV820; Sun, 31 Dec 2017 16:29:09 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Sun, 31 Dec 2017 16:29:09 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: [VOTE] Release Apache Maven Site Plugin version 3.7
+Date: Sun, 31 Dec 2017 16:29:08 +0100
+Message-ID: <13...@giga>
+In-Reply-To: <20...@apache.org>
+References: <25...@giga> <20...@apache.org>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Sun, 31 Dec 2017 15:29:14 -0000
+
+Le dimanche 31 d=E9cembre 2017, 13:37:29 CET Michael Osipov a =E9crit :
+> Am 2017-12-28 um 17:20 schrieb Herv=E9 BOUTEMY:
+> > Hi,
+> >=20
+> > We solved 8 issues:
+> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
+> > projectId=3D12317923&version=3D12338726&styleName=3DText
+> >=20
+> > There are still a couple of issues left in JIRA:
+> > https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20MSITE%20AND
+> > %20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
+> >=20
+> > Staging repo:
+> > https://repository.apache.org/content/repositories/maven-1386/
+> > https://repository.apache.org/content/repositories/maven-1386/org/apach=
+e/
+> > maven/plugins/maven-site-plugin/3.7/maven-site-plugin-3.7-source-releas=
+e.z
+> > ip
+> >=20
+> > Source release checksum(s):
+> > maven-site-plugin-3.7-source-release.zip sha1:
+> > 9fa4b28053f4cb79a08863568a66c1e87d8bbc93
+> >=20
+> > Staging site:
+> > https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/
+> >=20
+> > Guide to testing staged releases:
+> > https://maven.apache.org/guides/development/guide-testing-releases.html
+> >=20
+> > Vote open for at least 72 hours.
+>=20
+> Awesome Herv=E9, +1!
+thanks: I'm happy you like it as I do :)
+
+and here is the plan for the next weeks:
+=2D once the m-site-p release will be out, I'll release Fluido skin
+=2D then enable edit button on Maven parent pom (Apache & Maven parent poms=
+=20
+release)
+=2D then try to use Jenkins to build and publish Maven and Doxia sites (wit=
+hout=20
+staging, that is not useful to us)
+=2D then migrate Maven and Doxia sites sources to Git, with live edit on Gi=
+tHub=20
+for those who like edit from their browser
+=2D then we'll discuss what to do with the few remaining parts in svn...
+
+Regards,
+
+Herv=E9
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 54DBC200D3A
+ for <ar...@cust-asf2.ponee.io>; Wed, 15 Nov 2017 23:06:57 +0100 (CET)
+Received: by cust-asf.ponee.io (Postfix)
+ id 531DB160BF6; Wed, 15 Nov 2017 22:06:57 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 98B8A160BE4
+ for <ar...@cust-asf.ponee.io>; Wed, 15 Nov 2017 23:06:56 +0100 (CET)
+Received: (qmail 76193 invoked by uid 500); 15 Nov 2017 22:06:55 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 76178 invoked by uid 99); 15 Nov 2017 22:06:55 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Nov 2017 22:06:55 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id ADC5F1A1EEB
+ for <de...@maven.apache.org>; Wed, 15 Nov 2017 22:06:54 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id tWrnd63t67a3 for <de...@maven.apache.org>;
+ Wed, 15 Nov 2017 22:06:52 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5A81C60CF1
+ for <de...@maven.apache.org>; Wed, 15 Nov 2017 22:06:52 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d04 with ME
+ id aN6s1w00A20Ufdy03N6syf; Wed, 15 Nov 2017 23:06:52 +0100
+X-ME-Helo: giga.localnet
+X-ME-Date: Wed, 15 Nov 2017 23:06:52 +0100
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: Maven resolver branch consolidation
+Date: Wed, 15 Nov 2017 23:06:51 +0100
+Message-ID: <13...@giga>
+In-Reply-To: <20...@dd17332.kasserver.com>
+References: <20...@dd17332.kasserver.com> <16...@giga> <20...@dd17332.kasserver.com>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Wed, 15 Nov 2017 22:06:57 -0000
+
+let's start with demos: this one is really a great idea
+
+on ant-tasks, I hope my new explanations make the issue more clear
+
+Regards,
+
+Herv=E9
+
+Le mercredi 15 novembre 2017, 18:39:06 CET Manfred Moser a =E9crit :
+> Sorry herve. For some reason I totally missed those. I commented on the
+> issues.
+>=20
+> In summary I would like to get the ant-tasks merged as well since that ma=
+kes
+> a lot more sense to me than keeping it separate.
+>=20
+> Manfred
+>=20
+> Herv=E9 BOUTEMY wrote on 2017-11-14 15:50:
+> > I answered on the mailing list and on the 2 Jira issues
+> > In summary, +1 to merge demos, -1 to merge ant-tasks
+> >=20
+> > Regards,
+> >=20
+> > Herv=E9
+> >=20
+> > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a =E9crit :
+> >> Any feedback or should I just go ahead with the cleanup?
+> >>=20
+> >> Manfred
+> >>=20
+> >> Manfred Moser wrote on 2017-11-08 21:35:
+> >> > Hi all,
+> >> >=20
+> >> > I have started and made good progress on getting Maven resolver all
+> >> > into
+> >> > the master branch instead of having master, demos and ant-tasks in
+> >> > separate branches.
+> >> >=20
+> >> > Details are tracked in
+> >> > https://issues.apache.org/jira/browse/MRESOLVER-28
+> >> >=20
+> >> > All of it is now in a new branch called master-all for you to see.
+> >> >=20
+> >> > I am now wondering what the next steps are. I added what I think sho=
+uld
+> >> > happen next in the issue in a comment and would appreciate any input=
+ on
+> >> > the current setup and next steps.
+> >> >=20
+> >> > Any help would be appreciated.
+> >> >=20
+> >> > manfred
+> >>=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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 714BB200CEF
+ for <ar...@cust-asf2.ponee.io>; Mon, 4 Sep 2017 21:57:32 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 6F83F1653E3; Mon, 4 Sep 2017 19:57:32 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id DF3521653E1
+ for <ar...@cust-asf.ponee.io>; Mon, 4 Sep 2017 21:57:31 +0200 (CEST)
+Received: (qmail 37823 invoked by uid 500); 4 Sep 2017 19:57:29 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 37812 invoked by uid 99); 4 Sep 2017 19:57:29 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2017 19:57:29 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 03DD9D3EDA
+ for <de...@maven.apache.org>; Mon, 4 Sep 2017 19:57:29 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 2.922
+X-Spam-Level: **
+X-Spam-Status: No, score=2.922 tagged_above=-999 required=6.31
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25,
+ KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001,
+ SPF_SOFTFAIL=0.972] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id ZSIjRo_Mg56c for <de...@maven.apache.org>;
+ Mon, 4 Sep 2017 19:57:24 +0000 (UTC)
+Received: from n5.nabble.com (n5.nabble.com [162.253.133.84])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 508B261267
+ for <de...@maven.apache.org>; Mon, 4 Sep 2017 19:57:24 +0000 (UTC)
+Received: from mjim.nabble.com (localhost [127.0.0.1])
+ by n5.nabble.com (Postfix) with ESMTP id 813689A39EFF
+ for <de...@maven.apache.org>; Mon, 4 Sep 2017 12:57:17 -0700 (MST)
+Date: Mon, 4 Sep 2017 12:57:17 -0700 (MST)
+From: dejan2609 <de...@gmail.com>
+To: dev@maven.apache.org
+Message-ID: <15...@n5.nabble.com>
+In-Reply-To: <CA...@mail.gmail.com>
+References: <CA...@mail.gmail.com>
+Subject: Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.0
+MIME-Version: 1.0
+Content-Type: text/plain; charset=us-ascii
+Content-Transfer-Encoding: 7bit
+archived-at: Mon, 04 Sep 2017 19:57:32 -0000
+
+*+1 *
+
+Tested with Maven 3.5.0 / Oracle Java 1.8.0_131 on Windows 10.
+
+
+
+--
+Sent from: http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 7CD0D200D01
+ for <ar...@cust-asf2.ponee.io>; Thu, 7 Sep 2017 10:46:09 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 7B8DF1609BF; Thu, 7 Sep 2017 08:46:09 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id F160C1609DB
+ for <ar...@cust-asf.ponee.io>; Thu, 7 Sep 2017 10:46:08 +0200 (CEST)
+Received: (qmail 32840 invoked by uid 500); 7 Sep 2017 08:46:07 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 32777 invoked by uid 99); 7 Sep 2017 08:46:07 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Sep 2017 08:46:07 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 00999D7D6A
+ for <de...@maven.apache.org>; Thu, 7 Sep 2017 08:46:07 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 2.923
+X-Spam-Level: **
+X-Spam-Status: No, score=2.923 tagged_above=-999 required=6.31
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25,
+ KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001,
+ SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id Sr3M_Gc7Vtey for <de...@maven.apache.org>;
+ Thu, 7 Sep 2017 08:46:02 +0000 (UTC)
+Received: from n5.nabble.com (n5.nabble.com [162.253.133.81])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D4B5761257
+ for <de...@maven.apache.org>; Thu, 7 Sep 2017 08:46:01 +0000 (UTC)
+Received: from n5.nabble.com (localhost [127.0.0.1])
+ by n5.nabble.com (Postfix) with ESMTP id 468C3E98B5
+ for <de...@maven.apache.org>; Thu, 7 Sep 2017 01:46:01 -0700 (MST)
+Date: Thu, 7 Sep 2017 01:46:01 -0700 (MST)
+From: dejan2609 <de...@gmail.com>
+To: dev@maven.apache.org
+Message-ID: <15...@n5.nabble.com>
+In-Reply-To: <CA...@mail.gmail.com>
+References: <CA...@mail.gmail.com>
+Subject: Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.0
+MIME-Version: 1.0
+Content-Type: text/plain; charset=us-ascii
+Content-Transfer-Encoding: 7bit
+archived-at: Thu, 07 Sep 2017 08:46:09 -0000
+
+*+1 *
+
+Tested via Maven 3.5.0 and Oracle Java 1.8 on Windows 10 and Linux Centos 6.
+
+
+
+--
+Sent from: http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id BFEF8200CE6
+ for <ar...@cust-asf2.ponee.io>; Fri, 15 Sep 2017 14:12:31 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id BE9761609D1; Fri, 15 Sep 2017 12:12:31 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id DB1CD1609CF
+ for <ar...@cust-asf.ponee.io>; Fri, 15 Sep 2017 14:12:30 +0200 (CEST)
+Received: (qmail 50977 invoked by uid 500); 15 Sep 2017 12:12:29 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 50964 invoked by uid 99); 15 Sep 2017 12:12:29 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Sep 2017 12:12:29 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 12871184D66
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 12:12:29 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.48
+X-Spam-Level:
+X-Spam-Status: No, score=0.48 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001,
+ URIBL_BLOCKED=0.001] autolearn=disabled
+Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=pg5LQ0WN;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=jfTJVUWI
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id DtdC9JwHtRA7 for <de...@maven.apache.org>;
+ Fri, 15 Sep 2017 12:12:26 +0000 (UTC)
+Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 10C465FBDF
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 12:12:26 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id A840220D4E
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 08:12:25 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Fri, 15 Sep 2017 08:12:25 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=q9zzOyrbSos4Q/x079ePSTtgTTHxR
+ iaN+lIYYUSYwTc=; b=pg5LQ0WNMJLuNAvZTlTZ9mdsBVlt6mMwWEr4tn09fon/4
+ smjjJzZec5ac+Q4gR6qPQJZxPIjJBMIURrZ7Lbh3wFjKxd//QLDWHe+q2LcXy0eT
+ D5jbYfpn40WKKDFniAnkaQFS3ffdCy0gvbYZmHPcS22bZ5jM3io4Z0EDLrLP8kBp
+ 8d7HHP6dHnd2ZKUaNW97boo2qRz4RI2x9nUfu2WGtDsLrlUxTZz7kAYz9Y4nb6u2
+ E80dBauS5w3tDGeepEQqUAUIPRIru4nMENpVEH9CyVu5UsDtaux8duqa+vOH/tR4
+ UEyr10BIFSn9cfABJidfcGeUro/b0uzz3GFVHXmJw==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=q9zzOy
+ rbSos4Q/x079ePSTtgTTHxRiaN+lIYYUSYwTc=; b=jfTJVUWIuyFP8jzBk26xFZ
+ Spf7qOazWWITn8UHDqIwVrIsSKPpggkQeHeNwgN2tz8gLPsWKzL5Gp7qvQROUOLB
+ r1p8ir08zeqwATkA79WjEMYfIEwT+RQ53sPcyn8FtXdqabhlyUt6CS7ttWuxQRaf
+ W8RsOULQqmSvLiuynyHvSBVRTYxZzEtAGZsgeKARqNPRFq0TUGxPPu+0nb3SUoli
+ LxtIv4LNdF8MDpqavRXZDgAGrRk3DZoNcuxYQdleh8Tmtvar/KvOvvguLO+Se7T1
+ OI9VgTn1oB8NC8NfhD8vWyckS4/RiC9Z0I+jJkoOGLoAdJKj/kzKvH0koRrK2w2Q
+ ==
+X-ME-Sender: <xms:qcO7WdG6vu5XEQA9FWVtPUpV31R9GSBVrQ6Ya5TuoyDrjqvpnxOaUQ>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 873C96264D; Fri, 15 Sep 2017 08:12:25 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Subject: Re: [VOTE] Release Apache Maven 3.5.1
+Date: Fri, 15 Sep 2017 08:12:25 -0400
+References: <CA...@mail.gmail.com>
+ <po...@dev.maven.apache.org>
+ <CA...@mail.gmail.com>
+ <20...@giga>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+In-Reply-To: <CA...@mail.gmail.com>
+archived-at: Fri, 15 Sep 2017 12:12:31 -0000
+
+I answered in more details on m2e-dev, but I believe we can compensate
+for the change from m2e end. In the worst case we'll bundle hacked
+version of DefaultClassRealmManager with m2e, not ideal, but not the end
+of the world either.=20
+
+--=20
+Regards,
+Igor
+
+On Fri, Sep 15, 2017, at 07:21 AM, Anders Hammar wrote:
+> On Fri, Sep 15, 2017 at 8:29 AM, Anders Hammar <an...@hammar.net> wrote:
+>=20
+> > Reporting back from tests of m2e with embedded Maven 3.5.1, we see prob=
+lem
+> > with the jaxws-maven-plugin mojo. We're two people seeing the issue
+> > independently, but unfortunately Fred Bricon hasn't been able to reprod=
+uce.
+> >
+>=20
+> To follow up on this, my tests indicate that Maven 3.5.1 causes changed
+> class loading that could cause issues for plugins in m2e. I've asked for
+> input from the m2e devs if it is possible to handle in m2e but they
+> haven't
+> responded yet.
+>=20
+> /Anders
+>=20
+>=20
+> >
+> > So currently I'm 0 on the voting but I'll investigate some more.
+> >
+> > /Anders
+> >
+> > On Wed, Sep 13, 2017 at 9:26 AM, Anders Hammar <an...@hammar.net> wrot=
+e:
+> >
+> >>
+> >>
+> >> On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly <
+> >> stephen.alan.connolly@gmail.com> wrote:
+> >>
+> >>> Have we got any feedback from the embedder integrations yet?
+> >>>
+> >>
+> >> I haven't heard anything from the m2e people. Maybe we need to ping th=
+em
+> >> directly. I can contact Fred Bricon.
+> >>
+> >> /Anders
+> >>
+> >>
+> >>>
+> >>> On Mon 11 Sep 2017 at 22:57, Herv=C3=A9 BOUTEMY <herve.boutemy@free.f=
+r>
+> >>> wrote:
+> >>>
+> >>> > just for the records: it is Windows + Git Bash (MINGW64) only
+> >>> >
+> >>> > and there is a chance that adding -Djansi.force=3Dtrue can force JA=
+nsi
+> >>> > activation (even if JAnsi fails to detect that it should auto-activ=
+ate)
+> >>> >
+> >>> > details on issue in https://issues.apache.org/jira/browse/MNG-6282 ,
+> >>> and a
+> >>> > future JAnsi issue...
+> >>> >
+> >>> > Regards,
+> >>> >
+> >>> > Herv=C3=A9
+> >>> >
+> >>> > Le lundi 11 septembre 2017, 12:53:46 CEST Stephen Connolly a =C3=A9=
+crit :
+> >>> > > So that is windows only, or were they lost on other OSes for you.
+> >>> > >
+> >>> > > I have colours on linux (via docker) and os-x
+> >>> > >
+> >>> > > On 11 September 2017 at 12:35, dejan2609@gmail.com <
+> >>> dejan2609@gmail.com>
+> >>> > >
+> >>> > > wrote:
+> >>> > > > +1 (conditionally).
+> >>> > > >
+> >>> > > > Tested via project that includes dozen of plugins: 1st tier,
+> >>> MojoHaus
+> >>> > and
+> >>> > > > few 3rd party plugins (so to say).
+> >>> > > >
+> >>> > > > Everything looks good with one notable regression:
+> >>> > > > https://issues.apache.org/jira/browse/MNG-6282 Console output h=
+as
+> >>> no
+> >>> > > > colors (regression in Maven 3.5.1)
+> >>> > > >
+> >>> > > > Regards,
+> >>> > > > Dejan
+> >>> > > >
+> >>> > > > On 2017-09-10 17:39, Stephen Connolly <
+> >>> stephen.alan.connolly@gmail.com
+> >>> > >
+> >>> > > >
+> >>> > > > wrote:
+> >>> > > > > Hi,
+> >>> > > > >
+> >>> > > > > We solved 25 issues:
+> >>> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
+> >>> > > >
+> >>> > > > version=3D12338964&styleName=3DText&projectId=3D12316922
+> >>> > > >
+> >>> > > > > There are 350 issues left in JIRA for Maven core:
+> >>> > > > > https://issues.apache.org/jira/issues/?jql=3Dproject%20%
+> >>> > > >
+> >>> > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
+> >>> > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
+> >>> > > >
+> >>> > > > > Staging repo:
+> >>> > > > > https://repository.apache.org/content/repositories/maven-1364/
+> >>> > > > >
+> >>> > > > > The distributable binaries and sources can be found here:
+> >>> > > > > https://repository.apache.org/content/repositories/maven-> >
+> >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/
+> >>> > > >
+> >>> > > > > Specifically the zip, tarball and source archives can be found
+> >>> here:
+> >>> > > > > https://repository.apache.org/content/repositories/maven-> >
+> >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-
+> >>> bin.zip
+> >>> > > >
+> >>> > > > > https://repository.apache.org/content/repositories/maven-> >
+> >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-
+> >>> bin.tar.gz
+> >>> > > >
+> >>> > > > > https://repository.apache.org/content/repositories/maven-> >
+> >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-
+> >>> src.zip
+> >>> > > >
+> >>> > > > > https://repository.apache.org/content/repositories/maven-> >
+> >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-
+> >>> src.tar.gz
+> >>> > > >
+> >>> > > > > Source release checksum(s):
+> >>> > > > > apache-maven-3.5.1-src.tar.gz sha1:
+> >>> 9eb821f153c7667194aa11ccd099b7
+> >>> > > >
+> >>> > > > bd2059560d
+> >>> > > >
+> >>> > > > > apache-maven-3.5.1-src.zip: sha1: 121d54b045380a8a4895eb13797=
+0ab
+> >>> > > >
+> >>> > > > 69e698eb0e
+> >>> > > >
+> >>> > > > > Git tag:
+> >>> > > > > https://git-wip-us.apache.org/repos/asf?p=3Dmaven.git;a=3Dcom=
+mit;h=3D
+> >>> > > >
+> >>> > > > 094e4e31a5af55bb17be87675da41d9aeca062f3
+> >>> > > >
+> >>> > > > > Staging site:
+> >>> > > > > https://maven.apache.org/components/ref/3-LATEST/
+> >>> > > > >
+> >>> > > > > Vote open for 72 hours.
+> >>> > > > >
+> >>> > > > > [ ] +1
+> >>> > > > > [ ] +0
+> >>> > > > > [ ] -1
+> >>> > > > >
+> >>> > > > > Thanks,
+> >>> > > > >
+> >>> > > > > Stephen.
+> >>> > > >
+> >>> > > > ------------------------------------------------------------
+> >>> ---------
+> >>> > > > 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
+> >>> >
+> >>> > --
+> >>> Sent from my phone
+> >>>
+> >>
+> >>
+> >
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 01613200CE6
+ for <ar...@cust-asf2.ponee.io>; Fri, 15 Sep 2017 14:45:16 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id F40901609D1; Fri, 15 Sep 2017 12:45:15 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id EAB331609CF
+ for <ar...@cust-asf.ponee.io>; Fri, 15 Sep 2017 14:45:14 +0200 (CEST)
+Received: (qmail 4795 invoked by uid 500); 15 Sep 2017 12:45:13 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 4778 invoked by uid 99); 15 Sep 2017 12:45:13 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Sep 2017 12:45:13 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 300FFC3E04
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 12:45:13 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.48
+X-Spam-Level:
+X-Spam-Status: No, score=0.48 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001,
+ URIBL_BLOCKED=0.001] autolearn=disabled
+Authentication-Results: spamd1-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=s0siDiDT;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=exukrpcc
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id oBoEG7xfc_oF for <de...@maven.apache.org>;
+ Fri, 15 Sep 2017 12:45:12 +0000 (UTC)
+Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id D3B1B5FAF3
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 12:45:11 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id ABABB20B5D
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 08:45:10 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Fri, 15 Sep 2017 08:45:10 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=dudzpFm5QjesuC3E3jClpadPv8POL
+ ZXw5U38zL3SSdg=; b=s0siDiDTVO502P/GZIj3ojqx2efdXmTxt8lL84A2Nxw0k
+ uOiFpgUqTWONQup2hcLDAerT2UY0TnvK7souwLNu9z8Cjvzs+ODRlywNKWLn0GuS
+ CjsfKROU43MFaalMBwjUlQWzxfUWDx9Ag/FCr8gksShX8qAKx+GnZAS0XA2WEm/5
+ 051wYjxycaDwi3uVsCRiEPCyxMuNIr8umZaoJXajN/edEwfFdE/dFCx/DGJsmI4u
+ B0tdbenAOSfNzQptBo8wrrByjtcY1VeemPwFlewM/WkoH89CWh11CZdWREWkmXUg
+ yQxL6qiwGM6imL7Itt6RuTMvk/lIrR594GuElIkRA==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=dudzpF
+ m5QjesuC3E3jClpadPv8POLZXw5U38zL3SSdg=; b=exukrpccuUJ9D/d/X4QBZy
+ UmBEhH3UogtGgAHBBXGH7+DnS4t/rYXO1tVNWsZze96lwpMwJQlIaHEj82iV1yub
+ H2bMLVhAB0C2aV06zd5ua+nKsIZIU3Palu9UyQyCHIu1h2ylLyZHzBjlL2rJboYH
+ kW2ZwzSA42vtGEUZx6snTuvovE7illRLJjetyW/iqQQpUdaPnefzDptRA+bZn2y1
+ J1LcLCwsU0mUjqUS2/b4V83jPQ8FQR7Osnm1eKlT3hZqF82K+3sX6NOj1oVkGiF7
+ RquioJBbCKN+15Pgb3/UJUqvqZx/i3kb6fKP5g+BXtDwdnf9+yiXVoUvrwK+4ELQ
+ ==
+X-ME-Sender: <xms:Vsu7WSPGCGx-gyu57CFu5mJ7nL6Ky6uWW6KQ-vDccKb0xYoHQtAsHQ>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 7E35B6264D; Fri, 15 Sep 2017 08:45:10 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Subject: Re: [VOTE] Release Apache Maven 3.5.1
+Date: Fri, 15 Sep 2017 08:45:10 -0400
+In-Reply-To: <CA...@mail.gmail.com>
+References: <CA...@mail.gmail.com>
+ <po...@dev.maven.apache.org>
+ <CA...@mail.gmail.com>
+ <20...@giga>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+archived-at: Fri, 15 Sep 2017 12:45:16 -0000
+
+Has anyone tried wiring jvm extensions ClassLoader as foreign import to
+plugin/extensions realms? Jvm extensions classloader is little tricky to
+get to (see how this is done in java.util.ServiceLoader.loadInstalled),
+but I think this will solve ServiceLoader/MNG-6275 without polluting
+plugin classpath too much.
+
+--=20
+Regards,
+Igor
+
+On Fri, Sep 15, 2017, at 08:32 AM, Mark Derricutt wrote:
+> Would it be possible to handle this in a somewhat similar way to
+> threadSafe
+> mojos - some form of plugin flag that says "extensionSafe" [1], that if
+> the
+> plugin has <extensions>true</extensions> declared and doesn't declare
+> itself as being extensionSafe/extensionAware then we log a build warning
+> -
+> it wouldn't solve anything, other than giving some feedback to users some
+> indication of WHY their build fails under 3.5.1 - and to either remove
+> <extensions> or fix/update their plugins.
+>=20
+> [1] Or even just infer the applicability of extensions by the presence of
+> custom lifecycles, or Mojos implementing the extension interfaces ( it's
+> midnight, and a hazy tired thought ).
+>=20
+> --=20
+> "Great artists are extremely selfish and arrogant things" =E2=80=94 Steven
+> Wilson,
+> Porcupine Tree
+>=20
+> On Sat, Sep 16, 2017 at 12:22 AM, Anders Hammar <an...@hammar.net>
+> wrote:
+>=20
+> > Based on Igor's feedback I'm changing my vote to +1.
+> >
+> > Having this class loader change in a bug fix release is probably not
+> > (semver) ideal though.
+> >
+> > /Anders
+> >
+> > On Fri, Sep 15, 2017 at 2:12 PM, Igor Fedorenko <ig...@ifedorenko.com>
+> > wrote:
+> >
+> > > I answered in more details on m2e-dev, but I believe we can compensate
+> > > for the change from m2e end. In the worst case we'll bundle hacked
+> > > version of DefaultClassRealmManager with m2e, not ideal, but not the =
+end
+> > > of the world either.
+> > >
+> > > --
+> > > Regards,
+> > > Igor
+> > >
+> > > On Fri, Sep 15, 2017, at 07:21 AM, Anders Hammar wrote:
+> > > > On Fri, Sep 15, 2017 at 8:29 AM, Anders Hammar <an...@hammar.net>
+> > > wrote:
+> > > >
+> > > > > Reporting back from tests of m2e with embedded Maven 3.5.1, we see
+> > > problem
+> > > > > with the jaxws-maven-plugin mojo. We're two people seeing the iss=
+ue
+> > > > > independently, but unfortunately Fred Bricon hasn't been able to
+> > > reproduce.
+> > > > >
+> > > >
+> > > > To follow up on this, my tests indicate that Maven 3.5.1 causes cha=
+nged
+> > > > class loading that could cause issues for plugins in m2e. I've asked
+> > for
+> > > > input from the m2e devs if it is possible to handle in m2e but they
+> > > > haven't
+> > > > responded yet.
+> > > >
+> > > > /Anders
+> > > >
+> > > >
+> > > > >
+> > > > > So currently I'm 0 on the voting but I'll investigate some more.
+> > > > >
+> > > > > /Anders
+> > > > >
+> > > > > On Wed, Sep 13, 2017 at 9:26 AM, Anders Hammar <an...@hammar.net>
+> > > wrote:
+> > > > >
+> > > > >>
+> > > > >>
+> > > > >> On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly <
+> > > > >> stephen.alan.connolly@gmail.com> wrote:
+> > > > >>
+> > > > >>> Have we got any feedback from the embedder integrations yet?
+> > > > >>>
+> > > > >>
+> > > > >> I haven't heard anything from the m2e people. Maybe we need to p=
+ing
+> > > them
+> > > > >> directly. I can contact Fred Bricon.
+> > > > >>
+> > > > >> /Anders
+> > > > >>
+> > > > >>
+> > > > >>>
+> > > > >>> On Mon 11 Sep 2017 at 22:57, Herv=C3=A9 BOUTEMY <herve.boutemy@=
+free.fr>
+> > > > >>> wrote:
+> > > > >>>
+> > > > >>> > just for the records: it is Windows + Git Bash (MINGW64) only
+> > > > >>> >
+> > > > >>> > and there is a chance that adding -Djansi.force=3Dtrue can fo=
+rce
+> > > JAnsi
+> > > > >>> > activation (even if JAnsi fails to detect that it should
+> > > auto-activate)
+> > > > >>> >
+> > > > >>> > details on issue in https://issues.apache.org/
+> > jira/browse/MNG-6282
+> > > ,
+> > > > >>> and a
+> > > > >>> > future JAnsi issue...
+> > > > >>> >
+> > > > >>> > Regards,
+> > > > >>> >
+> > > > >>> > Herv=C3=A9
+> > > > >>> >
+> > > > >>> > Le lundi 11 septembre 2017, 12:53:46 CEST Stephen Connolly a
+> > =C3=A9crit
+> > > :
+> > > > >>> > > So that is windows only, or were they lost on other OSes for
+> > you.
+> > > > >>> > >
+> > > > >>> > > I have colours on linux (via docker) and os-x
+> > > > >>> > >
+> > > > >>> > > On 11 September 2017 at 12:35, dejan2609@gmail.com <
+> > > > >>> dejan2609@gmail.com>
+> > > > >>> > >
+> > > > >>> > > wrote:
+> > > > >>> > > > +1 (conditionally).
+> > > > >>> > > >
+> > > > >>> > > > Tested via project that includes dozen of plugins: 1st ti=
+er,
+> > > > >>> MojoHaus
+> > > > >>> > and
+> > > > >>> > > > few 3rd party plugins (so to say).
+> > > > >>> > > >
+> > > > >>> > > > Everything looks good with one notable regression:
+> > > > >>> > > > https://issues.apache.org/jira/browse/MNG-6282 Console
+> > output
+> > > has
+> > > > >>> no
+> > > > >>> > > > colors (regression in Maven 3.5.1)
+> > > > >>> > > >
+> > > > >>> > > > Regards,
+> > > > >>> > > > Dejan
+> > > > >>> > > >
+> > > > >>> > > > On 2017-09-10 17:39, Stephen Connolly <
+> > > > >>> stephen.alan.connolly@gmail.com
+> > > > >>> > >
+> > > > >>> > > >
+> > > > >>> > > > wrote:
+> > > > >>> > > > > Hi,
+> > > > >>> > > > >
+> > > > >>> > > > > We solved 25 issues:
+> > > > >>> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
+> > > > >>> > > >
+> > > > >>> > > > version=3D12338964&styleName=3DText&projectId=3D12316922
+> > > > >>> > > >
+> > > > >>> > > > > There are 350 issues left in JIRA for Maven core:
+> > > > >>> > > > > https://issues.apache.org/jira/issues/?jql=3Dproject%20%
+> > > > >>> > > >
+> > > > >>> > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
+> > > > >>> > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
+> > > > >>> > > >
+> > > > >>> > > > > Staging repo:
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n-
+> > > 1364/
+> > > > >>> > > > >
+> > > > >>> > > > > The distributable binaries and sources can be found her=
+e:
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n->
+> > >
+> > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/
+> > > > >>> > > >
+> > > > >>> > > > > Specifically the zip, tarball and source archives can be
+> > > found
+> > > > >>> here:
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n->
+> > >
+> > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5=
+.1-
+> > > > >>> bin.zip
+> > > > >>> > > >
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n->
+> > >
+> > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5=
+.1-
+> > > > >>> bin.tar.gz
+> > > > >>> > > >
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n->
+> > >
+> > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5=
+.1-
+> > > > >>> src.zip
+> > > > >>> > > >
+> > > > >>> > > > > https://repository.apache.org/content/repositories/mave=
+n->
+> > >
+> > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5=
+.1-
+> > > > >>> src.tar.gz
+> > > > >>> > > >
+> > > > >>> > > > > Source release checksum(s):
+> > > > >>> > > > > apache-maven-3.5.1-src.tar.gz sha1:
+> > > > >>> 9eb821f153c7667194aa11ccd099b7
+> > > > >>> > > >
+> > > > >>> > > > bd2059560d
+> > > > >>> > > >
+> > > > >>> > > > > apache-maven-3.5.1-src.zip: sha1:
+> > > 121d54b045380a8a4895eb137970ab
+> > > > >>> > > >
+> > > > >>> > > > 69e698eb0e
+> > > > >>> > > >
+> > > > >>> > > > > Git tag:
+> > > > >>> > > > > https://git-wip-us.apache.org/repos/asf?p=3Dmaven.git;a=
+=3D
+> > > commit;h=3D
+> > > > >>> > > >
+> > > > >>> > > > 094e4e31a5af55bb17be87675da41d9aeca062f3
+> > > > >>> > > >
+> > > > >>> > > > > Staging site:
+> > > > >>> > > > > https://maven.apache.org/components/ref/3-LATEST/
+> > > > >>> > > > >
+> > > > >>> > > > > Vote open for 72 hours.
+> > > > >>> > > > >
+> > > > >>> > > > > [ ] +1
+> > > > >>> > > > > [ ] +0
+> > > > >>> > > > > [ ] -1
+> > > > >>> > > > >
+> > > > >>> > > > > Thanks,
+> > > > >>> > > > >
+> > > > >>> > > > > Stephen.
+> > > > >>> > > >
+> > > > >>> > > > ---------------------------------------------------------=
+---
+> > > > >>> ---------
+> > > > >>> > > > 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
+> > > > >>> >
+> > > > >>> > --
+> > > > >>> Sent from my phone
+> > > > >>>
+> > > > >>
+> > > > >>
+> > > > >
+> > >
+> > > ---------------------------------------------------------------------
+> > > 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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 1E873200D13
+ for <ar...@cust-asf2.ponee.io>; Sat, 16 Sep 2017 05:07:39 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 1D5381609D2; Sat, 16 Sep 2017 03:07:39 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 132E91609D1
+ for <ar...@cust-asf.ponee.io>; Sat, 16 Sep 2017 05:07:37 +0200 (CEST)
+Received: (qmail 3601 invoked by uid 500); 16 Sep 2017 03:07:36 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 3588 invoked by uid 99); 16 Sep 2017 03:07:36 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Sep 2017 03:07:36 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0A4761A19FE
+ for <de...@maven.apache.org>; Sat, 16 Sep 2017 03:07:36 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.479
+X-Spam-Level:
+X-Spam-Status: No, score=0.479 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=qf2ypOHy;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=pLZT8RC2
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id jf4753H4TOIw for <de...@maven.apache.org>;
+ Sat, 16 Sep 2017 03:07:33 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A92105FAF7
+ for <de...@maven.apache.org>; Sat, 16 Sep 2017 03:07:32 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id 0D45720D9D
+ for <de...@maven.apache.org>; Fri, 15 Sep 2017 23:07:26 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Fri, 15 Sep 2017 23:07:26 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=MrTLEHbqxq/p3vpWqEvf+MpbvFNOZ
+ SMIb1zVWp+kuFA=; b=qf2ypOHy9NHLR2jcKAMuSfip4WMlo2CcK/Yn7vyybRF/Q
+ QA1yW96kANH0EkB2UB+1JY08Wo9PJNYk3tGnBeavzKSGl6k8H6KINIH9QZgWy8BO
+ ht6O10hJ007daK2DhL1hc4hB4AbIvgM/tA2mns9rxzFCSjXKQd94XJXl2S32nwMa
+ nXZWlGLdmdNVpF+zr02bWbF/W1j/8YEGXZi+3qLPVzMLWuOfhwO1dCjqnxQEIxFR
+ Gc98A1b/4HqrHVrSnEMwqrbRQtioxfyX8nDKvazF3HCA08SK1AThakhvxT2ewno4
+ SDUddF0RCamvhyFK+r1jZJuPysxJjvSi4go2m27Ig==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=MrTLEH
+ bqxq/p3vpWqEvf+MpbvFNOZSMIb1zVWp+kuFA=; b=pLZT8RC251QFIIP6D2IxP5
+ pjsgNGYTXzRFHv1GEU1h2x+3FRHFpjNVSVMMnXgwVjzSLLIWDjayUvadxJbRVcYU
+ fiKj9v6z0T2cOkNAiwa/Xm2uvpzu2sVkcHdLWPpOjT5n1+dyp/8Wf7TbdBdqsrlb
+ NlJySrKKwj/az6+8SDjke/c8nTbGX0GiHk7Qkhd0+fH1n3lHg59AcInHFOZshhIZ
+ gjFsUp6tlIbjRFI1LK5SBjJF5fVFaiPSECGtzrQpQypvTMIYgo2v+H3BpyqpDnu2
+ TGsFe+8OKifroxaW24lD+/+3fOQp7QUZ9No7le5VFOCLyXtnX+bABkdBF7lbCxHw
+ ==
+X-ME-Sender: <xms:bZW8WeEoby_POSXY6jHnRwmF_t1emsViAL-zj8UkoCFgV6H2wa2Xmg>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id C04B66264D; Fri, 15 Sep 2017 23:07:25 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Subject: Re: [VOTE] Release Apache Maven 3.5.1
+Date: Fri, 15 Sep 2017 23:07:25 -0400
+References: <CA...@mail.gmail.com>
+ <po...@dev.maven.apache.org>
+ <CA...@mail.gmail.com>
+ <20...@giga>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+In-Reply-To: <CA...@mail.gmail.com>
+archived-at: Sat, 16 Sep 2017 03:07:39 -0000
+
+I don't really have much to add, but let me answer anyways :-)
+
+1) I am reasonably confident we can compensate for the new classloader
+arrangement in m2e without much problems. The new setup does make plugin
+runtime classpath less stable, so there are likely other scenarios where
+plugins will behave differently (bad). On the other hand, I don't see
+any better way to support ServiceLoader. For java 8 it may be possible
+to use foreign-import of extensions classloader to fix MNG-6275, but
+that classloader was removed in java 9, unless I am mistaken.
+
+2) I believe TCCL is already set to project realm for projects that have
+extensions (and to plugin realm otherwise) during plugin execution.
+Problem is, neither project realm nor any of the plugin realms have
+access to jvm extensions classloader, so ServiceLoader can't get classes
+from there.=20
+
+--=20
+Regards,
+Igor
+
+On Fri, Sep 15, 2017, at 12:09 PM, Stephen Connolly wrote:
+> I'm going to hold off closing the vote over the weekend to give Igor a
+> chance to:
+>=20
+> 1. comment on whether we need an alternative fix for MNG-6275 (and indeed
+> ideally provide one ;- );
+> 2. comment on whether the fix for MNG-6209 is exposing bugs in plugins
+> that
+> made incorrect assumptions about TCCL, or whether the fix is invalid or
+> even incomplete (I wonder if TCCL should always be
+> project.getClassRealm()
+> as extensions should be available to all plugins not just those that
+> declare they are providing extensions - unless I misunderstand)
+>=20
+> Once I have the required information I will be better able to assess
+> whether we should release 3.5.1 and follow up with a quick 3.5.2 or just
+> drop 3.5.1 and go straight to 3.5.2.
+>=20
+> -Stephen
+>=20
+> On 15 September 2017 at 05:45, Igor Fedorenko <ig...@ifedorenko.com>
+> wrote:
+>=20
+> > Has anyone tried wiring jvm extensions ClassLoader as foreign import to
+> > plugin/extensions realms? Jvm extensions classloader is little tricky to
+> > get to (see how this is done in java.util.ServiceLoader.loadInstalled),
+> > but I think this will solve ServiceLoader/MNG-6275 without polluting
+> > plugin classpath too much.
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> > On Fri, Sep 15, 2017, at 08:32 AM, Mark Derricutt wrote:
+> > > Would it be possible to handle this in a somewhat similar way to
+> > > threadSafe
+> > > mojos - some form of plugin flag that says "extensionSafe" [1], that =
+if
+> > > the
+> > > plugin has <extensions>true</extensions> declared and doesn't declare
+> > > itself as being extensionSafe/extensionAware then we log a build warn=
+ing
+> > > -
+> > > it wouldn't solve anything, other than giving some feedback to users =
+some
+> > > indication of WHY their build fails under 3.5.1 - and to either remove
+> > > <extensions> or fix/update their plugins.
+> > >
+> > > [1] Or even just infer the applicability of extensions by the presenc=
+e of
+> > > custom lifecycles, or Mojos implementing the extension interfaces ( i=
+t's
+> > > midnight, and a hazy tired thought ).
+> > >
+> > > --
+> > > "Great artists are extremely selfish and arrogant things" =E2=80=94 S=
+teven
+> > > Wilson,
+> > > Porcupine Tree
+> > >
+> > > On Sat, Sep 16, 2017 at 12:22 AM, Anders Hammar <an...@hammar.net>
+> > > wrote:
+> > >
+> > > > Based on Igor's feedback I'm changing my vote to +1.
+> > > >
+> > > > Having this class loader change in a bug fix release is probably not
+> > > > (semver) ideal though.
+> > > >
+> > > > /Anders
+> > > >
+> > > > On Fri, Sep 15, 2017 at 2:12 PM, Igor Fedorenko <igor@ifedorenko.co=
+m>
+> > > > wrote:
+> > > >
+> > > > > I answered in more details on m2e-dev, but I believe we can
+> > compensate
+> > > > > for the change from m2e end. In the worst case we'll bundle hacked
+> > > > > version of DefaultClassRealmManager with m2e, not ideal, but not =
+the
+> > end
+> > > > > of the world either.
+> > > > >
+> > > > > --
+> > > > > Regards,
+> > > > > Igor
+> > > > >
+> > > > > On Fri, Sep 15, 2017, at 07:21 AM, Anders Hammar wrote:
+> > > > > > On Fri, Sep 15, 2017 at 8:29 AM, Anders Hammar <anders@hammar.n=
+et>
+> > > > > wrote:
+> > > > > >
+> > > > > > > Reporting back from tests of m2e with embedded Maven 3.5.1, we
+> > see
+> > > > > problem
+> > > > > > > with the jaxws-maven-plugin mojo. We're two people seeing the
+> > issue
+> > > > > > > independently, but unfortunately Fred Bricon hasn't been able=
+ to
+> > > > > reproduce.
+> > > > > > >
+> > > > > >
+> > > > > > To follow up on this, my tests indicate that Maven 3.5.1 causes
+> > changed
+> > > > > > class loading that could cause issues for plugins in m2e. I've
+> > asked
+> > > > for
+> > > > > > input from the m2e devs if it is possible to handle in m2e but =
+they
+> > > > > > haven't
+> > > > > > responded yet.
+> > > > > >
+> > > > > > /Anders
+> > > > > >
+> > > > > >
+> > > > > > >
+> > > > > > > So currently I'm 0 on the voting but I'll investigate some mo=
+re.
+> > > > > > >
+> > > > > > > /Anders
+> > > > > > >
+> > > > > > > On Wed, Sep 13, 2017 at 9:26 AM, Anders Hammar <
+> > anders@hammar.net>
+> > > > > wrote:
+> > > > > > >
+> > > > > > >>
+> > > > > > >>
+> > > > > > >> On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly <
+> > > > > > >> stephen.alan.connolly@gmail.com> wrote:
+> > > > > > >>
+> > > > > > >>> Have we got any feedback from the embedder integrations yet?
+> > > > > > >>>
+> > > > > > >>
+> > > > > > >> I haven't heard anything from the m2e people. Maybe we need =
+to
+> > ping
+> > > > > them
+> > > > > > >> directly. I can contact Fred Bricon.
+> > > > > > >>
+> > > > > > >> /Anders
+> > > > > > >>
+> > > > > > >>
+> > > > > > >>>
+> > > > > > >>> On Mon 11 Sep 2017 at 22:57, Herv=C3=A9 BOUTEMY <
+> > herve.boutemy@free.fr>
+> > > > > > >>> wrote:
+> > > > > > >>>
+> > > > > > >>> > just for the records: it is Windows + Git Bash (MINGW64) =
+only
+> > > > > > >>> >
+> > > > > > >>> > and there is a chance that adding -Djansi.force=3Dtrue can
+> > force
+> > > > > JAnsi
+> > > > > > >>> > activation (even if JAnsi fails to detect that it should
+> > > > > auto-activate)
+> > > > > > >>> >
+> > > > > > >>> > details on issue in https://issues.apache.org/
+> > > > jira/browse/MNG-6282
+> > > > > ,
+> > > > > > >>> and a
+> > > > > > >>> > future JAnsi issue...
+> > > > > > >>> >
+> > > > > > >>> > Regards,
+> > > > > > >>> >
+> > > > > > >>> > Herv=C3=A9
+> > > > > > >>> >
+> > > > > > >>> > Le lundi 11 septembre 2017, 12:53:46 CEST Stephen Connoll=
+y a
+> > > > =C3=A9crit
+> > > > > :
+> > > > > > >>> > > So that is windows only, or were they lost on other OSes
+> > for
+> > > > you.
+> > > > > > >>> > >
+> > > > > > >>> > > I have colours on linux (via docker) and os-x
+> > > > > > >>> > >
+> > > > > > >>> > > On 11 September 2017 at 12:35, dejan2609@gmail.com <
+> > > > > > >>> dejan2609@gmail.com>
+> > > > > > >>> > >
+> > > > > > >>> > > wrote:
+> > > > > > >>> > > > +1 (conditionally).
+> > > > > > >>> > > >
+> > > > > > >>> > > > Tested via project that includes dozen of plugins: 1st
+> > tier,
+> > > > > > >>> MojoHaus
+> > > > > > >>> > and
+> > > > > > >>> > > > few 3rd party plugins (so to say).
+> > > > > > >>> > > >
+> > > > > > >>> > > > Everything looks good with one notable regression:
+> > > > > > >>> > > > https://issues.apache.org/jira/browse/MNG-6282 Console
+> > > > output
+> > > > > has
+> > > > > > >>> no
+> > > > > > >>> > > > colors (regression in Maven 3.5.1)
+> > > > > > >>> > > >
+> > > > > > >>> > > > Regards,
+> > > > > > >>> > > > Dejan
+> > > > > > >>> > > >
+> > > > > > >>> > > > On 2017-09-10 17:39, Stephen Connolly <
+> > > > > > >>> stephen.alan.connolly@gmail.com
+> > > > > > >>> > >
+> > > > > > >>> > > >
+> > > > > > >>> > > > wrote:
+> > > > > > >>> > > > > Hi,
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > We solved 25 issues:
+> > > > > > >>> > > > > https://issues.apache.org/jira/secure/ReleaseNote.j=
+spa
+> > ?
+> > > > > > >>> > > >
+> > > > > > >>> > > > version=3D12338964&styleName=3DText&projectId=3D12316=
+922
+> > > > > > >>> > > >
+> > > > > > >>> > > > > There are 350 issues left in JIRA for Maven core:
+> > > > > > >>> > > > > https://issues.apache.org/jira/issues/?jql=3Dprojec=
+t%20%
+> > > > > > >>> > > >
+> > > > > > >>> > > > 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDE=
+R%
+> > > > > > >>> > > > 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20=
+ASC
+> > > > > > >>> > > >
+> > > > > > >>> > > > > Staging repo:
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven-
+> > > > > 1364/
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > The distributable binaries and sources can be found
+> > here:
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven->
+> > > > >
+> > > > > > >>> > > > 1364/org/apache/maven/apache-maven/3.5.1/
+> > > > > > >>> > > >
+> > > > > > >>> > > > > Specifically the zip, tarball and source archives c=
+an
+> > be
+> > > > > found
+> > > > > > >>> here:
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven->
+> > > > >
+> > > > > > >>> > > > 1364/org/apache/maven/apache-
+> > maven/3.5.1/apache-maven-3.5.1-
+> > > > > > >>> bin.zip
+> > > > > > >>> > > >
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven->
+> > > > >
+> > > > > > >>> > > > 1364/org/apache/maven/apache-
+> > maven/3.5.1/apache-maven-3.5.1-
+> > > > > > >>> bin.tar.gz
+> > > > > > >>> > > >
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven->
+> > > > >
+> > > > > > >>> > > > 1364/org/apache/maven/apache-
+> > maven/3.5.1/apache-maven-3.5.1-
+> > > > > > >>> src.zip
+> > > > > > >>> > > >
+> > > > > > >>> > > > > https://repository.apache.org/
+> > content/repositories/maven->
+> > > > >
+> > > > > > >>> > > > 1364/org/apache/maven/apache-
+> > maven/3.5.1/apache-maven-3.5.1-
+> > > > > > >>> src.tar.gz
+> > > > > > >>> > > >
+> > > > > > >>> > > > > Source release checksum(s):
+> > > > > > >>> > > > > apache-maven-3.5.1-src.tar.gz sha1:
+> > > > > > >>> 9eb821f153c7667194aa11ccd099b7
+> > > > > > >>> > > >
+> > > > > > >>> > > > bd2059560d
+> > > > > > >>> > > >
+> > > > > > >>> > > > > apache-maven-3.5.1-src.zip: sha1:
+> > > > > 121d54b045380a8a4895eb137970ab
+> > > > > > >>> > > >
+> > > > > > >>> > > > 69e698eb0e
+> > > > > > >>> > > >
+> > > > > > >>> > > > > Git tag:
+> > > > > > >>> > > > > https://git-wip-us.apache.org/repos/asf?p=3Dmaven.g=
+it;a=3D
+> > > > > commit;h=3D
+> > > > > > >>> > > >
+> > > > > > >>> > > > 094e4e31a5af55bb17be87675da41d9aeca062f3
+> > > > > > >>> > > >
+> > > > > > >>> > > > > Staging site:
+> > > > > > >>> > > > > https://maven.apache.org/components/ref/3-LATEST/
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > Vote open for 72 hours.
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > [ ] +1
+> > > > > > >>> > > > > [ ] +0
+> > > > > > >>> > > > > [ ] -1
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > Thanks,
+> > > > > > >>> > > > >
+> > > > > > >>> > > > > Stephen.
+> > > > > > >>> > > >
+> > > > > > >>> > > > ------------------------------
+> > ------------------------------
+> > > > > > >>> ---------
+> > > > > > >>> > > > 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
+> > > > > > >>> >
+> > > > > > >>> > --
+> > > > > > >>> Sent from my phone
+> > > > > > >>>
+> > > > > > >>
+> > > > > > >>
+> > > > > > >
+> > > > >
+> > > > > ------------------------------------------------------------
+> > ---------
+> > > > > 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
+> >
+> >
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 2683C200D14
+ for <ar...@cust-asf2.ponee.io>; Tue, 19 Sep 2017 06:55:16 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 24EF11609DE; Tue, 19 Sep 2017 04:55:16 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id EA4B11609DB
+ for <ar...@cust-asf.ponee.io>; Tue, 19 Sep 2017 06:55:14 +0200 (CEST)
+Received: (qmail 31095 invoked by uid 500); 19 Sep 2017 04:55:13 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 31082 invoked by uid 99); 19 Sep 2017 04:55:13 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2017 04:55:13 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id DAF8E1A31B8
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 04:55:12 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.02
+X-Spam-Level:
+X-Spam-Status: No, score=-0.02 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001,
+ URIBL_BLOCKED=0.001] autolearn=disabled
+Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=KzfUXXaw;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=BoHIo+on
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id cizlmqr8Bxpk for <de...@maven.apache.org>;
+ Tue, 19 Sep 2017 04:55:09 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 377875FD1B
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 04:55:09 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id A3C8420AF7
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 00:55:08 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Tue, 19 Sep 2017 00:55:08 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=RPqtXYj7R+wuZKML3JDsfjyPcME5m
+ 3fk+iSJZBqaaHw=; b=KzfUXXawdWytgPwgPrQKLS+csg+VnT2fUOO05xs6q+JE+
+ r1a1JI+kWXOGQDnov3NNC2nSwWnFI0N1hLZLAgNIX7Y2NvTbdT9X7wtEfMFahAFj
+ 5/jf7GMoQ7ZsA6h6b9UD0ziDC+xsaT81G8vqEGcunSigmxdKRA4fmVp6B0ecFCx6
+ vRd15MLPsOQBxByXQhaROt/tGebqclFVkdoaKAgDs81wUinm7wxwAUq2dduwp3bI
+ atsyQnJS2Jnnr3fH+RjEOyp8CK2ROg6vRlYjlP2sFI2lybz2Odk2oY3zoGc4CHBP
+ rozCMerz8QUiACfi+L2rDzTlmlgllpvsvRmETOOmA==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=RPqtXY
+ j7R+wuZKML3JDsfjyPcME5m3fk+iSJZBqaaHw=; b=BoHIo+onY2n9BB0JfCxpt1
+ fg2S6aXrguLZbCpKJDP9qqerMqn2zDnjE4VdZ5f+ZKAoIhi/97/Gkn9xBnOaLnb6
+ my8JzNATSc8CsinanmRjk0T5jnSeLfAoLBPJkd2flY9la5rl1096J3Nlu/92cpg1
+ /SPgEjD9tsmebOWAoT1HVmWmwSmGyWmEMhh3QIVYIuLrD23t9pvhByO84ENqeYUf
+ EV1iZa6JiEIQHD+bCfh5W1iIWEFW+C5obtJyzLzTSd/SVJ4RpbbK3BgNtiyaoY9f
+ ClEVqNN+1TZ6ATkbNFRV60k/XuMyqcN48ewYVmenMDIVA8TaKS3CDNqpkipwlgFA
+ ==
+X-ME-Sender: <xms:LKPAWdCDYCCgQQog93kxQZvH4zQtMSYYQjPX8SQ6TFL-viKTStAxNQ>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 607056264E; Tue, 19 Sep 2017 00:55:08 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+In-Reply-To: <CA...@mail.gmail.com>
+Date: Tue, 19 Sep 2017 00:55:08 -0400
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+archived-at: Tue, 19 Sep 2017 04:55:16 -0000
+
+TL;DR your test project exposed two existing bugs, one change in
+behaviour and one quirk I can't explain
+
+* Build `<extensions>` are loaded by two classloaders, which is a bug in
+DefaultProjectBuildingHelper#createProjectRealm and explains why you see
+extjar1/extjar2 in the output
+* ClassRealm does not allow same foreign-import from multiple
+classloaders, which is a bug and explains why it is not possible to load
+same resource from multiple plugins/extensions
+* TCCL does not have access to private (i.e. not exported) resources of
+this extensions plugin, which is a change of behaviour introduced by
+mng-6209 fix
+* Also, component injection order appears to be backwards, but maybe
+Stuart can explain why.
+
+
+Below is more detailed explanation of expected and observed behaviour
+
+
+## Component injection depends on the currently running plugin and the
+injection site
+
+Currently running plugins have access to the following component
+implementations:
+
+* Regular plugin has access to components implemented by the plugin,
+project build extensions, if any (via project class realm foreign
+import) and Maven Core.
+* Extension plugin has access to components implemented by the project
+build extensions and Maven Core.
+* Without a running plugin (e.g., during project dependency resolution),
+components implemented by the project build extensions and Maven Core
+are accessible.
+
+Different injection sites have access to the following component
+interfaces:
+
+* Maven Core has access to component interfaces defined by the core
+itself (obviously)
+* Project build extensions have access to **public** component
+interfaces defined by Maven Core and component interfaces defined by the
+build extension itself (there is no way to access component interfaces
+defined in other extensions)
+* Regular plugins have access to **public** component interfaces defined
+by Maven Core, component interfaces **exported** by build extensions and
+component interfaces defined in the plugin itself
+
+For injection to work, injection site has to have access to the
+component interface and the component implementation must be accessible
+through the current context.
+
+>From what I can tell, in your example all plugins have access to the
+right components when using current 3.5.2-SNAPSHOT. The injection order
+does appear to be backwards from what I expected, however.
+
+
+## Resources lookup fully depends on classpath visibility, specifically
+
+* Regular plugin class realm has access to resources from the plugin
+itself, from **exported** packages of the project build extensions and
+**public** Maven Core packages
+* Extensions plugin class realm has access to the resources from the
+extensions plugin itself and from **public** Maven Core packages
+* Project class realm has access to classes and resources **exported**
+by project build extensions and **public** Maven Core packages
+
+I see three problems here
+
+* Maven adds build single-jar `<extensions>` elements directly to
+project class realm **and** creates separate extensions class realms for
+them. Which results in duplicate classes/resources loaded by two
+classloaders and explains why you see extjar1/extjar2 output (which you
+shouldn't according to the explanation above)
+* ClassRealm does not allow foreign-import of the same package from
+multiple classloaders. This makes it impossible to load the same
+resource from multiple plugins/extensions.
+* Extensions plugins cannot access their own private (i.e. not exported)
+resources via TCCL, this is change in behaviour introduced by mng-6209
+fix
+
+Hope this helps
+
+--
+Regards,
+Igor
+
+On Mon, Sep 18, 2017, at 11:46 AM, Stephen Connolly wrote:
+> Oh if only... there is some subtleties going on here.
+>
+> Classes are managed by the "plexus" / "classworlds" stuff, so you cannot
+> override core classes etc.
+>
+> The problem is what extensions are visible and from which classloader
+>
+> On 18 September 2017 at 08:42, Charles Honton <ch...@honton.org> wrote:
+>
+> > From a security perspective, I would expect that core classes can not be
+> > overridden by extensions or plugins. Likewise, extension classes can not
+> > be overridden by plugins.
+> >
+> > Given the use case of defaulting resources, I would expect that the plugin
+> > resources are first, followed by plugin specific extensions, followed by
+> > global extensions, finally core maven. (This allows resources to be
+> > specialized.)
+> >
+> > regards,
+> > chas
+> >
+> > > On Sep 18, 2017, at 3:20 AM, Stephen Connolly <
+> > stephen.alan.connolly@gmail.com> wrote:
+> > >
+> > > Hmmm, so I did some experiments:
+> > >
+> > > If you want to ride along, the experiments are at:
+> > >
+> > > https://github.com/stephenc/mng-6209
+> > >
+> > > So basically I have a plugin that does three different tests:
+> > >
+> > > getLog().info("Injected by @Component:");
+> > > for (Lifecycle l : lifecycles) {
+> > > if (l.getId().startsWith("mng-6209-")) {
+> > > getLog().info(" " + l.getId().substring(9));
+> > > }
+> > > }
+> > > getLog().info("");
+> > > getLog().info("On Plugin Class Loader:");
+> > > try {
+> > > ClassLoader tccl = ListMojo.class.getClassLoader();
+> > > for (URL url :
+> > > Collections.list(tccl.getResources("META-INF/probe.txt"))) {
+> > > InputStream is = url.openStream();
+> > > try {
+> > > getLog().info(" " + IOUtil.toString(is).trim());
+> > > } finally {
+> > > is.close();
+> > > }
+> > > }
+> > > } catch (IOException e) {
+> > > throw new MojoExecutionException(e.getMessage(), e);
+> > > }
+> > > getLog().info("");
+> > > getLog().info("On Thread Context Class Loader:");
+> > > try {
+> > > ClassLoader tccl =
+> > > Thread.currentThread().getContextClassLoader();
+> > > for (URL url :
+> > > Collections.list(tccl.getResources("META-INF/probe.txt"))) {
+> > > InputStream is = url.openStream();
+> > > try {
+> > > getLog().info(" " + IOUtil.toString(is).trim());
+> > > } finally {
+> > > is.close();
+> > > }
+> > > }
+> > > } catch (IOException e) {
+> > > throw new MojoExecutionException(e.getMessage(), e);
+> > > }
+> > >
+> > >
+> > > First off, I hijack the @Component injection with some fake "lifecycles"
+> > to
+> > > see what "plexus" exposes to the plugins.
+> > >
+> > > Second, I look at the resources visible from the plugin's classloader.
+> > >
+> > > Finally, I look at the resources visible from the TCCL.
+> > >
+> > > Here's what 3.5.0 outputs:
+> > >
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin1, plugin2 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe1 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe1 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Only plugin1 extensions. Order: plugin1, plugin2
+> > > 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe2 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe2 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin2, plugin1 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe3 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe3 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin1, plugin2. Extra
+> > dependency
+> > > in plugin1 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe4 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] extjar2
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe4 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > >
+> > > Now if we run with 3.5.1 (which contains the fix for MNG-6209)
+> > >
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin1, plugin2 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe1 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > I would have expected the sequence to be: /build/extensions in pom order
+> > > followed by /build/plugins/plugin[extensions=true] in pom order. This
+> > seems
+> > > to be the reverse order. Is this a bug?
+> > >
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > >
+> > > We haven't changed how the plugin classloader gets instantiated in
+> > > MNG-6209. It seems strange to me that this excludes the
+> > > /build/extensions... on the other hand this could be a side-effect of how
+> > > the classloader gets instantiated (which would mean using the plugin's
+> > > classloader is probably a bad idea, perhaps we need to provide the
+> > ability
+> > > to inject the classloader as a @Component or something)
+> > >
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar1
+> > > [INFO] extjar2
+> > >
+> > > OK, we see the change vs 3.5.0 as this is now the project realm...
+> > though I
+> > > would have expected the project realm to also include the plugins that
+> > were
+> > > marked as extensions...
+> > >
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe1 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar1
+> > > [INFO] extjar2
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Only plugin1 extensions. Order: plugin1, plugin2
+> > > 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe2 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > As expected, given that plugin2 is not an extension here (apart from the
+> > > order being reverse of what I expect)
+> > >
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe2 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > As expected (modulo order) because a plugin should see any self-defined
+> > > extensions. I would expect the order to be plugin2, extjar1, extjar2,
+> > > plugin1 (because the plugin is not an extension, it should have its
+> > > extensions as priority over the project realms's)
+> > >
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > WAT! ok, this I do not understand. Something is wrong somewhere, either
+> > > plugin1's classloader should also include extjar2 and extjar1 or this one
+> > > shouldn't. And since we have extjar1 and extjar2 where is plugin1? (if
+> > the
+> > > inclusion is correct here I expect plugin2, extjar1, extjar2, plugin1 as
+> > a
+> > > plugin that is not an extension plugin should have its own implementation
+> > > first followed then by /build/extensions in pom order and then
+> > > /build/plugins/plugin[extension==true]
+> > >
+> > > This is making no sense at all!
+> > >
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > So TCCL is the plugin classloader here as expected
+> > >
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin2, plugin1 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe3 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > I note that the change in pom order has had no effect on the component
+> > > sequence. This leads me to suspect that plexus has some rule that is
+> > > defining the sequencing... it would be good if we could document that
+> > > somewhere...
+> > >
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe3 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin2
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO] Building Both extensions. Order: plugin1, plugin2. Extra
+> > dependency
+> > > in plugin1 1.0-SNAPSHOT
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > > [INFO]
+> > > [INFO] --- plugin1:1.0-SNAPSHOT:list (default) @ probe4 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > >
+> > > WAT! seems that @Component is somewhat in random order, in this case we
+> > > have modified the dependencies if plugin1 to also include extjar2, the
+> > > order I would expect is:
+> > >
+> > > extjar1, extjar2, plugin1, extjar2, plugin2
+> > >
+> > > Given the previous executions and the fact that changing the sequence of
+> > > plugin1 and plugin2 in the pom did not affect the previous executions, if
+> > > plexus had a deterministic ordering then I would have been somewhat OK
+> > with:
+> > >
+> > > plugin2, plugin1, extjar2, extjar2, extjar1
+> > >
+> > > But this seems to suggest that we have a completely non-deterministic
+> > > ordering... that is not good for reproducible builds...
+> > >
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > >
+> > > Now we see extjar2 but only because it has been explicitly added to the
+> > > plugins dependencies, IMHO it should be here twice, e.g.
+> > >
+> > > extjar1, extjar2, plugin1, extjar2, plugin2
+> > >
+> > > But it seems acceptable if this is instead plugin1, extjar2 (though it
+> > > makes the plugin classloader useless for discovery)
+> > >
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar1
+> > > [INFO] extjar2
+> > > [INFO]
+> > > [INFO] --- plugin2:1.0-SNAPSHOT:list (default) @ probe4 ---
+> > > [INFO] Injected by @Component:
+> > > [INFO] plugin1
+> > > [INFO] extjar2
+> > > [INFO] plugin2
+> > > [INFO] extjar2
+> > > [INFO] extjar1
+> > > [INFO]
+> > > [INFO] On Plugin Class Loader:
+> > > [INFO] plugin2
+> > > [INFO]
+> > > [INFO] On Thread Context Class Loader:
+> > > [INFO] extjar1
+> > > [INFO] extjar2
+> > > [INFO]
+> > > ------------------------------------------------------------------------
+> > >
+> >
+> >
+> > ---------------------------------------------------------------------
+> > 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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 2C725200CF7
+ for <ar...@cust-asf2.ponee.io>; Tue, 19 Sep 2017 22:39:06 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 2AC441609DD; Tue, 19 Sep 2017 20:39:06 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 499EB1609BF
+ for <ar...@cust-asf.ponee.io>; Tue, 19 Sep 2017 22:39:05 +0200 (CEST)
+Received: (qmail 29280 invoked by uid 500); 19 Sep 2017 20:39:04 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 29264 invoked by uid 99); 19 Sep 2017 20:39:03 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2017 20:39:03 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 800CD184A6F
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 20:39:03 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.02
+X-Spam-Level:
+X-Spam-Status: No, score=-0.02 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001,
+ URIBL_BLOCKED=0.001] autolearn=disabled
+Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=1VEkc8+h;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=pRcLHIkZ
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id TZk6vsJVSFUo for <de...@maven.apache.org>;
+ Tue, 19 Sep 2017 20:39:01 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3B4435FE6B
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 20:39:01 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id 3F82320DF9
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 16:39:00 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Tue, 19 Sep 2017 16:39:00 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=BAc9PjeeLNCLeF2IqmDuRfjyy73Vh
+ NS7Pr2l5YzkA9I=; b=1VEkc8+hhorfO0XRoxEuurmMnfcIhcyrHHyZmiSFqcrz0
+ UjCLuDr/ZRSF0+Qi2sxXt1/dItswmGNznkPNa/SrBl84QG120qgcgmxjEHTcUl/5
+ q/b19t9LCFG7Vxpl7kF7Zora15w6Jrpw6FgSGcm9dXtqkZa5jt8uYXOXM8C48Qjp
+ ERilxShoPFsk9yCYWipNtzmFQCnpi3cQln0g27+s5OjLtuvxdA9b4fxuO+KDt+Ve
+ ibx2McbUQsBlgLAmpZVU4NhfhCi9xdbJQvW56n7qOj1Fr28ra/AwONIsufOzCg4y
+ WcPT6IVXouJ7YcIqdhoSMUB8/5CQVf3KuDo0sxAng==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=BAc9Pj
+ eeLNCLeF2IqmDuRfjyy73VhNS7Pr2l5YzkA9I=; b=pRcLHIkZ3ThUGdsETm1RfG
+ uRjWvfN7rLib2zokp4yrWSH7EA6o+YIv5g+PDwXBVSGYScHzRAMaBcY7u9XPvn37
+ 25GXiPf5igKTFToeSEmrauYriU75849XK2gTIuIfL3uLwk5gmUGGMz22Tc7opjly
+ hAqFPVnFg6RD9H6b6TZ6Iqi0LvfjMMUaYrqND7r9jrxHJvkr+n7dNeHSddasP0rJ
+ xN0aS0cYXT1Fkb7TZay1XylNZqK5w2vI+MeeIVGY/2nyJ5W0+DS7CYcNzmDazzpP
+ 7QlbVxaU0WaOzUvOp4SaHVig+Cm/xqafpDUnfl8UkMScwa2iT15x6DO/TDSe+9pQ
+ ==
+X-ME-Sender: <xms:ZIDBWXgbfu7PyPgbk7pZSJyHprNR6ZEziXkC40I6Qeq1ZD2YjC0DKw>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 18E706264E; Tue, 19 Sep 2017 16:39:00 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+In-Reply-To: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+Date: Tue, 19 Sep 2017 16:39:00 -0400
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+archived-at: Tue, 19 Sep 2017 20:39:06 -0000
+
+Just to confirm I understand what we are trying to establish here. We
+want to decide the expected/desired component injection behaviour and
+classpath visibility in the absence of package and artifact export
+configuration (i.e. META-INF/maven/extension.xml file). Did I get this
+right?
+
+--
+Regards,
+Igor
+
+On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> Let's do it like this:
+> https://cwiki.apache.org/confluence/download/attachments/2329841/classrealms.pdf?api=v2
+>
+> Robert
+>
+> On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> <st...@gmail.com> wrote:
+>
+> > I think you will need a link to the PDF as attachments are stripped from
+> > the ML
+> >
+> > On Tue 19 Sep 2017 at 19:57, Robert Scholte <rf...@apache.org> wrote:
+> >
+> >> Attached a single page overview.
+> >>
+> >> Per block you'll see in the upper left corner the executed plugin
+> >> The left column contains the extensions and plugin in orderas specified
+> >> in
+> >> the pom.xml
+> >> In every classloadercolumn you'll see numbers which represent the order.
+> >>
+> >> I hope I didn't make any mistakes.
+> >> Tomorrow I have enough time to see if I understand what's happening
+> >> here.
+> >>
+> >> I will come back with my conclusions.
+> >>
+> >> Robert
+> >>
+> >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <ig...@ifedorenko.com>
+> >> wrote:
+> >>
+> >> > TL;DR your test project exposed two existing bugs, one change in
+> >> > behaviour and one quirk I can't explain
+> >> >
+> >> > * Build `<extensions>` are loaded by two classloaders, which is a bug
+> >> in
+> >> > DefaultProjectBuildingHelper#createProjectRealm and explains why you
+> >> see
+> >> > extjar1/extjar2 in the output
+> >> > * ClassRealm does not allow same foreign-import from multiple
+> >> > classloaders, which is a bug and explains why it is not possible to
+> >> load
+> >> > same resource from multiple plugins/extensions
+> >> > * TCCL does not have access to private (i.e. not exported) resources
+> >> of
+> >> > this extensions plugin, which is a change of behaviour introduced by
+> >> > mng-6209 fix
+> >> > * Also, component injection order appears to be backwards, but maybe
+> >> > Stuart can explain why.
+> >> >
+> >> >
+> >> > Below is more detailed explanation of expected and observed behaviour
+> >> >
+> >> >
+> >> > ## Component injection depends on the currently running plugin and the
+> >> > injection site
+> >> >
+> >> > Currently running plugins have access to the following component
+> >> > implementations:
+> >> >
+> >> > * Regular plugin has access to components implemented by the plugin,
+> >> > project build extensions, if any (via project class realm foreign
+> >> > import) and Maven Core.
+> >> > * Extension plugin has access to components implemented by the project
+> >> > build extensions and Maven Core.
+> >> > * Without a running plugin (e.g., during project dependency
+> >> resolution),
+> >> > components implemented by the project build extensions and Maven Core
+> >> > are accessible.
+> >> >
+> >> > Different injection sites have access to the following component
+> >> > interfaces:
+> >> >
+> >> > * Maven Core has access to component interfaces defined by the core
+> >> > itself (obviously)
+> >> > * Project build extensions have access to **public** component
+> >> > interfaces defined by Maven Core and component interfaces defined by
+> >> the
+> >> > build extension itself (there is no way to access component interfaces
+> >> > defined in other extensions)
+> >> > * Regular plugins have access to **public** component interfaces
+> >> defined
+> >> > by Maven Core, component interfaces **exported** by build extensions
+> >> and
+> >> > component interfaces defined in the plugin itself
+> >> >
+> >> > For injection to work, injection site has to have access to the
+> >> > component interface and the component implementation must be
+> >> accessible
+> >> > through the current context.
+> >> >
+> >> > From what I can tell, in your example all plugins have access to the
+> >> > right components when using current 3.5.2-SNAPSHOT. The injection
+> >> order
+> >> > does appear to be backwards from what I expected, however.
+> >> >
+> >> >
+> >> > ## Resources lookup fully depends on classpath visibility,
+> >> specifically
+> >> >
+> >> > * Regular plugin class realm has access to resources from the plugin
+> >> > itself, from **exported** packages of the project build extensions and
+> >> > **public** Maven Core packages
+> >> > * Extensions plugin class realm has access to the resources from the
+> >> > extensions plugin itself and from **public** Maven Core packages
+> >> > * Project class realm has access to classes and resources **exported**
+> >> > by project build extensions and **public** Maven Core packages
+> >> >
+> >> > I see three problems here
+> >> >
+> >> > * Maven adds build single-jar `<extensions>` elements directly to
+> >> > project class realm **and** creates separate extensions class realms
+> >> for
+> >> > them. Which results in duplicate classes/resources loaded by two
+> >> > classloaders and explains why you see extjar1/extjar2 output (which
+> >> you
+> >> > shouldn't according to the explanation above)
+> >> > * ClassRealm does not allow foreign-import of the same package from
+> >> > multiple classloaders. This makes it impossible to load the same
+> >> > resource from multiple plugins/extensions.
+> >> > * Extensions plugins cannot access their own private (i.e. not
+> >> exported)
+> >> > resources via TCCL, this is change in behaviour introduced by mng-6209
+> >> > fix
+> >> >
+> >> > Hope this helps
+> >>
+> >> ---------------------------------------------------------------------
+> >> 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
+>
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 70D1C200D0A
+ for <ar...@cust-asf2.ponee.io>; Wed, 20 Sep 2017 02:29:40 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 6EFE61609E0; Wed, 20 Sep 2017 00:29:40 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 8C6CE1609DD
+ for <ar...@cust-asf.ponee.io>; Wed, 20 Sep 2017 02:29:39 +0200 (CEST)
+Received: (qmail 91096 invoked by uid 500); 20 Sep 2017 00:29:38 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 91081 invoked by uid 99); 20 Sep 2017 00:29:38 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2017 00:29:38 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CCDE0CD528
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 00:29:37 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd1-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=BIk1lLge;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=MYQcGkWr
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id yyRavHno3WXj for <de...@maven.apache.org>;
+ Wed, 20 Sep 2017 00:29:35 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id BF46D5F659
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 00:29:34 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id 4630A20D96
+ for <de...@maven.apache.org>; Tue, 19 Sep 2017 20:29:34 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Tue, 19 Sep 2017 20:29:34 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=S1M3WhIrpDs6Swjubr0CclyiYMuft
+ lAjdX566pU+qTg=; b=BIk1lLgePm9M4VQzzoD7ETezp0tE83LyOnXY9uK5JqYCF
+ cf0B+mrCPThTmdcivB+3TQPvOubhkAyEUw4sIv3dKx6TngIxqY6AY9Q4RZoEqOZy
+ xlvYMZfvnwq71/+egFqZD0N+uYkXTpkiMLqdH5YR4rAPmeqJ4mx6goYsm1aqp4sg
+ tdFafxMBkWWEIBjaTwrreQOZd0Z4r4gaEhPEbTxXBdYfUeCKlsKc+jml1OephknF
+ 2D6d+rufGGoYVRAPgx+bbH5tiIOlUqGj/lCwh6Trr9GBSprSwPm9LTDD5p8c1VLs
+ 0dPoN67AathJoc3a/tPPgIYo5VRq6s1MvPe/WX2iA==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=S1M3Wh
+ IrpDs6Swjubr0CclyiYMuftlAjdX566pU+qTg=; b=MYQcGkWr4wWwz81YuPbaN+
+ RYL/7cbF3iI9nCNB7pU0bisJUBNpUxbuAmtO4mRd4AEooVPWqkuqXjE8Qo3nNgxi
+ AgM/Di2i073rNe97ytcVfQGzDrJ9nuhsZwixPlcrg+5UnxuRJ9BqBtwkyOf9CD0a
+ tgzp3TUGPFmQlaCMlmbguTjTyub7D/pnFcnAgWuTPJyCHqE2o7Q9bZbvh+tebtYq
+ xSM9A7ePiLiaUybnLtxdsz5ZZ9E+n7BhVNwSmZHIdRCUgITrNe4Ln3B0Y3M5zmoA
+ 5IVa3OoceegCjATe2day43oAhVdjJPqWPmKQWuB2bHpUFOTJnkgG7//b5UyRKYSA
+ ==
+X-ME-Sender: <xms:brbBWZj4QmX5EwYULKe6w35HyWiJF2ARfYkBKJzq8-7qdPrB8Y1DqA>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 171EE6264E; Tue, 19 Sep 2017 20:29:34 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+In-Reply-To: <CA...@mail.gmail.com>
+Date: Tue, 19 Sep 2017 20:29:34 -0400
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+archived-at: Wed, 20 Sep 2017 00:29:40 -0000
+
+In that case, can I suggest couple of changes to the test project
+
+* I thinks it makes more sense to configure extjar1 and extjar2 as
+extensions <plugin> elements in probleN pom.xml files. First, there is
+no meaningful order between <extensions> and <plugins> elements. More
+importantly, though, simple <extensions> are treated in special
+maven2-compat mode and are not representative of likely real-world
+extensions.
+
+* I think we should introduce META-INF/maven/extension.xml to the test
+extensions. This metadata what introduced to configure classpath
+visibility, so lets use it.
+
+--
+Regards,
+Igor
+
+On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> Yes, the expectations are key. Depending on what they are we may either
+> drop 3.5.1 or go ahead as it depends on whether this is more correct than
+> 3.5.0 or swapping one fix for a bug
+>
+> On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <ig...@ifedorenko.com> wrote:
+>
+> > Just to confirm I understand what we are trying to establish here. We
+> > want to decide the expected/desired component injection behaviour and
+> > classpath visibility in the absence of package and artifact export
+> > configuration (i.e. META-INF/maven/extension.xml file). Did I get this
+> > right?
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> > > Let's do it like this:
+> > >
+> > https://cwiki.apache.org/confluence/download/attachments/2329841/classrealms.pdf?api=v2
+> > >
+> > > Robert
+> > >
+> > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> > > <st...@gmail.com> wrote:
+> > >
+> > > > I think you will need a link to the PDF as attachments are stripped
+> > from
+> > > > the ML
+> > > >
+> > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte <rf...@apache.org>
+> > wrote:
+> > > >
+> > > >> Attached a single page overview.
+> > > >>
+> > > >> Per block you'll see in the upper left corner the executed plugin
+> > > >> The left column contains the extensions and plugin in orderas
+> > specified
+> > > >> in
+> > > >> the pom.xml
+> > > >> In every classloadercolumn you'll see numbers which represent the
+> > order.
+> > > >>
+> > > >> I hope I didn't make any mistakes.
+> > > >> Tomorrow I have enough time to see if I understand what's happening
+> > > >> here.
+> > > >>
+> > > >> I will come back with my conclusions.
+> > > >>
+> > > >> Robert
+> > > >>
+> > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <
+> > igor@ifedorenko.com>
+> > > >> wrote:
+> > > >>
+> > > >> > TL;DR your test project exposed two existing bugs, one change in
+> > > >> > behaviour and one quirk I can't explain
+> > > >> >
+> > > >> > * Build `<extensions>` are loaded by two classloaders, which is a
+> > bug
+> > > >> in
+> > > >> > DefaultProjectBuildingHelper#createProjectRealm and explains why you
+> > > >> see
+> > > >> > extjar1/extjar2 in the output
+> > > >> > * ClassRealm does not allow same foreign-import from multiple
+> > > >> > classloaders, which is a bug and explains why it is not possible to
+> > > >> load
+> > > >> > same resource from multiple plugins/extensions
+> > > >> > * TCCL does not have access to private (i.e. not exported) resources
+> > > >> of
+> > > >> > this extensions plugin, which is a change of behaviour introduced by
+> > > >> > mng-6209 fix
+> > > >> > * Also, component injection order appears to be backwards, but maybe
+> > > >> > Stuart can explain why.
+> > > >> >
+> > > >> >
+> > > >> > Below is more detailed explanation of expected and observed
+> > behaviour
+> > > >> >
+> > > >> >
+> > > >> > ## Component injection depends on the currently running plugin and
+> > the
+> > > >> > injection site
+> > > >> >
+> > > >> > Currently running plugins have access to the following component
+> > > >> > implementations:
+> > > >> >
+> > > >> > * Regular plugin has access to components implemented by the plugin,
+> > > >> > project build extensions, if any (via project class realm foreign
+> > > >> > import) and Maven Core.
+> > > >> > * Extension plugin has access to components implemented by the
+> > project
+> > > >> > build extensions and Maven Core.
+> > > >> > * Without a running plugin (e.g., during project dependency
+> > > >> resolution),
+> > > >> > components implemented by the project build extensions and Maven
+> > Core
+> > > >> > are accessible.
+> > > >> >
+> > > >> > Different injection sites have access to the following component
+> > > >> > interfaces:
+> > > >> >
+> > > >> > * Maven Core has access to component interfaces defined by the core
+> > > >> > itself (obviously)
+> > > >> > * Project build extensions have access to **public** component
+> > > >> > interfaces defined by Maven Core and component interfaces defined by
+> > > >> the
+> > > >> > build extension itself (there is no way to access component
+> > interfaces
+> > > >> > defined in other extensions)
+> > > >> > * Regular plugins have access to **public** component interfaces
+> > > >> defined
+> > > >> > by Maven Core, component interfaces **exported** by build extensions
+> > > >> and
+> > > >> > component interfaces defined in the plugin itself
+> > > >> >
+> > > >> > For injection to work, injection site has to have access to the
+> > > >> > component interface and the component implementation must be
+> > > >> accessible
+> > > >> > through the current context.
+> > > >> >
+> > > >> > From what I can tell, in your example all plugins have access to the
+> > > >> > right components when using current 3.5.2-SNAPSHOT. The injection
+> > > >> order
+> > > >> > does appear to be backwards from what I expected, however.
+> > > >> >
+> > > >> >
+> > > >> > ## Resources lookup fully depends on classpath visibility,
+> > > >> specifically
+> > > >> >
+> > > >> > * Regular plugin class realm has access to resources from the plugin
+> > > >> > itself, from **exported** packages of the project build extensions
+> > and
+> > > >> > **public** Maven Core packages
+> > > >> > * Extensions plugin class realm has access to the resources from the
+> > > >> > extensions plugin itself and from **public** Maven Core packages
+> > > >> > * Project class realm has access to classes and resources
+> > **exported**
+> > > >> > by project build extensions and **public** Maven Core packages
+> > > >> >
+> > > >> > I see three problems here
+> > > >> >
+> > > >> > * Maven adds build single-jar `<extensions>` elements directly to
+> > > >> > project class realm **and** creates separate extensions class realms
+> > > >> for
+> > > >> > them. Which results in duplicate classes/resources loaded by two
+> > > >> > classloaders and explains why you see extjar1/extjar2 output (which
+> > > >> you
+> > > >> > shouldn't according to the explanation above)
+> > > >> > * ClassRealm does not allow foreign-import of the same package from
+> > > >> > multiple classloaders. This makes it impossible to load the same
+> > > >> > resource from multiple plugins/extensions.
+> > > >> > * Extensions plugins cannot access their own private (i.e. not
+> > > >> exported)
+> > > >> > resources via TCCL, this is change in behaviour introduced by
+> > mng-6209
+> > > >> > fix
+> > > >> >
+> > > >> > Hope this helps
+> > > >>
+> > > >> ---------------------------------------------------------------------
+> > > >> 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
+> > >
+> >
+> > ---------------------------------------------------------------------
+> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > For additional commands, e-mail: dev-help@maven.apache.org
+> >
+> > --
+> Sent from my phone
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 34D6E200D0C
+ for <ar...@cust-asf2.ponee.io>; Wed, 20 Sep 2017 13:31:55 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 336051609E2; Wed, 20 Sep 2017 11:31:55 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 214191609E1
+ for <ar...@cust-asf.ponee.io>; Wed, 20 Sep 2017 13:31:53 +0200 (CEST)
+Received: (qmail 37418 invoked by uid 500); 20 Sep 2017 11:31:53 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 37361 invoked by uid 99); 20 Sep 2017 11:31:52 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2017 11:31:52 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 49A48D2155
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 11:31:52 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd1-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=aSYqoBs3;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=Yx0wOq3m
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id KAHX4dyD5KTl for <de...@maven.apache.org>;
+ Wed, 20 Sep 2017 11:31:50 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 6D6F85FC69
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 11:31:50 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id B583E20D40
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 07:31:44 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Wed, 20 Sep 2017 07:31:44 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=09mxRytprmxSYBcfR/sokuD95FIly
+ Baj5/GaUWnv3o0=; b=aSYqoBs3aNAUCqef2sR/ZhbPZE56WWQnaEGrnViI2JaT1
+ GQFad6xfRNjHuX11JSMKp3xkiEI2pFl84yyh9iuFW7Ybsobz5Faud2B3q8IcliPC
+ 3w5wBhZI8a4AYwhyv+ktv8W/7DG6oBsjRDqyVRSc3wArdQWzXDhBGtQmZsxnHkze
+ /WTMRHcfTJodsc/GOdqZhXnAoL6QGGWp7RbnqKRgV16JtLjzMTboSyiOOHduNANB
+ 5uNGCMaLt+AXnoqnZxlhyZxx0RJg5DsvKZm8dw3jgJJy84yZW7rE8lznn0UPtfDo
+ JRV4O59F+gC26hpHbIVTF/lj7Y6ZRIHmkoy48jvww==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=09mxRy
+ tprmxSYBcfR/sokuD95FIlyBaj5/GaUWnv3o0=; b=Yx0wOq3mHPvjJsT2vm+YyS
+ Z3YGc5q5/k1C1r9bDaI81tTBcTgZ8lWYH/C4ZfCKzdHreM65krkXyb7cMPyan3+p
+ wcjhAyYgR7yi5tf2mVVv3n47EtHxfRGpRA3rYPCO4SqIjhxHgYVlUVv/hAJKN/5T
+ wA86IycTy8PBZ7LC4EQ1O942V4Z3NLRrTFTKU+3UhjKJV4zl18HeU/nXhwwor9ls
+ C+cPHFQv1/5ME8BVxOhzbZGb1r438vdAHDfnDRo5PPUHmvQQPyTbg3iu704VIzF/
+ X2Z/ne+r8/9gjKeFUvgSaFXkTKIxBDM5Di9r/GQhZYgMPlxpGDHerbD+d1RbYMwg
+ ==
+X-ME-Sender: <xms:oFHCWXXgkRzOYR4wZgvgkNXWkGxB35taiU-V0iw2DzD7NweHHgdBhg>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 872266264E; Wed, 20 Sep 2017 07:31:44 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+In-Reply-To: <CA...@mail.gmail.com>
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+Date: Wed, 20 Sep 2017 07:31:44 -0400
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+archived-at: Wed, 20 Sep 2017 11:31:55 -0000
+
+Just to be clear, while I agree the documentation is lacking, neither
+special-casing "simple" <extensions> nor META-INF/maven/extension.xml=20
+is new behaviour in 3.5.1, both existed since 3.0 alphas iirc. Also,
+Herv=C3=A9 did add some extension.xml documentation couple of years ago.
+
+https://issues.apache.org/jira/browse/MNG-4381
+
+--=20
+Regards,
+Igor
+
+On Wed, Sep 20, 2017, at 03:12 AM, Stephen Connolly wrote:
+> On Wed 20 Sep 2017 at 01:29, Igor Fedorenko <ig...@ifedorenko.com> wrote:
+>=20
+> > In that case, can I suggest couple of changes to the test project
+> >
+> > * I thinks it makes more sense to configure extjar1 and extjar2 as
+> > extensions <plugin> elements in probleN pom.xml files. First, there is
+> > no meaningful order between <extensions> and <plugins> elements. More
+> > importantly, though, simple <extensions> are treated in special
+> > maven2-compat mode and are not representative of likely real-world
+> > extensions.
+>=20
+>=20
+> That sounds like we need documentation updated then. None of that is
+> obvious to me.
+>=20
+>=20
+> >
+> > * I think we should introduce META-INF/maven/extension.xml to the test
+> > extensions. This metadata what introduced to configure classpath
+> > visibility, so lets use it.
+>=20
+>=20
+> Again, not obvious to me, if that file allows control of classpath
+> visibility then it may be that the only issue *with* 3.5.1 is the lack of
+> documentation... now previous versions would have been adding breaking
+> changes from my PoV but that is the past and should not affect the 3.5.1
+> release.
+>=20
+> PRs for the probe project welcome. I am happy to try and write docs once
+> I
+> have an understanding of what the expected behaviours are
+>=20
+>=20
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> > On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> > > Yes, the expectations are key. Depending on what they are we may eith=
+er
+> > > drop 3.5.1 or go ahead as it depends on whether this is more correct =
+than
+> > > 3.5.0 or swapping one fix for a bug
+> > >
+> > > On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <ig...@ifedorenko.com> wro=
+te:
+> > >
+> > > > Just to confirm I understand what we are trying to establish here. =
+We
+> > > > want to decide the expected/desired component injection behaviour a=
+nd
+> > > > classpath visibility in the absence of package and artifact export
+> > > > configuration (i.e. META-INF/maven/extension.xml file). Did I get t=
+his
+> > > > right?
+> > > >
+> > > > --
+> > > > Regards,
+> > > > Igor
+> > > >
+> > > > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> > > > > Let's do it like this:
+> > > > >
+> > > >
+> > https://cwiki.apache.org/confluence/download/attachments/2329841/classr=
+ealms.pdf?api=3Dv2
+> > > > >
+> > > > > Robert
+> > > > >
+> > > > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> > > > > <st...@gmail.com> wrote:
+> > > > >
+> > > > > > I think you will need a link to the PDF as attachments are stri=
+pped
+> > > > from
+> > > > > > the ML
+> > > > > >
+> > > > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte <rfscholte@apache.o=
+rg>
+> > > > wrote:
+> > > > > >
+> > > > > >> Attached a single page overview.
+> > > > > >>
+> > > > > >> Per block you'll see in the upper left corner the executed plu=
+gin
+> > > > > >> The left column contains the extensions and plugin in orderas
+> > > > specified
+> > > > > >> in
+> > > > > >> the pom.xml
+> > > > > >> In every classloadercolumn you'll see numbers which represent =
+the
+> > > > order.
+> > > > > >>
+> > > > > >> I hope I didn't make any mistakes.
+> > > > > >> Tomorrow I have enough time to see if I understand what's
+> > happening
+> > > > > >> here.
+> > > > > >>
+> > > > > >> I will come back with my conclusions.
+> > > > > >>
+> > > > > >> Robert
+> > > > > >>
+> > > > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <
+> > > > igor@ifedorenko.com>
+> > > > > >> wrote:
+> > > > > >>
+> > > > > >> > TL;DR your test project exposed two existing bugs, one chang=
+e in
+> > > > > >> > behaviour and one quirk I can't explain
+> > > > > >> >
+> > > > > >> > * Build `<extensions>` are loaded by two classloaders, which=
+ is
+> > a
+> > > > bug
+> > > > > >> in
+> > > > > >> > DefaultProjectBuildingHelper#createProjectRealm and explains
+> > why you
+> > > > > >> see
+> > > > > >> > extjar1/extjar2 in the output
+> > > > > >> > * ClassRealm does not allow same foreign-import from multiple
+> > > > > >> > classloaders, which is a bug and explains why it is not
+> > possible to
+> > > > > >> load
+> > > > > >> > same resource from multiple plugins/extensions
+> > > > > >> > * TCCL does not have access to private (i.e. not exported)
+> > resources
+> > > > > >> of
+> > > > > >> > this extensions plugin, which is a change of behaviour
+> > introduced by
+> > > > > >> > mng-6209 fix
+> > > > > >> > * Also, component injection order appears to be backwards, b=
+ut
+> > maybe
+> > > > > >> > Stuart can explain why.
+> > > > > >> >
+> > > > > >> >
+> > > > > >> > Below is more detailed explanation of expected and observed
+> > > > behaviour
+> > > > > >> >
+> > > > > >> >
+> > > > > >> > ## Component injection depends on the currently running plug=
+in
+> > and
+> > > > the
+> > > > > >> > injection site
+> > > > > >> >
+> > > > > >> > Currently running plugins have access to the following compo=
+nent
+> > > > > >> > implementations:
+> > > > > >> >
+> > > > > >> > * Regular plugin has access to components implemented by the
+> > plugin,
+> > > > > >> > project build extensions, if any (via project class realm
+> > foreign
+> > > > > >> > import) and Maven Core.
+> > > > > >> > * Extension plugin has access to components implemented by t=
+he
+> > > > project
+> > > > > >> > build extensions and Maven Core.
+> > > > > >> > * Without a running plugin (e.g., during project dependency
+> > > > > >> resolution),
+> > > > > >> > components implemented by the project build extensions and M=
+aven
+> > > > Core
+> > > > > >> > are accessible.
+> > > > > >> >
+> > > > > >> > Different injection sites have access to the following compo=
+nent
+> > > > > >> > interfaces:
+> > > > > >> >
+> > > > > >> > * Maven Core has access to component interfaces defined by t=
+he
+> > core
+> > > > > >> > itself (obviously)
+> > > > > >> > * Project build extensions have access to **public** compone=
+nt
+> > > > > >> > interfaces defined by Maven Core and component interfaces
+> > defined by
+> > > > > >> the
+> > > > > >> > build extension itself (there is no way to access component
+> > > > interfaces
+> > > > > >> > defined in other extensions)
+> > > > > >> > * Regular plugins have access to **public** component interf=
+aces
+> > > > > >> defined
+> > > > > >> > by Maven Core, component interfaces **exported** by build
+> > extensions
+> > > > > >> and
+> > > > > >> > component interfaces defined in the plugin itself
+> > > > > >> >
+> > > > > >> > For injection to work, injection site has to have access to =
+the
+> > > > > >> > component interface and the component implementation must be
+> > > > > >> accessible
+> > > > > >> > through the current context.
+> > > > > >> >
+> > > > > >> > From what I can tell, in your example all plugins have access
+> > to the
+> > > > > >> > right components when using current 3.5.2-SNAPSHOT. The
+> > injection
+> > > > > >> order
+> > > > > >> > does appear to be backwards from what I expected, however.
+> > > > > >> >
+> > > > > >> >
+> > > > > >> > ## Resources lookup fully depends on classpath visibility,
+> > > > > >> specifically
+> > > > > >> >
+> > > > > >> > * Regular plugin class realm has access to resources from the
+> > plugin
+> > > > > >> > itself, from **exported** packages of the project build
+> > extensions
+> > > > and
+> > > > > >> > **public** Maven Core packages
+> > > > > >> > * Extensions plugin class realm has access to the resources
+> > from the
+> > > > > >> > extensions plugin itself and from **public** Maven Core pack=
+ages
+> > > > > >> > * Project class realm has access to classes and resources
+> > > > **exported**
+> > > > > >> > by project build extensions and **public** Maven Core packag=
+es
+> > > > > >> >
+> > > > > >> > I see three problems here
+> > > > > >> >
+> > > > > >> > * Maven adds build single-jar `<extensions>` elements direct=
+ly
+> > to
+> > > > > >> > project class realm **and** creates separate extensions class
+> > realms
+> > > > > >> for
+> > > > > >> > them. Which results in duplicate classes/resources loaded by=
+ two
+> > > > > >> > classloaders and explains why you see extjar1/extjar2 output
+> > (which
+> > > > > >> you
+> > > > > >> > shouldn't according to the explanation above)
+> > > > > >> > * ClassRealm does not allow foreign-import of the same packa=
+ge
+> > from
+> > > > > >> > multiple classloaders. This makes it impossible to load the =
+same
+> > > > > >> > resource from multiple plugins/extensions.
+> > > > > >> > * Extensions plugins cannot access their own private (i.e. n=
+ot
+> > > > > >> exported)
+> > > > > >> > resources via TCCL, this is change in behaviour introduced by
+> > > > mng-6209
+> > > > > >> > fix
+> > > > > >> >
+> > > > > >> > Hope this helps
+> > > > > >>
+> > > > > >>
+> > ---------------------------------------------------------------------
+> > > > > >> 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
+> > > > >
+> > > >
+> > > > -------------------------------------------------------------------=
+--
+> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > >
+> > > > --
+> > > Sent from my phone
+> >
+> > ---------------------------------------------------------------------
+> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > For additional commands, e-mail: dev-help@maven.apache.org
+> >
+> > --
+> Sent from my phone
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 721C7200D15
+ for <ar...@cust-asf2.ponee.io>; Wed, 20 Sep 2017 13:44:59 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 70BE81609E2; Wed, 20 Sep 2017 11:44:59 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 46A651609E1
+ for <ar...@cust-asf.ponee.io>; Wed, 20 Sep 2017 13:44:58 +0200 (CEST)
+Received: (qmail 69104 invoked by uid 500); 20 Sep 2017 11:44:57 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 69090 invoked by uid 99); 20 Sep 2017 11:44:56 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2017 11:44:56 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6A0741A0DC3
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 11:44:56 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=HcjL0PUw;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=rIMFPvBy
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id LQGvwbAFfOlg for <de...@maven.apache.org>;
+ Wed, 20 Sep 2017 11:44:54 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9C33E60D90
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 11:44:53 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id CDE6A20B87
+ for <de...@maven.apache.org>; Wed, 20 Sep 2017 07:44:52 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Wed, 20 Sep 2017 07:44:52 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=rrx2rOFrFQjCjcZSk0T49vA8CXNES
+ zSHxrYxlo4BbOs=; b=HcjL0PUw/8EFsm1vNzeblaDcmn7dlXcf8avbIEvIQQUQp
+ KCGKzh/R2tm1zvjfD2/EliHUwO/boudC8bQk9U1mN8kNvQpQl5GCxs5vuqZtzujc
+ /XMWd/2NCe7GEYKslHUOUr9aCGZnShWvQJYEa93eS0yj7FvIyEV5p0w5QGCViwC8
+ C37HjoiZJ6LL/DqSIwij68KtpJ62PrW+OQKubosA08iGjcJsPbs9kSe3+4sk2oKq
+ xwgl11SUeAG5XxekTpZYxpAIjOvjdnnE4+9vWp8r56bK7dYAu2kr3pyuc0TW+UmA
+ JpVgvMRK9pV5fXr0f6HeuUm190j8mHRGzUlAt3bWQ==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rrx2rO
+ FrFQjCjcZSk0T49vA8CXNESzSHxrYxlo4BbOs=; b=rIMFPvBy3UaLXFlRw+TXm4
+ zCTsUs0yEKNCPCL+s1a8G3pK53/EwMwccgu6z6lIftkx6UGtPLWz88NDMZsc9li4
+ 0DMAAwDSKHhHbWLV//4WaG7/GbOIW1D1spk+7ZL6MicZuszHNl37tBQxpPAcCMaL
+ RPazzDN5OAKO8EYPhTfEuf2jTDUv2Ybj5F3vqL9bELDFtgrobA2J7LahJ862fPwI
+ w9DMcZSRGJpddn/Ou0tc/PuNI3bt8jQh06jWI+Rn0fUyyFYkrDoPqlTZUguzLYAF
+ MRGBiGAAkONOMx/bqagTyH6pawle0n1YYvi8Q1WiZESDpvS4o8tFsRuTtGUcFlFg
+ ==
+X-ME-Sender: <xms:tFTCWTklC1lBNSEEWRLjxkQGgXs7g810r4rUYhd5KAE4u6Oxc3m0TA>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 981746264E; Wed, 20 Sep 2017 07:44:52 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Date: Wed, 20 Sep 2017 07:44:52 -0400
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+In-Reply-To: <op...@desktop-2khsk44.dynamic.ziggo.nl>
+archived-at: Wed, 20 Sep 2017 11:44:59 -0000
+
+Real-world scm or wagon <extensions> won't trigger maven2-compat code
+path [1]. To avoid that obscure code path we can either make the test
+more elaborate (i.e. add dependencies to extjar1/extjar2) or we can use
+extensions <plugin>. Either way I don't think we should spend time on
+the code path unlikely to be used in real life.
+
+[1]
+https://github.com/apache/maven/blob/maven-3.5.1/maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuildingHelper.java#L210-L219
+
+--
+Regards,
+Igor
+
+On Wed, Sep 20, 2017, at 03:29 AM, Robert Scholte wrote:
+> On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly
+> <st...@gmail.com> wrote:
+>
+> > On Wed 20 Sep 2017 at 01:29, Igor Fedorenko <ig...@ifedorenko.com> wrote:
+> >
+> >> In that case, can I suggest couple of changes to the test project
+> >>
+> >> * I thinks it makes more sense to configure extjar1 and extjar2 as
+> >> extensions <plugin> elements in probleN pom.xml files. First, there is
+> >> no meaningful order between <extensions> and <plugins> elements. More
+> >> importantly, though, simple <extensions> are treated in special
+> >> maven2-compat mode and are not representative of likely real-world
+> >> extensions.
+> >
+>
+> Not sure I agree with this. I think there are jars worth sharing across
+> multiple plugins, but where making the plugin an extension is a bit
+> weird.
+> I'm thinking of scm and wagon in this case.
+>
+> >
+> > That sounds like we need documentation updated then. None of that is
+> > obvious to me.
+> >
+> >
+> >>
+> >> * I think we should introduce META-INF/maven/extension.xml to the test
+> >> extensions. This metadata what introduced to configure classpath
+> >> visibility, so lets use it.
+> >
+> >
+> > Again, not obvious to me, if that file allows control of classpath
+> > visibility then it may be that the only issue *with* 3.5.1 is the lack of
+> > documentation... now previous versions would have been adding breaking
+> > changes from my PoV but that is the past and should not affect the 3.5.1
+> > release.
+> >
+> > PRs for the probe project welcome. I am happy to try and write docs once
+> > I
+> > have an understanding of what the expected behaviours are
+> >
+> >
+> >>
+> >> --
+> >> Regards,
+> >> Igor
+> >>
+> >> On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> >> > Yes, the expectations are key. Depending on what they are we may
+> >> either
+> >> > drop 3.5.1 or go ahead as it depends on whether this is more correct
+> >> than
+> >> > 3.5.0 or swapping one fix for a bug
+> >> >
+> >> > On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <ig...@ifedorenko.com>
+> >> wrote:
+> >> >
+> >> > > Just to confirm I understand what we are trying to establish here.
+> >> We
+> >> > > want to decide the expected/desired component injection behaviour
+> >> and
+> >> > > classpath visibility in the absence of package and artifact export
+> >> > > configuration (i.e. META-INF/maven/extension.xml file). Did I get
+> >> this
+> >> > > right?
+> >> > >
+> >> > > --
+> >> > > Regards,
+> >> > > Igor
+> >> > >
+> >> > > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> >> > > > Let's do it like this:
+> >> > > >
+> >> > >
+> >> https://cwiki.apache.org/confluence/download/attachments/2329841/classrealms.pdf?api=v2
+> >> > > >
+> >> > > > Robert
+> >> > > >
+> >> > > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> >> > > > <st...@gmail.com> wrote:
+> >> > > >
+> >> > > > > I think you will need a link to the PDF as attachments are
+> >> stripped
+> >> > > from
+> >> > > > > the ML
+> >> > > > >
+> >> > > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte
+> >> <rf...@apache.org>
+> >> > > wrote:
+> >> > > > >
+> >> > > > >> Attached a single page overview.
+> >> > > > >>
+> >> > > > >> Per block you'll see in the upper left corner the executed
+> >> plugin
+> >> > > > >> The left column contains the extensions and plugin in orderas
+> >> > > specified
+> >> > > > >> in
+> >> > > > >> the pom.xml
+> >> > > > >> In every classloadercolumn you'll see numbers which represent
+> >> the
+> >> > > order.
+> >> > > > >>
+> >> > > > >> I hope I didn't make any mistakes.
+> >> > > > >> Tomorrow I have enough time to see if I understand what's
+> >> happening
+> >> > > > >> here.
+> >> > > > >>
+> >> > > > >> I will come back with my conclusions.
+> >> > > > >>
+> >> > > > >> Robert
+> >> > > > >>
+> >> > > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <
+> >> > > igor@ifedorenko.com>
+> >> > > > >> wrote:
+> >> > > > >>
+> >> > > > >> > TL;DR your test project exposed two existing bugs, one
+> >> change in
+> >> > > > >> > behaviour and one quirk I can't explain
+> >> > > > >> >
+> >> > > > >> > * Build `<extensions>` are loaded by two classloaders, which
+> >> is
+> >> a
+> >> > > bug
+> >> > > > >> in
+> >> > > > >> > DefaultProjectBuildingHelper#createProjectRealm and explains
+> >> why you
+> >> > > > >> see
+> >> > > > >> > extjar1/extjar2 in the output
+> >> > > > >> > * ClassRealm does not allow same foreign-import from multiple
+> >> > > > >> > classloaders, which is a bug and explains why it is not
+> >> possible to
+> >> > > > >> load
+> >> > > > >> > same resource from multiple plugins/extensions
+> >> > > > >> > * TCCL does not have access to private (i.e. not exported)
+> >> resources
+> >> > > > >> of
+> >> > > > >> > this extensions plugin, which is a change of behaviour
+> >> introduced by
+> >> > > > >> > mng-6209 fix
+> >> > > > >> > * Also, component injection order appears to be backwards,
+> >> but
+> >> maybe
+> >> > > > >> > Stuart can explain why.
+> >> > > > >> >
+> >> > > > >> >
+> >> > > > >> > Below is more detailed explanation of expected and observed
+> >> > > behaviour
+> >> > > > >> >
+> >> > > > >> >
+> >> > > > >> > ## Component injection depends on the currently running
+> >> plugin
+> >> and
+> >> > > the
+> >> > > > >> > injection site
+> >> > > > >> >
+> >> > > > >> > Currently running plugins have access to the following
+> >> component
+> >> > > > >> > implementations:
+> >> > > > >> >
+> >> > > > >> > * Regular plugin has access to components implemented by the
+> >> plugin,
+> >> > > > >> > project build extensions, if any (via project class realm
+> >> foreign
+> >> > > > >> > import) and Maven Core.
+> >> > > > >> > * Extension plugin has access to components implemented by
+> >> the
+> >> > > project
+> >> > > > >> > build extensions and Maven Core.
+> >> > > > >> > * Without a running plugin (e.g., during project dependency
+> >> > > > >> resolution),
+> >> > > > >> > components implemented by the project build extensions and
+> >> Maven
+> >> > > Core
+> >> > > > >> > are accessible.
+> >> > > > >> >
+> >> > > > >> > Different injection sites have access to the following
+> >> component
+> >> > > > >> > interfaces:
+> >> > > > >> >
+> >> > > > >> > * Maven Core has access to component interfaces defined by
+> >> the
+> >> core
+> >> > > > >> > itself (obviously)
+> >> > > > >> > * Project build extensions have access to **public**
+> >> component
+> >> > > > >> > interfaces defined by Maven Core and component interfaces
+> >> defined by
+> >> > > > >> the
+> >> > > > >> > build extension itself (there is no way to access component
+> >> > > interfaces
+> >> > > > >> > defined in other extensions)
+> >> > > > >> > * Regular plugins have access to **public** component
+> >> interfaces
+> >> > > > >> defined
+> >> > > > >> > by Maven Core, component interfaces **exported** by build
+> >> extensions
+> >> > > > >> and
+> >> > > > >> > component interfaces defined in the plugin itself
+> >> > > > >> >
+> >> > > > >> > For injection to work, injection site has to have access to
+> >> the
+> >> > > > >> > component interface and the component implementation must be
+> >> > > > >> accessible
+> >> > > > >> > through the current context.
+> >> > > > >> >
+> >> > > > >> > From what I can tell, in your example all plugins have access
+> >> to the
+> >> > > > >> > right components when using current 3.5.2-SNAPSHOT. The
+> >> injection
+> >> > > > >> order
+> >> > > > >> > does appear to be backwards from what I expected, however.
+> >> > > > >> >
+> >> > > > >> >
+> >> > > > >> > ## Resources lookup fully depends on classpath visibility,
+> >> > > > >> specifically
+> >> > > > >> >
+> >> > > > >> > * Regular plugin class realm has access to resources from the
+> >> plugin
+> >> > > > >> > itself, from **exported** packages of the project build
+> >> extensions
+> >> > > and
+> >> > > > >> > **public** Maven Core packages
+> >> > > > >> > * Extensions plugin class realm has access to the resources
+> >> from the
+> >> > > > >> > extensions plugin itself and from **public** Maven Core
+> >> packages
+> >> > > > >> > * Project class realm has access to classes and resources
+> >> > > **exported**
+> >> > > > >> > by project build extensions and **public** Maven Core
+> >> packages
+> >> > > > >> >
+> >> > > > >> > I see three problems here
+> >> > > > >> >
+> >> > > > >> > * Maven adds build single-jar `<extensions>` elements
+> >> directly
+> >> to
+> >> > > > >> > project class realm **and** creates separate extensions class
+> >> realms
+> >> > > > >> for
+> >> > > > >> > them. Which results in duplicate classes/resources loaded by
+> >> two
+> >> > > > >> > classloaders and explains why you see extjar1/extjar2 output
+> >> (which
+> >> > > > >> you
+> >> > > > >> > shouldn't according to the explanation above)
+> >> > > > >> > * ClassRealm does not allow foreign-import of the same
+> >> package
+> >> from
+> >> > > > >> > multiple classloaders. This makes it impossible to load the
+> >> same
+> >> > > > >> > resource from multiple plugins/extensions.
+> >> > > > >> > * Extensions plugins cannot access their own private (i.e.
+> >> not
+> >> > > > >> exported)
+> >> > > > >> > resources via TCCL, this is change in behaviour introduced by
+> >> > > mng-6209
+> >> > > > >> > fix
+> >> > > > >> >
+> >> > > > >> > Hope this helps
+> >> > > > >>
+> >> > > > >>
+> >> ---------------------------------------------------------------------
+> >> > > > >> 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
+> >> > > >
+> >> > >
+> >> > >
+> >> ---------------------------------------------------------------------
+> >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> >> > > For additional commands, e-mail: dev-help@maven.apache.org
+> >> > >
+> >> > > --
+> >> > Sent from my phone
+> >>
+> >> ---------------------------------------------------------------------
+> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> >> For additional commands, e-mail: dev-help@maven.apache.org
+> >>
+> >> --
+> > Sent from my phone
+>
+> ---------------------------------------------------------------------
+> 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
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 34818200D10
+ for <ar...@cust-asf2.ponee.io>; Sun, 24 Sep 2017 19:59:04 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 236401609E6; Sun, 24 Sep 2017 17:59:04 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id E2B521609A7
+ for <ar...@cust-asf.ponee.io>; Sun, 24 Sep 2017 19:59:02 +0200 (CEST)
+Received: (qmail 43167 invoked by uid 500); 24 Sep 2017 17:58:56 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 43152 invoked by uid 99); 24 Sep 2017 17:58:56 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Sep 2017 17:58:56 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EF2A91835D2
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 17:58:55 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=j2Fhtnlt;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=KTeIUNpK
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id aax4ugRdTWg9 for <de...@maven.apache.org>;
+ Sun, 24 Sep 2017 17:58:52 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 305155F2AD
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 17:58:52 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id E320E20BC3
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 13:58:51 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Sun, 24 Sep 2017 13:58:51 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=YIkV8GRhCNGF/Q92ZFUusJZtfJzJD
+ jHXhaUSpYle+eE=; b=j2Fhtnlt6YufwHo2Xb4EeG49pmNuxU1r3zV4qfO8IccnX
+ aTkoXBcLSd9S9j4yWQUBa1muRwSsaPf/Tm1WmGTdsIkoyXiCvGQt95eTUH/nZF+6
+ f2Twwo90xQVn0u5D8j6mTKfkY0kTWbIBH+1P2OloEu9YLOtvRtqx5w2T6MJ5EGgZ
+ YOcIZa4tIZQHRl7nRp2ndbrc21V8ru0FONjuiK1fJ7C9+s0mfe42uS3OhETrPukQ
+ oRfGh9BcTbTJ7bDK+k9hvChbM57MYerIuiY1jW5uS5mCyvJ9nGRFvc/lg7L8X2El
+ 5K+yIEmgSurb3iU9uxhFHTfS33CCB/dFrHYXZZYqg==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=YIkV8G
+ RhCNGF/Q92ZFUusJZtfJzJDjHXhaUSpYle+eE=; b=KTeIUNpK1EAQG1ek/txoTy
+ p34ug8KQCSU02RSGfrE0J7eBvWAOAwQFixkTaehv7Q0PTUloq0a2sowCFdEtHl54
+ WIXyf2jyRp/JU1JfTHd5nG4jNFcEUiNlq+g1YiJffrlPW1MqH+VIVgaYGbeWUCQI
+ Uv3KbP+SgoXVU/NwJpvUoJ/tRdRsZcK5J2SjNJ80++HJCErINIcP1NcC/Mj/FGx/
+ YZMEBUBtqrfdsVaBHXZD1i+Pp6QU2UgL6aVC1rZvgdf49N8cA9E0WsM0LNOetzb7
+ eiT2bn8WPusX0TFq9m2e161Emmig229zEH4Lp6lUCZo3UG0NiH4W+Ej8KyAeSltA
+ ==
+X-ME-Sender: <xms:W_LHWU5mC3iv3Lg5XuISsAye4JLSgx8v-o-K1I4nvPD1219TyQEkFA>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id B8698626A2; Sun, 24 Sep 2017 13:58:51 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+In-Reply-To: <CA...@mail.gmail.com>
+Date: Sun, 24 Sep 2017 13:58:51 -0400
+archived-at: Sun, 24 Sep 2017 17:59:04 -0000
+
+See my answers/comments inline
+
+
+On Sun, Sep 24, 2017, at 12:07 PM, Stephen Connolly wrote:
+> https://maven.apache.org/guides/mini/guide-maven-classloading.html says:
+>
+> > When a build plugin is executed, the thread's context classloader is set
+> to the plugin classloader.
+>
+> So we'll need to fix something somewhere...
+>
+> https://svn.apache.org/repos/infra/websites/production/maven/content/reference/maven-classloading.html
+> is unaccessible from the website due to a rewrite rule...
+>
+> Things that seem to be missing:
+>
+> * What is the desired classloading for a plugin that is marked as an
+> extension? Can a plugin have a META-INF/maven/extension.xml to allow
+> exporting classes and artifacts when used as an extension? How should the
+> classloading look for such a strange beast.
+
+To me, the key requirement is that @Singleton components and class
+static members are singletons when injected in Maven core or in @Mojos.
+This implies that there should be single classloader representing an
+extensions plugins (MNG-5742).
+
+META-INF/maven/extension.xml declares what packages of the extension
+plugin are visible to other (non extension) plugins.
+META-INF/maven/extension.xml does not affect classloading of the
+extension plugin nor it affects the "shape" of other classloaders.
+
+> * How does one access the plugin classloader if we want TCCL to be other
+> than that, is it a Dependency Injection or something else?
+
+this.getClass().getClassLoader() is the most direct way to access plugin
+classloader. Why do you think we need anything more elaborate?
+
+
+> * What differentiates a Core extension from a Build extension (is it that
+> a
+> build extension lacks a META-INF/maven/extension.xml and was only
+> declared
+> in the pom.xml, while a core extension either has a
+> META-INF/maven/extension.xml - if declared in the pom - or is an
+> extension
+> declared in .mvn/extensions.xml)
+
+Core extensions are loaded *before* build starts, so they can contribute
+AbstractMavenLifecycleParticipant#afterSessionStart, for example. They
+can also export packages visible to all build plugins, including
+extensions=true. On the flip side, each core extension is effectively
+singleton, you can't have two different versions of the same Core
+extension. Core extensions also have direct access to Maven core classes
+and can do more interesting things there (for better or worse).
+
+Build extensions are part of the project build and as such are limited
+what components they can contribute to the Core and what core classes
+they have access to.
+
+I tried to capture this in the diagram I drew for
+http://takari.io/book/91-maven-classloading.html.
+
+> At this point in time I think we are nearing the point where I may have
+> to
+> declare 3.5.1 abandoned as I think the classloading in that is a symptom
+> of
+> too many cooks all changing things in different directions. We need a
+> consistent vision of where we want things to go and - while we need not
+> get
+> there in one go - the path presented for others to see.
+
+There were two classloading changes in 3.5.1, namely extensions=true
+plugins now have project realm as TCCL and all realms now use
+application classloader as the parent. Apart from lacking documentation,
+what practical problems have been caused by these two changes?
+
+>
+> Things I think we should consider:
+>
+> 1. Do we want to formally deprecate Build Extensions and the
+> /project/build/extensions element (start logging warnings, etc)?
+> 2. Do we want to formally deprecate plugins as extensions and start
+> logging
+> warnings for
+> /project/build/(pluginManagement|.)/plugins/plugin/extensions[text()==true]
+
+I'd keep them both, and maybe fix/remove maven2-compat codepath. If I
+had to choose between the two, however, I'd choose <plugin> with
+extensions=true. Think of a custom packaging type with mojos the user
+wants to configure in pom.xml, it'd be more tedious to configure if I
+had to add build/extension and build/plugin.
+
+> 3. What is the difference in classloading for a /project/build/extensions
+> which has a META-INF/maven/extension.xml and one that doesn't?
+
+I think extensions with META-INF/maven/extension.xml should not go
+through maven2-compat codepath. In other words, we need to change the
+current behaviour.
+
+Extensions without META-INF/maven/extension.xml... I am not sure.
+Probably safer to keep the current maven2-compat behaviour.
+
+> I'm keeping the 3.5.1 release in staging until we get a clear vision for
+> how we want to have classloading so that I can assess whether the 3.5.1
+> actuality is only moving nearer to the vision (ok to release) or has
+> moved
+> nearer in some ways but further in others (not ok to release)
+>
+
+
+--
+Regards,
+Igor
+
+
+
+> On 20 September 2017 at 12:44, Igor Fedorenko <ig...@ifedorenko.com>
+> wrote:
+>
+> > Real-world scm or wagon <extensions> won't trigger maven2-compat code
+> > path [1]. To avoid that obscure code path we can either make the test
+> > more elaborate (i.e. add dependencies to extjar1/extjar2) or we can use
+> > extensions <plugin>. Either way I don't think we should spend time on
+> > the code path unlikely to be used in real life.
+> >
+> > [1]
+> > https://github.com/apache/maven/blob/maven-3.5.1/maven-
+> > core/src/main/java/org/apache/maven/project/DefaultProjectBuildingHelper.
+> > java#L210-L219
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> > On Wed, Sep 20, 2017, at 03:29 AM, Robert Scholte wrote:
+> > > On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly
+> > > <st...@gmail.com> wrote:
+> > >
+> > > > On Wed 20 Sep 2017 at 01:29, Igor Fedorenko <ig...@ifedorenko.com>
+> > wrote:
+> > > >
+> > > >> In that case, can I suggest couple of changes to the test project
+> > > >>
+> > > >> * I thinks it makes more sense to configure extjar1 and extjar2 as
+> > > >> extensions <plugin> elements in probleN pom.xml files. First, there is
+> > > >> no meaningful order between <extensions> and <plugins> elements. More
+> > > >> importantly, though, simple <extensions> are treated in special
+> > > >> maven2-compat mode and are not representative of likely real-world
+> > > >> extensions.
+> > > >
+> > >
+> > > Not sure I agree with this. I think there are jars worth sharing across
+> > > multiple plugins, but where making the plugin an extension is a bit
+> > > weird.
+> > > I'm thinking of scm and wagon in this case.
+> > >
+> > > >
+> > > > That sounds like we need documentation updated then. None of that is
+> > > > obvious to me.
+> > > >
+> > > >
+> > > >>
+> > > >> * I think we should introduce META-INF/maven/extension.xml to the test
+> > > >> extensions. This metadata what introduced to configure classpath
+> > > >> visibility, so lets use it.
+> > > >
+> > > >
+> > > > Again, not obvious to me, if that file allows control of classpath
+> > > > visibility then it may be that the only issue *with* 3.5.1 is the lack
+> > of
+> > > > documentation... now previous versions would have been adding breaking
+> > > > changes from my PoV but that is the past and should not affect the
+> > 3.5.1
+> > > > release.
+> > > >
+> > > > PRs for the probe project welcome. I am happy to try and write docs
+> > once
+> > > > I
+> > > > have an understanding of what the expected behaviours are
+> > > >
+> > > >
+> > > >>
+> > > >> --
+> > > >> Regards,
+> > > >> Igor
+> > > >>
+> > > >> On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> > > >> > Yes, the expectations are key. Depending on what they are we may
+> > > >> either
+> > > >> > drop 3.5.1 or go ahead as it depends on whether this is more correct
+> > > >> than
+> > > >> > 3.5.0 or swapping one fix for a bug
+> > > >> >
+> > > >> > On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <ig...@ifedorenko.com>
+> > > >> wrote:
+> > > >> >
+> > > >> > > Just to confirm I understand what we are trying to establish here.
+> > > >> We
+> > > >> > > want to decide the expected/desired component injection behaviour
+> > > >> and
+> > > >> > > classpath visibility in the absence of package and artifact export
+> > > >> > > configuration (i.e. META-INF/maven/extension.xml file). Did I get
+> > > >> this
+> > > >> > > right?
+> > > >> > >
+> > > >> > > --
+> > > >> > > Regards,
+> > > >> > > Igor
+> > > >> > >
+> > > >> > > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> > > >> > > > Let's do it like this:
+> > > >> > > >
+> > > >> > >
+> > > >> https://cwiki.apache.org/confluence/download/attachments/2329841/
+> > classrealms.pdf?api=v2
+> > > >> > > >
+> > > >> > > > Robert
+> > > >> > > >
+> > > >> > > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> > > >> > > > <st...@gmail.com> wrote:
+> > > >> > > >
+> > > >> > > > > I think you will need a link to the PDF as attachments are
+> > > >> stripped
+> > > >> > > from
+> > > >> > > > > the ML
+> > > >> > > > >
+> > > >> > > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte
+> > > >> <rf...@apache.org>
+> > > >> > > wrote:
+> > > >> > > > >
+> > > >> > > > >> Attached a single page overview.
+> > > >> > > > >>
+> > > >> > > > >> Per block you'll see in the upper left corner the executed
+> > > >> plugin
+> > > >> > > > >> The left column contains the extensions and plugin in orderas
+> > > >> > > specified
+> > > >> > > > >> in
+> > > >> > > > >> the pom.xml
+> > > >> > > > >> In every classloadercolumn you'll see numbers which represent
+> > > >> the
+> > > >> > > order.
+> > > >> > > > >>
+> > > >> > > > >> I hope I didn't make any mistakes.
+> > > >> > > > >> Tomorrow I have enough time to see if I understand what's
+> > > >> happening
+> > > >> > > > >> here.
+> > > >> > > > >>
+> > > >> > > > >> I will come back with my conclusions.
+> > > >> > > > >>
+> > > >> > > > >> Robert
+> > > >> > > > >>
+> > > >> > > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <
+> > > >> > > igor@ifedorenko.com>
+> > > >> > > > >> wrote:
+> > > >> > > > >>
+> > > >> > > > >> > TL;DR your test project exposed two existing bugs, one
+> > > >> change in
+> > > >> > > > >> > behaviour and one quirk I can't explain
+> > > >> > > > >> >
+> > > >> > > > >> > * Build `<extensions>` are loaded by two classloaders,
+> > which
+> > > >> is
+> > > >> a
+> > > >> > > bug
+> > > >> > > > >> in
+> > > >> > > > >> > DefaultProjectBuildingHelper#createProjectRealm and
+> > explains
+> > > >> why you
+> > > >> > > > >> see
+> > > >> > > > >> > extjar1/extjar2 in the output
+> > > >> > > > >> > * ClassRealm does not allow same foreign-import from
+> > multiple
+> > > >> > > > >> > classloaders, which is a bug and explains why it is not
+> > > >> possible to
+> > > >> > > > >> load
+> > > >> > > > >> > same resource from multiple plugins/extensions
+> > > >> > > > >> > * TCCL does not have access to private (i.e. not exported)
+> > > >> resources
+> > > >> > > > >> of
+> > > >> > > > >> > this extensions plugin, which is a change of behaviour
+> > > >> introduced by
+> > > >> > > > >> > mng-6209 fix
+> > > >> > > > >> > * Also, component injection order appears to be backwards,
+> > > >> but
+> > > >> maybe
+> > > >> > > > >> > Stuart can explain why.
+> > > >> > > > >> >
+> > > >> > > > >> >
+> > > >> > > > >> > Below is more detailed explanation of expected and observed
+> > > >> > > behaviour
+> > > >> > > > >> >
+> > > >> > > > >> >
+> > > >> > > > >> > ## Component injection depends on the currently running
+> > > >> plugin
+> > > >> and
+> > > >> > > the
+> > > >> > > > >> > injection site
+> > > >> > > > >> >
+> > > >> > > > >> > Currently running plugins have access to the following
+> > > >> component
+> > > >> > > > >> > implementations:
+> > > >> > > > >> >
+> > > >> > > > >> > * Regular plugin has access to components implemented by
+> > the
+> > > >> plugin,
+> > > >> > > > >> > project build extensions, if any (via project class realm
+> > > >> foreign
+> > > >> > > > >> > import) and Maven Core.
+> > > >> > > > >> > * Extension plugin has access to components implemented by
+> > > >> the
+> > > >> > > project
+> > > >> > > > >> > build extensions and Maven Core.
+> > > >> > > > >> > * Without a running plugin (e.g., during project dependency
+> > > >> > > > >> resolution),
+> > > >> > > > >> > components implemented by the project build extensions and
+> > > >> Maven
+> > > >> > > Core
+> > > >> > > > >> > are accessible.
+> > > >> > > > >> >
+> > > >> > > > >> > Different injection sites have access to the following
+> > > >> component
+> > > >> > > > >> > interfaces:
+> > > >> > > > >> >
+> > > >> > > > >> > * Maven Core has access to component interfaces defined by
+> > > >> the
+> > > >> core
+> > > >> > > > >> > itself (obviously)
+> > > >> > > > >> > * Project build extensions have access to **public**
+> > > >> component
+> > > >> > > > >> > interfaces defined by Maven Core and component interfaces
+> > > >> defined by
+> > > >> > > > >> the
+> > > >> > > > >> > build extension itself (there is no way to access component
+> > > >> > > interfaces
+> > > >> > > > >> > defined in other extensions)
+> > > >> > > > >> > * Regular plugins have access to **public** component
+> > > >> interfaces
+> > > >> > > > >> defined
+> > > >> > > > >> > by Maven Core, component interfaces **exported** by build
+> > > >> extensions
+> > > >> > > > >> and
+> > > >> > > > >> > component interfaces defined in the plugin itself
+> > > >> > > > >> >
+> > > >> > > > >> > For injection to work, injection site has to have access to
+> > > >> the
+> > > >> > > > >> > component interface and the component implementation must
+> > be
+> > > >> > > > >> accessible
+> > > >> > > > >> > through the current context.
+> > > >> > > > >> >
+> > > >> > > > >> > From what I can tell, in your example all plugins have
+> > access
+> > > >> to the
+> > > >> > > > >> > right components when using current 3.5.2-SNAPSHOT. The
+> > > >> injection
+> > > >> > > > >> order
+> > > >> > > > >> > does appear to be backwards from what I expected, however.
+> > > >> > > > >> >
+> > > >> > > > >> >
+> > > >> > > > >> > ## Resources lookup fully depends on classpath visibility,
+> > > >> > > > >> specifically
+> > > >> > > > >> >
+> > > >> > > > >> > * Regular plugin class realm has access to resources from
+> > the
+> > > >> plugin
+> > > >> > > > >> > itself, from **exported** packages of the project build
+> > > >> extensions
+> > > >> > > and
+> > > >> > > > >> > **public** Maven Core packages
+> > > >> > > > >> > * Extensions plugin class realm has access to the resources
+> > > >> from the
+> > > >> > > > >> > extensions plugin itself and from **public** Maven Core
+> > > >> packages
+> > > >> > > > >> > * Project class realm has access to classes and resources
+> > > >> > > **exported**
+> > > >> > > > >> > by project build extensions and **public** Maven Core
+> > > >> packages
+> > > >> > > > >> >
+> > > >> > > > >> > I see three problems here
+> > > >> > > > >> >
+> > > >> > > > >> > * Maven adds build single-jar `<extensions>` elements
+> > > >> directly
+> > > >> to
+> > > >> > > > >> > project class realm **and** creates separate extensions
+> > class
+> > > >> realms
+> > > >> > > > >> for
+> > > >> > > > >> > them. Which results in duplicate classes/resources loaded
+> > by
+> > > >> two
+> > > >> > > > >> > classloaders and explains why you see extjar1/extjar2
+> > output
+> > > >> (which
+> > > >> > > > >> you
+> > > >> > > > >> > shouldn't according to the explanation above)
+> > > >> > > > >> > * ClassRealm does not allow foreign-import of the same
+> > > >> package
+> > > >> from
+> > > >> > > > >> > multiple classloaders. This makes it impossible to load the
+> > > >> same
+> > > >> > > > >> > resource from multiple plugins/extensions.
+> > > >> > > > >> > * Extensions plugins cannot access their own private (i.e.
+> > > >> not
+> > > >> > > > >> exported)
+> > > >> > > > >> > resources via TCCL, this is change in behaviour introduced
+> > by
+> > > >> > > mng-6209
+> > > >> > > > >> > fix
+> > > >> > > > >> >
+> > > >> > > > >> > Hope this helps
+> > > >> > > > >>
+> > > >> > > > >>
+> > > >> ---------------------------------------------------------------------
+> > > >> > > > >> 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
+> > > >> > > >
+> > > >> > >
+> > > >> > >
+> > > >> ---------------------------------------------------------------------
+> > > >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > >> > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > >> > >
+> > > >> > > --
+> > > >> > Sent from my phone
+> > > >>
+> > > >> ---------------------------------------------------------------------
+> > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > >> For additional commands, e-mail: dev-help@maven.apache.org
+> > > >>
+> > > >> --
+> > > > Sent from my phone
+> > >
+> > > ---------------------------------------------------------------------
+> > > 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
+> >
+> >
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 00386200D10
+ for <ar...@cust-asf2.ponee.io>; Sun, 24 Sep 2017 21:06:19 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id F2BE51609E6; Sun, 24 Sep 2017 19:06:18 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id A25A71609A7
+ for <ar...@cust-asf.ponee.io>; Sun, 24 Sep 2017 21:06:17 +0200 (CEST)
+Received: (qmail 25011 invoked by uid 500); 24 Sep 2017 19:06:16 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 24993 invoked by uid 99); 24 Sep 2017 19:06:16 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Sep 2017 19:06:16 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CBE881A584B
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 19:06:15 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd2-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=k3ka9mpv;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=ebU5PBdR
+Received: from mx1-lw-us.apache.org ([10.40.0.8])
+ by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
+ with ESMTP id aSFb89n6b2EK for <de...@maven.apache.org>;
+ Sun, 24 Sep 2017 19:06:11 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 0E15860FA3
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 19:06:10 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id 9F59620D2A
+ for <de...@maven.apache.org>; Sun, 24 Sep 2017 15:06:10 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Sun, 24 Sep 2017 15:06:10 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=QVXMSLSXvvwwJuUxTqNH70AMckTiL
+ BvOK/64GvNgibc=; b=k3ka9mpv24QWoXm81eafmlLG4xqD8OLgKOUPq5lByBUWx
+ mrsfO1p0hAaKSpPeTBvDqGpEJ6/FvXwBR3sC+CBVS4rygCgVe/r2pHxAu5UIyZuF
+ /GjjBuM0gK1G9IteJZtBQYRNNTR+HcK1+0fuyG4ZmQTZ1ane+xWHiDZ4IQaYbniv
+ HpB5E0tbaaOuV25Cfz9luXLXWuAb74PmkW/PrzJd9f9k1toWCzZKs9ACNffKgTJR
+ Oj/IhAQgT6jg4ZcsOMK8+mFAr2mgiN4eyGzFAVCMtKxP2y0Azztq3XzAzVNMc/4B
+ 8Zft32uilpSAHm4Y8hAnkOtroZs1SxbVRtAPo/qWg==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=QVXMSL
+ SXvvwwJuUxTqNH70AMckTiLBvOK/64GvNgibc=; b=ebU5PBdRqaBSqlXCqNBmEh
+ RJdJpQZZ2XS7urV+Pf5byqFVjaPiggn+rdCnE3/eQaRA1TGisWGjFNiDsUnP+0yq
+ bciPAR103TfXwoKB5JsAhpFj+yf1pNIteNQNtv/1LREPg1uw6NYz4CjoZ3JJcM0Z
+ hllc6PadVdlZFWKRJi11q/9GMkHn//5XpbgVykDwr4AZt4D3qeFLLRBzN9hTPBZB
+ RfDgSu7hZQuah8wii2dg3yjM9/rVKunUjQQqP4YLnCqyKUPME7Q/E7tHnmj2dStC
+ Z/698NoUQt2famjOUxoDmcqrEF35Ih4PBK6odlrX+9fICBFhrOomNX77LRupkoJA
+ ==
+X-ME-Sender: <xms:IgLIWYy1JIrDIiaoyrC_c30dLpepk8s2lyRPuKSMoCcg2kDjWHh7fQ>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 6B2D6626A2; Sun, 24 Sep 2017 15:06:10 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Date: Sun, 24 Sep 2017 15:06:10 -0400
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+In-Reply-To: <CA...@mail.gmail.com>
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+archived-at: Sun, 24 Sep 2017 19:06:19 -0000
+
+Lets decide the agenda first, then who you need to attend (assuming you
+are driving this discussion/decision), then pick the time that works.
+
+>From my side, I still don't understand the problems we are trying to
+solve. If this is the lacking documentation and general "uncomfort" to
+mess with classloading in bug fix release, then maybe do what Anders
+suggests (I think), bump the version to 3.6.0, document the behaviour we
+have on master and move on.
+
+--=20
+Regards,
+Igor
+
+On Sun, Sep 24, 2017, at 02:28 PM, Stephen Connolly wrote:
+> I wonder should we do a hangout to decide what you do?
+>=20
+> What times on Monday work best?
+>=20
+> I can maybe do 8:30-9:30pm Irish time
+>=20
+> https://www.timeanddate.com/worldclock/meetingdetails.html?year=3D2017&mo=
+nth=3D9&day=3D25&hour=3D19&min=3D30&sec=3D0&p1=3D78&p2=3D37&p3=3D179
+>=20
+> But we=E2=80=99d need to decide who we need and an actual agenda.
+>=20
+> If Monday is too soon I can see if I have a window later this week
+>=20
+> On Sun 24 Sep 2017 at 18:58, Igor Fedorenko <ig...@ifedorenko.com> wrote:
+>=20
+> > See my answers/comments inline
+> >
+> >
+> > On Sun, Sep 24, 2017, at 12:07 PM, Stephen Connolly wrote:
+> > > https://maven.apache.org/guides/mini/guide-maven-classloading.html sa=
+ys:
+> > >
+> > > > When a build plugin is executed, the thread's context classloader is
+> > set
+> > > to the plugin classloader.
+> > >
+> > > So we'll need to fix something somewhere...
+> > >
+> > >
+> > https://svn.apache.org/repos/infra/websites/production/maven/content/re=
+ference/maven-classloading.html
+> > > is unaccessible from the website due to a rewrite rule...
+> > >
+> > > Things that seem to be missing:
+> > >
+> > > * What is the desired classloading for a plugin that is marked as an
+> > > extension? Can a plugin have a META-INF/maven/extension.xml to allow
+> > > exporting classes and artifacts when used as an extension? How should=
+ the
+> > > classloading look for such a strange beast.
+> >
+> > To me, the key requirement is that @Singleton components and class
+> > static members are singletons when injected in Maven core or in @Mojos.
+> > This implies that there should be single classloader representing an
+> > extensions plugins (MNG-5742).
+> >
+> > META-INF/maven/extension.xml declares what packages of the extension
+> > plugin are visible to other (non extension) plugins.
+> > META-INF/maven/extension.xml does not affect classloading of the
+> > extension plugin nor it affects the "shape" of other classloaders.
+> >
+> > > * How does one access the plugin classloader if we want TCCL to be ot=
+her
+> > > than that, is it a Dependency Injection or something else?
+> >
+> > this.getClass().getClassLoader() is the most direct way to access plugin
+> > classloader. Why do you think we need anything more elaborate?
+> >
+> >
+> > > * What differentiates a Core extension from a Build extension (is it =
+that
+> > > a
+> > > build extension lacks a META-INF/maven/extension.xml and was only
+> > > declared
+> > > in the pom.xml, while a core extension either has a
+> > > META-INF/maven/extension.xml - if declared in the pom - or is an
+> > > extension
+> > > declared in .mvn/extensions.xml)
+> >
+> > Core extensions are loaded *before* build starts, so they can contribute
+> > AbstractMavenLifecycleParticipant#afterSessionStart, for example. They
+> > can also export packages visible to all build plugins, including
+> > extensions=3Dtrue. On the flip side, each core extension is effectively
+> > singleton, you can't have two different versions of the same Core
+> > extension. Core extensions also have direct access to Maven core classes
+> > and can do more interesting things there (for better or worse).
+> >
+> > Build extensions are part of the project build and as such are limited
+> > what components they can contribute to the Core and what core classes
+> > they have access to.
+> >
+> > I tried to capture this in the diagram I drew for
+> > http://takari.io/book/91-maven-classloading.html.
+> >
+> > > At this point in time I think we are nearing the point where I may ha=
+ve
+> > > to
+> > > declare 3.5.1 abandoned as I think the classloading in that is a symp=
+tom
+> > > of
+> > > too many cooks all changing things in different directions. We need a
+> > > consistent vision of where we want things to go and - while we need n=
+ot
+> > > get
+> > > there in one go - the path presented for others to see.
+> >
+> > There were two classloading changes in 3.5.1, namely extensions=3Dtrue
+> > plugins now have project realm as TCCL and all realms now use
+> > application classloader as the parent. Apart from lacking documentation,
+> > what practical problems have been caused by these two changes?
+> >
+> > >
+> > > Things I think we should consider:
+> > >
+> > > 1. Do we want to formally deprecate Build Extensions and the
+> > > /project/build/extensions element (start logging warnings, etc)?
+> > > 2. Do we want to formally deprecate plugins as extensions and start
+> > > logging
+> > > warnings for
+> > >
+> > /project/build/(pluginManagement|.)/plugins/plugin/extensions[text()=3D=
+=3Dtrue]
+> >
+> > I'd keep them both, and maybe fix/remove maven2-compat codepath. If I
+> > had to choose between the two, however, I'd choose <plugin> with
+> > extensions=3Dtrue. Think of a custom packaging type with mojos the user
+> > wants to configure in pom.xml, it'd be more tedious to configure if I
+> > had to add build/extension and build/plugin.
+> >
+> > > 3. What is the difference in classloading for a /project/build/extens=
+ions
+> > > which has a META-INF/maven/extension.xml and one that doesn't?
+> >
+> > I think extensions with META-INF/maven/extension.xml should not go
+> > through maven2-compat codepath. In other words, we need to change the
+> > current behaviour.
+> >
+> > Extensions without META-INF/maven/extension.xml... I am not sure.
+> > Probably safer to keep the current maven2-compat behaviour.
+> >
+> > > I'm keeping the 3.5.1 release in staging until we get a clear vision =
+for
+> > > how we want to have classloading so that I can assess whether the 3.5=
+.1
+> > > actuality is only moving nearer to the vision (ok to release) or has
+> > > moved
+> > > nearer in some ways but further in others (not ok to release)
+> > >
+> >
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> >
+> >
+> > > On 20 September 2017 at 12:44, Igor Fedorenko <ig...@ifedorenko.com>
+> > > wrote:
+> > >
+> > > > Real-world scm or wagon <extensions> won't trigger maven2-compat co=
+de
+> > > > path [1]. To avoid that obscure code path we can either make the te=
+st
+> > > > more elaborate (i.e. add dependencies to extjar1/extjar2) or we can=
+ use
+> > > > extensions <plugin>. Either way I don't think we should spend time =
+on
+> > > > the code path unlikely to be used in real life.
+> > > >
+> > > > [1]
+> > > > https://github.com/apache/maven/blob/maven-3.5.1/maven-
+> > > >
+> > core/src/main/java/org/apache/maven/project/DefaultProjectBuildingHelpe=
+r.
+> > > > java#L210-L219
+> > > >
+> > > > --
+> > > > Regards,
+> > > > Igor
+> > > >
+> > > > On Wed, Sep 20, 2017, at 03:29 AM, Robert Scholte wrote:
+> > > > > On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly
+> > > > > <st...@gmail.com> wrote:
+> > > > >
+> > > > > > On Wed 20 Sep 2017 at 01:29, Igor Fedorenko <igor@ifedorenko.co=
+m>
+> > > > wrote:
+> > > > > >
+> > > > > >> In that case, can I suggest couple of changes to the test proj=
+ect
+> > > > > >>
+> > > > > >> * I thinks it makes more sense to configure extjar1 and extjar=
+2 as
+> > > > > >> extensions <plugin> elements in probleN pom.xml files. First,
+> > there is
+> > > > > >> no meaningful order between <extensions> and <plugins> element=
+s.
+> > More
+> > > > > >> importantly, though, simple <extensions> are treated in special
+> > > > > >> maven2-compat mode and are not representative of likely real-w=
+orld
+> > > > > >> extensions.
+> > > > > >
+> > > > >
+> > > > > Not sure I agree with this. I think there are jars worth sharing
+> > across
+> > > > > multiple plugins, but where making the plugin an extension is a b=
+it
+> > > > > weird.
+> > > > > I'm thinking of scm and wagon in this case.
+> > > > >
+> > > > > >
+> > > > > > That sounds like we need documentation updated then. None of th=
+at
+> > is
+> > > > > > obvious to me.
+> > > > > >
+> > > > > >
+> > > > > >>
+> > > > > >> * I think we should introduce META-INF/maven/extension.xml to =
+the
+> > test
+> > > > > >> extensions. This metadata what introduced to configure classpa=
+th
+> > > > > >> visibility, so lets use it.
+> > > > > >
+> > > > > >
+> > > > > > Again, not obvious to me, if that file allows control of classp=
+ath
+> > > > > > visibility then it may be that the only issue *with* 3.5.1 is t=
+he
+> > lack
+> > > > of
+> > > > > > documentation... now previous versions would have been adding
+> > breaking
+> > > > > > changes from my PoV but that is the past and should not affect =
+the
+> > > > 3.5.1
+> > > > > > release.
+> > > > > >
+> > > > > > PRs for the probe project welcome. I am happy to try and write =
+docs
+> > > > once
+> > > > > > I
+> > > > > > have an understanding of what the expected behaviours are
+> > > > > >
+> > > > > >
+> > > > > >>
+> > > > > >> --
+> > > > > >> Regards,
+> > > > > >> Igor
+> > > > > >>
+> > > > > >> On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> > > > > >> > Yes, the expectations are key. Depending on what they are we=
+ may
+> > > > > >> either
+> > > > > >> > drop 3.5.1 or go ahead as it depends on whether this is more
+> > correct
+> > > > > >> than
+> > > > > >> > 3.5.0 or swapping one fix for a bug
+> > > > > >> >
+> > > > > >> > On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <
+> > igor@ifedorenko.com>
+> > > > > >> wrote:
+> > > > > >> >
+> > > > > >> > > Just to confirm I understand what we are trying to establi=
+sh
+> > here.
+> > > > > >> We
+> > > > > >> > > want to decide the expected/desired component injection
+> > behaviour
+> > > > > >> and
+> > > > > >> > > classpath visibility in the absence of package and artifact
+> > export
+> > > > > >> > > configuration (i.e. META-INF/maven/extension.xml file). Di=
+d I
+> > get
+> > > > > >> this
+> > > > > >> > > right?
+> > > > > >> > >
+> > > > > >> > > --
+> > > > > >> > > Regards,
+> > > > > >> > > Igor
+> > > > > >> > >
+> > > > > >> > > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrote:
+> > > > > >> > > > Let's do it like this:
+> > > > > >> > > >
+> > > > > >> > >
+> > > > > >> https://cwiki.apache.org/confluence/download/attachments/23298=
+41/
+> > > > classrealms.pdf?api=3Dv2
+> > > > > >> > > >
+> > > > > >> > > > Robert
+> > > > > >> > > >
+> > > > > >> > > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> > > > > >> > > > <st...@gmail.com> wrote:
+> > > > > >> > > >
+> > > > > >> > > > > I think you will need a link to the PDF as attachments=
+ are
+> > > > > >> stripped
+> > > > > >> > > from
+> > > > > >> > > > > the ML
+> > > > > >> > > > >
+> > > > > >> > > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte
+> > > > > >> <rf...@apache.org>
+> > > > > >> > > wrote:
+> > > > > >> > > > >
+> > > > > >> > > > >> Attached a single page overview.
+> > > > > >> > > > >>
+> > > > > >> > > > >> Per block you'll see in the upper left corner the
+> > executed
+> > > > > >> plugin
+> > > > > >> > > > >> The left column contains the extensions and plugin in
+> > orderas
+> > > > > >> > > specified
+> > > > > >> > > > >> in
+> > > > > >> > > > >> the pom.xml
+> > > > > >> > > > >> In every classloadercolumn you'll see numbers which
+> > represent
+> > > > > >> the
+> > > > > >> > > order.
+> > > > > >> > > > >>
+> > > > > >> > > > >> I hope I didn't make any mistakes.
+> > > > > >> > > > >> Tomorrow I have enough time to see if I understand wh=
+at's
+> > > > > >> happening
+> > > > > >> > > > >> here.
+> > > > > >> > > > >>
+> > > > > >> > > > >> I will come back with my conclusions.
+> > > > > >> > > > >>
+> > > > > >> > > > >> Robert
+> > > > > >> > > > >>
+> > > > > >> > > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenko <
+> > > > > >> > > igor@ifedorenko.com>
+> > > > > >> > > > >> wrote:
+> > > > > >> > > > >>
+> > > > > >> > > > >> > TL;DR your test project exposed two existing bugs, =
+one
+> > > > > >> change in
+> > > > > >> > > > >> > behaviour and one quirk I can't explain
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > * Build `<extensions>` are loaded by two classloade=
+rs,
+> > > > which
+> > > > > >> is
+> > > > > >> a
+> > > > > >> > > bug
+> > > > > >> > > > >> in
+> > > > > >> > > > >> > DefaultProjectBuildingHelper#createProjectRealm and
+> > > > explains
+> > > > > >> why you
+> > > > > >> > > > >> see
+> > > > > >> > > > >> > extjar1/extjar2 in the output
+> > > > > >> > > > >> > * ClassRealm does not allow same foreign-import from
+> > > > multiple
+> > > > > >> > > > >> > classloaders, which is a bug and explains why it is=
+ not
+> > > > > >> possible to
+> > > > > >> > > > >> load
+> > > > > >> > > > >> > same resource from multiple plugins/extensions
+> > > > > >> > > > >> > * TCCL does not have access to private (i.e. not
+> > exported)
+> > > > > >> resources
+> > > > > >> > > > >> of
+> > > > > >> > > > >> > this extensions plugin, which is a change of behavi=
+our
+> > > > > >> introduced by
+> > > > > >> > > > >> > mng-6209 fix
+> > > > > >> > > > >> > * Also, component injection order appears to be
+> > backwards,
+> > > > > >> but
+> > > > > >> maybe
+> > > > > >> > > > >> > Stuart can explain why.
+> > > > > >> > > > >> >
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > Below is more detailed explanation of expected and
+> > observed
+> > > > > >> > > behaviour
+> > > > > >> > > > >> >
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > ## Component injection depends on the currently run=
+ning
+> > > > > >> plugin
+> > > > > >> and
+> > > > > >> > > the
+> > > > > >> > > > >> > injection site
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > Currently running plugins have access to the follow=
+ing
+> > > > > >> component
+> > > > > >> > > > >> > implementations:
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > * Regular plugin has access to components implement=
+ed
+> > by
+> > > > the
+> > > > > >> plugin,
+> > > > > >> > > > >> > project build extensions, if any (via project class
+> > realm
+> > > > > >> foreign
+> > > > > >> > > > >> > import) and Maven Core.
+> > > > > >> > > > >> > * Extension plugin has access to components
+> > implemented by
+> > > > > >> the
+> > > > > >> > > project
+> > > > > >> > > > >> > build extensions and Maven Core.
+> > > > > >> > > > >> > * Without a running plugin (e.g., during project
+> > dependency
+> > > > > >> > > > >> resolution),
+> > > > > >> > > > >> > components implemented by the project build extensi=
+ons
+> > and
+> > > > > >> Maven
+> > > > > >> > > Core
+> > > > > >> > > > >> > are accessible.
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > Different injection sites have access to the follow=
+ing
+> > > > > >> component
+> > > > > >> > > > >> > interfaces:
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > * Maven Core has access to component interfaces
+> > defined by
+> > > > > >> the
+> > > > > >> core
+> > > > > >> > > > >> > itself (obviously)
+> > > > > >> > > > >> > * Project build extensions have access to **public**
+> > > > > >> component
+> > > > > >> > > > >> > interfaces defined by Maven Core and component
+> > interfaces
+> > > > > >> defined by
+> > > > > >> > > > >> the
+> > > > > >> > > > >> > build extension itself (there is no way to access
+> > component
+> > > > > >> > > interfaces
+> > > > > >> > > > >> > defined in other extensions)
+> > > > > >> > > > >> > * Regular plugins have access to **public** compone=
+nt
+> > > > > >> interfaces
+> > > > > >> > > > >> defined
+> > > > > >> > > > >> > by Maven Core, component interfaces **exported** by
+> > build
+> > > > > >> extensions
+> > > > > >> > > > >> and
+> > > > > >> > > > >> > component interfaces defined in the plugin itself
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > For injection to work, injection site has to have
+> > access to
+> > > > > >> the
+> > > > > >> > > > >> > component interface and the component implementation
+> > must
+> > > > be
+> > > > > >> > > > >> accessible
+> > > > > >> > > > >> > through the current context.
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > From what I can tell, in your example all plugins h=
+ave
+> > > > access
+> > > > > >> to the
+> > > > > >> > > > >> > right components when using current 3.5.2-SNAPSHOT.=
+ The
+> > > > > >> injection
+> > > > > >> > > > >> order
+> > > > > >> > > > >> > does appear to be backwards from what I expected,
+> > however.
+> > > > > >> > > > >> >
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > ## Resources lookup fully depends on classpath
+> > visibility,
+> > > > > >> > > > >> specifically
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > * Regular plugin class realm has access to resources
+> > from
+> > > > the
+> > > > > >> plugin
+> > > > > >> > > > >> > itself, from **exported** packages of the project b=
+uild
+> > > > > >> extensions
+> > > > > >> > > and
+> > > > > >> > > > >> > **public** Maven Core packages
+> > > > > >> > > > >> > * Extensions plugin class realm has access to the
+> > resources
+> > > > > >> from the
+> > > > > >> > > > >> > extensions plugin itself and from **public** Maven =
+Core
+> > > > > >> packages
+> > > > > >> > > > >> > * Project class realm has access to classes and
+> > resources
+> > > > > >> > > **exported**
+> > > > > >> > > > >> > by project build extensions and **public** Maven Co=
+re
+> > > > > >> packages
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > I see three problems here
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > * Maven adds build single-jar `<extensions>` elemen=
+ts
+> > > > > >> directly
+> > > > > >> to
+> > > > > >> > > > >> > project class realm **and** creates separate extens=
+ions
+> > > > class
+> > > > > >> realms
+> > > > > >> > > > >> for
+> > > > > >> > > > >> > them. Which results in duplicate classes/resources
+> > loaded
+> > > > by
+> > > > > >> two
+> > > > > >> > > > >> > classloaders and explains why you see extjar1/extja=
+r2
+> > > > output
+> > > > > >> (which
+> > > > > >> > > > >> you
+> > > > > >> > > > >> > shouldn't according to the explanation above)
+> > > > > >> > > > >> > * ClassRealm does not allow foreign-import of the s=
+ame
+> > > > > >> package
+> > > > > >> from
+> > > > > >> > > > >> > multiple classloaders. This makes it impossible to
+> > load the
+> > > > > >> same
+> > > > > >> > > > >> > resource from multiple plugins/extensions.
+> > > > > >> > > > >> > * Extensions plugins cannot access their own private
+> > (i.e.
+> > > > > >> not
+> > > > > >> > > > >> exported)
+> > > > > >> > > > >> > resources via TCCL, this is change in behaviour
+> > introduced
+> > > > by
+> > > > > >> > > mng-6209
+> > > > > >> > > > >> > fix
+> > > > > >> > > > >> >
+> > > > > >> > > > >> > Hope this helps
+> > > > > >> > > > >>
+> > > > > >> > > > >>
+> > > > > >>
+> > ---------------------------------------------------------------------
+> > > > > >> > > > >> 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.o=
+rg
+> > > > > >> > > >
+> > > > > >> > >
+> > > > > >> > >
+> > > > > >>
+> > ---------------------------------------------------------------------
+> > > > > >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > >> > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > > > >> > >
+> > > > > >> > > --
+> > > > > >> > Sent from my phone
+> > > > > >>
+> > > > > >>
+> > ---------------------------------------------------------------------
+> > > > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > >> For additional commands, e-mail: dev-help@maven.apache.org
+> > > > > >>
+> > > > > >> --
+> > > > > > Sent from my phone
+> > > > >
+> > > > > -----------------------------------------------------------------=
+----
+> > > > > 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
+> > > >
+> > > >
+> >
+> > ---------------------------------------------------------------------
+> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > For additional commands, e-mail: dev-help@maven.apache.org
+> >
+> > --
+> Sent from my phone
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id 2983B200D06
+ for <ar...@cust-asf2.ponee.io>; Mon, 25 Sep 2017 15:03:46 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id 281951609C4; Mon, 25 Sep 2017 13:03:46 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 9B9641609BB
+ for <ar...@cust-asf.ponee.io>; Mon, 25 Sep 2017 15:03:44 +0200 (CEST)
+Received: (qmail 67492 invoked by uid 500); 25 Sep 2017 13:03:43 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 67467 invoked by uid 99); 25 Sep 2017 13:03:43 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Sep 2017 13:03:43 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B997CDBF32
+ for <de...@maven.apache.org>; Mon, 25 Sep 2017 13:03:42 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -0.021
+X-Spam-Level:
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=6.31
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
+ KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7,
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
+ autolearn=disabled
+Authentication-Results: spamd1-us-west.apache.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=ifedorenko.com header.b=bkCVtpJK;
+ dkim=pass (2048-bit key) header.d=messagingengine.com
+ header.b=dW/lUplK
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024)
+ with ESMTP id rGtgUf6NpDxU for <de...@maven.apache.org>;
+ Mon, 25 Sep 2017 13:03:39 +0000 (UTC)
+Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4440260E4C
+ for <de...@maven.apache.org>; Mon, 25 Sep 2017 13:03:39 +0000 (UTC)
+Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
+ by mailout.nyi.internal (Postfix) with ESMTP id 99E3820C4A
+ for <de...@maven.apache.org>; Mon, 25 Sep 2017 09:03:37 -0400 (EDT)
+Received: from web2 ([10.202.2.212])
+ by compute2.internal (MEProxy); Mon, 25 Sep 2017 09:03:37 -0400
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ifedorenko.com;
+ h=content-transfer-encoding:content-type:date:from:in-reply-to
+ :message-id:mime-version:references:subject:to:x-me-sender
+ :x-me-sender:x-sasl-enc; s=fm1; bh=1y+Nlq0uk2dCgTgHJzm58wL7idWJd
+ ZZ8I/3vYuGbHNc=; b=bkCVtpJKI+FiiSq+SqJxwe87L55ceQ+zCKGznSyjzG/77
+ 36awYn1jNitaT72vOn4Yog0E2pAe1xDZrHWs7/R992dZXX2pF3DY0ad+3ipmjftI
+ mLpTFWVXHtl6m4n6y2/3I57aH4roZdqfhbP0aoVR8bKiA3HGtx4uRHs4uCfHPF5a
+ GL51p4aeNBdiSoT4MUvw6FmDZc2TrdPjuAYINUD+0pSs2HLmAqK18pP+vfK2wyWl
+ rZW1xH1dqBjTchI3q5TV2FpVsU9sMZ7mRfCr7asRkA8TTc3w8WC9jsKfE6lhAvLP
+ g0+fUSZVt+bWdm4+oxKfaIpPnpGe/qG7DfSmuCpMg==
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
+ messagingengine.com; h=content-transfer-encoding:content-type
+ :date:from:in-reply-to:message-id:mime-version:references
+ :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1y+Nlq
+ 0uk2dCgTgHJzm58wL7idWJdZZ8I/3vYuGbHNc=; b=dW/lUplKfFTn75YTAQlt7Q
+ AYnR6CWgpqu4SWiMjjGZjJ4/jCqAEKbb+ErDsrTGGfDw8yckmB8C1q7P90yvhXe0
+ /Sf5qRq5MiH/eIyWXjlwzg4d93rM3P8QXph96V+lKkWlUcv9L/E38I1MM63lw8KA
+ C+WnB9X7YwHX9uaub97rT5FqI22/6Vl3ZfJg07kNC4T+Dbz5xIGt8r7YTWvJ7bjF
+ HSKQTijKaIVNpfgs7ckeYgG67KAIAGBkcmG4fSGMCqoffV13/0I1rESbAHEFcirx
+ H/KbVkd0DrtVp7qB2CsqDkN0WRasu+oEWOZ1JP94uxFN/FiJFxyg0xe3pKBqt+Ow
+ ==
+X-ME-Sender: <xms:qf7IWZsZzdxUfppSBUdnNFCNBcSJqVFM1sL8HWL_PZ5N1XZjCt5Hrw>
+Received: by mailuser.nyi.internal (Postfix, from userid 99)
+ id 5F338626A2; Mon, 25 Sep 2017 09:03:37 -0400 (EDT)
+Message-Id: <15...@webmail.messagingengine.com>
+From: Igor Fedorenko <ig...@ifedorenko.com>
+To: dev@maven.apache.org
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="utf-8"
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-64b08692
+Subject: Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)
+Date: Mon, 25 Sep 2017 09:03:37 -0400
+In-Reply-To: <CA...@mail.gmail.com>
+References: <CA...@mail.gmail.com>
+ <F1...@honton.org>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <op...@desktop-2khsk44.dynamic.ziggo.nl>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+ <15...@webmail.messagingengine.com>
+ <CA...@mail.gmail.com>
+archived-at: Mon, 25 Sep 2017 13:03:46 -0000
+
+See inline
+
+
+On Sun, Sep 24, 2017, at 03:37 PM, Stephen Connolly wrote:
+> Right now I have a successful vote to release 3.5.1
+>=20
+
+[snip]
+
+> Now I see 6209 changing the classloader for plugins that are also build
+> extensions... the question here is two fold:
+>=20
+> 1. Is the new behaviour *correct* or just *less wrong*?
+> 2. If =E2=80=9Cless wrong=E2=80=9D, is it less wrong on the same side of =
+correct as the
+> old
+> behaviour, or is it less wrong on the other side of correct?
+
+6209 does not change plugin classloading per se, but it does change TCCL
+used when running mojos from extensions=3Dtrue plugins.
+
+I believe the new *behaviour* is correct, that is, components from
+extensions=3Dtrue plugins should be used consistently with or without
+other extensions present. Think of a custom wagon or packaging type,
+it'd be very surprising if these component were ignored when running
+mojos from other extensions=3Dtrue plugins.
+
+I also believe changing TCCL is the only way to implement the correct
+behaviour given how Sisu locates components, but I am open to other
+ideas. I also think that extensions=3Dtrue plugins are a relative
+minority, we only had single problem exposed by the TCCL change (root
+cause being a bug in assembly-plugin), so I wonder if we are
+otherthinking this.
+
+https://issues.apache.org/jira/browse/MNG-6209
+
+> The other one is 6275 changing the TCCL. We have site documentation
+> *stating* that TCCL will be the plugin classloader, and we are changing
+> now
+> so that TCCL is not.
+
+
+6275 does not change TCCL, it changes classloader parent hierarchy.
+Still a big change, especially for applications that embed Maven, but I
+think current implementation falls into "less wrong" category too but it
+is likely the best we can do to support ServiceLoaderFactory and java9
+(without completely redesigning and reimplementing Maven classloading,
+at least).
+
+https://issues.apache.org/jira/browse/MNG-6275
+
+> 3. Which do we need to fix: site or code?
+> 4. Are we sure we can guarantee that the plugin classloader is always the
+> classloader that loaded the plugin class: what if I have plugin A
+> dependends on Plugin B (not what i=E2=80=99d recommend, but users do crazy
+> things)
+> so we have the mojos in Plugin B coming from a jar dependency of Plugin
+> A... so could we then we have layered classloaders in which case when I
+> invoke A:mojo-from-b will it be loaded by A=E2=80=99s classloader or a pa=
+rent of
+> A
+> that hold the B jar?
+
+I don't believe this behaviour changed in 3.5.1. We don't guarantee
+mojos are always loaded from plugin classloader, but we do guarantee
+mojos implementation is looked up in plugin classloader first (see
+DefaultMavenPluginManager.getConfiguredMojo). We could validate mojo
+classloader =3D=3D plugin classloader and fail the build if that's not the
+case, but I don't see the advantages such check would provide.
+
+> Or what if I were to use an extension to provide the mojo but advertising
+> the extension=E2=80=99s mojo class via a plugin?
+
+This can only happen the mojo is declared in plugin
+META-INF/maven/plugin.xml, which means the plugin authors made
+deliberate effort to enable such arrangement and I currently don't see
+why we should attempt to block it.
+
+>=20
+> These are all *really* stupid things in my opinion, but we haven=E2=80=99=
+t said
+> =E2=80=9Cthou shalt not expose mojos from other jar files=E2=80=9D so som=
+eone *could*
+> have
+> done it... how are they to get the plugin classloader now that 6275 is
+> landing? (I think a component of type classloader with a role-hint of
+> =E2=80=9Cplugin=E2=80=9D would make sense to me)
+>=20
+> Alternatively, we document =E2=80=9Cthou shalt not=E2=80=9D and be done w=
+ith it...
+>=20
+> But these are the kinds of things we need to resolve before I feel I can
+> close the 3.5.1 vote one way or another.
+>=20
+>=20
+
+
+--=20
+Regards,
+Igor
+
+
+> On Sun 24 Sep 2017 at 20:06, Igor Fedorenko <ig...@ifedorenko.com> wrote:
+>=20
+> > Lets decide the agenda first, then who you need to attend (assuming you
+> > are driving this discussion/decision), then pick the time that works.
+> >
+> > From my side, I still don't understand the problems we are trying to
+> > solve. If this is the lacking documentation and general "uncomfort" to
+> > mess with classloading in bug fix release, then maybe do what Anders
+> > suggests (I think), bump the version to 3.6.0, document the behaviour we
+> > have on master and move on.
+> >
+> > --
+> > Regards,
+> > Igor
+> >
+> > On Sun, Sep 24, 2017, at 02:28 PM, Stephen Connolly wrote:
+> > > I wonder should we do a hangout to decide what you do?
+> > >
+> > > What times on Monday work best?
+> > >
+> > > I can maybe do 8:30-9:30pm Irish time
+> > >
+> > >
+> > https://www.timeanddate.com/worldclock/meetingdetails.html?year=3D2017&=
+month=3D9&day=3D25&hour=3D19&min=3D30&sec=3D0&p1=3D78&p2=3D37&p3=3D179
+> > >
+> > > But we=E2=80=99d need to decide who we need and an actual agenda.
+> > >
+> > > If Monday is too soon I can see if I have a window later this week
+> > >
+> > > On Sun 24 Sep 2017 at 18:58, Igor Fedorenko <ig...@ifedorenko.com> wro=
+te:
+> > >
+> > > > See my answers/comments inline
+> > > >
+> > > >
+> > > > On Sun, Sep 24, 2017, at 12:07 PM, Stephen Connolly wrote:
+> > > > > https://maven.apache.org/guides/mini/guide-maven-classloading.html
+> > says:
+> > > > >
+> > > > > > When a build plugin is executed, the thread's context classload=
+er
+> > is
+> > > > set
+> > > > > to the plugin classloader.
+> > > > >
+> > > > > So we'll need to fix something somewhere...
+> > > > >
+> > > > >
+> > > >
+> > https://svn.apache.org/repos/infra/websites/production/maven/content/re=
+ference/maven-classloading.html
+> > > > > is unaccessible from the website due to a rewrite rule...
+> > > > >
+> > > > > Things that seem to be missing:
+> > > > >
+> > > > > * What is the desired classloading for a plugin that is marked as=
+ an
+> > > > > extension? Can a plugin have a META-INF/maven/extension.xml to al=
+low
+> > > > > exporting classes and artifacts when used as an extension? How
+> > should the
+> > > > > classloading look for such a strange beast.
+> > > >
+> > > > To me, the key requirement is that @Singleton components and class
+> > > > static members are singletons when injected in Maven core or in @Mo=
+jos.
+> > > > This implies that there should be single classloader representing an
+> > > > extensions plugins (MNG-5742).
+> > > >
+> > > > META-INF/maven/extension.xml declares what packages of the extension
+> > > > plugin are visible to other (non extension) plugins.
+> > > > META-INF/maven/extension.xml does not affect classloading of the
+> > > > extension plugin nor it affects the "shape" of other classloaders.
+> > > >
+> > > > > * How does one access the plugin classloader if we want TCCL to be
+> > other
+> > > > > than that, is it a Dependency Injection or something else?
+> > > >
+> > > > this.getClass().getClassLoader() is the most direct way to access
+> > plugin
+> > > > classloader. Why do you think we need anything more elaborate?
+> > > >
+> > > >
+> > > > > * What differentiates a Core extension from a Build extension (is=
+ it
+> > that
+> > > > > a
+> > > > > build extension lacks a META-INF/maven/extension.xml and was only
+> > > > > declared
+> > > > > in the pom.xml, while a core extension either has a
+> > > > > META-INF/maven/extension.xml - if declared in the pom - or is an
+> > > > > extension
+> > > > > declared in .mvn/extensions.xml)
+> > > >
+> > > > Core extensions are loaded *before* build starts, so they can
+> > contribute
+> > > > AbstractMavenLifecycleParticipant#afterSessionStart, for example. T=
+hey
+> > > > can also export packages visible to all build plugins, including
+> > > > extensions=3Dtrue. On the flip side, each core extension is effecti=
+vely
+> > > > singleton, you can't have two different versions of the same Core
+> > > > extension. Core extensions also have direct access to Maven core
+> > classes
+> > > > and can do more interesting things there (for better or worse).
+> > > >
+> > > > Build extensions are part of the project build and as such are limi=
+ted
+> > > > what components they can contribute to the Core and what core class=
+es
+> > > > they have access to.
+> > > >
+> > > > I tried to capture this in the diagram I drew for
+> > > > http://takari.io/book/91-maven-classloading.html.
+> > > >
+> > > > > At this point in time I think we are nearing the point where I may
+> > have
+> > > > > to
+> > > > > declare 3.5.1 abandoned as I think the classloading in that is a
+> > symptom
+> > > > > of
+> > > > > too many cooks all changing things in different directions. We ne=
+ed a
+> > > > > consistent vision of where we want things to go and - while we ne=
+ed
+> > not
+> > > > > get
+> > > > > there in one go - the path presented for others to see.
+> > > >
+> > > > There were two classloading changes in 3.5.1, namely extensions=3Dt=
+rue
+> > > > plugins now have project realm as TCCL and all realms now use
+> > > > application classloader as the parent. Apart from lacking
+> > documentation,
+> > > > what practical problems have been caused by these two changes?
+> > > >
+> > > > >
+> > > > > Things I think we should consider:
+> > > > >
+> > > > > 1. Do we want to formally deprecate Build Extensions and the
+> > > > > /project/build/extensions element (start logging warnings, etc)?
+> > > > > 2. Do we want to formally deprecate plugins as extensions and sta=
+rt
+> > > > > logging
+> > > > > warnings for
+> > > > >
+> > > >
+> > /project/build/(pluginManagement|.)/plugins/plugin/extensions[text()=3D=
+=3Dtrue]
+> > > >
+> > > > I'd keep them both, and maybe fix/remove maven2-compat codepath. If=
+ I
+> > > > had to choose between the two, however, I'd choose <plugin> with
+> > > > extensions=3Dtrue. Think of a custom packaging type with mojos the =
+user
+> > > > wants to configure in pom.xml, it'd be more tedious to configure if=
+ I
+> > > > had to add build/extension and build/plugin.
+> > > >
+> > > > > 3. What is the difference in classloading for a
+> > /project/build/extensions
+> > > > > which has a META-INF/maven/extension.xml and one that doesn't?
+> > > >
+> > > > I think extensions with META-INF/maven/extension.xml should not go
+> > > > through maven2-compat codepath. In other words, we need to change t=
+he
+> > > > current behaviour.
+> > > >
+> > > > Extensions without META-INF/maven/extension.xml... I am not sure.
+> > > > Probably safer to keep the current maven2-compat behaviour.
+> > > >
+> > > > > I'm keeping the 3.5.1 release in staging until we get a clear vis=
+ion
+> > for
+> > > > > how we want to have classloading so that I can assess whether the
+> > 3.5.1
+> > > > > actuality is only moving nearer to the vision (ok to release) or =
+has
+> > > > > moved
+> > > > > nearer in some ways but further in others (not ok to release)
+> > > > >
+> > > >
+> > > >
+> > > > --
+> > > > Regards,
+> > > > Igor
+> > > >
+> > > >
+> > > >
+> > > > > On 20 September 2017 at 12:44, Igor Fedorenko <igor@ifedorenko.co=
+m>
+> > > > > wrote:
+> > > > >
+> > > > > > Real-world scm or wagon <extensions> won't trigger maven2-compat
+> > code
+> > > > > > path [1]. To avoid that obscure code path we can either make the
+> > test
+> > > > > > more elaborate (i.e. add dependencies to extjar1/extjar2) or we
+> > can use
+> > > > > > extensions <plugin>. Either way I don't think we should spend t=
+ime
+> > on
+> > > > > > the code path unlikely to be used in real life.
+> > > > > >
+> > > > > > [1]
+> > > > > > https://github.com/apache/maven/blob/maven-3.5.1/maven-
+> > > > > >
+> > > >
+> > core/src/main/java/org/apache/maven/project/DefaultProjectBuildingHelpe=
+r.
+> > > > > > java#L210-L219
+> > > > > >
+> > > > > > --
+> > > > > > Regards,
+> > > > > > Igor
+> > > > > >
+> > > > > > On Wed, Sep 20, 2017, at 03:29 AM, Robert Scholte wrote:
+> > > > > > > On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly
+> > > > > > > <st...@gmail.com> wrote:
+> > > > > > >
+> > > > > > > > On Wed 20 Sep 2017 at 01:29, Igor Fedorenko <
+> > igor@ifedorenko.com>
+> > > > > > wrote:
+> > > > > > > >
+> > > > > > > >> In that case, can I suggest couple of changes to the test
+> > project
+> > > > > > > >>
+> > > > > > > >> * I thinks it makes more sense to configure extjar1 and
+> > extjar2 as
+> > > > > > > >> extensions <plugin> elements in probleN pom.xml files. Fir=
+st,
+> > > > there is
+> > > > > > > >> no meaningful order between <extensions> and <plugins>
+> > elements.
+> > > > More
+> > > > > > > >> importantly, though, simple <extensions> are treated in
+> > special
+> > > > > > > >> maven2-compat mode and are not representative of likely
+> > real-world
+> > > > > > > >> extensions.
+> > > > > > > >
+> > > > > > >
+> > > > > > > Not sure I agree with this. I think there are jars worth shar=
+ing
+> > > > across
+> > > > > > > multiple plugins, but where making the plugin an extension is=
+ a
+> > bit
+> > > > > > > weird.
+> > > > > > > I'm thinking of scm and wagon in this case.
+> > > > > > >
+> > > > > > > >
+> > > > > > > > That sounds like we need documentation updated then. None of
+> > that
+> > > > is
+> > > > > > > > obvious to me.
+> > > > > > > >
+> > > > > > > >
+> > > > > > > >>
+> > > > > > > >> * I think we should introduce META-INF/maven/extension.xml=
+ to
+> > the
+> > > > test
+> > > > > > > >> extensions. This metadata what introduced to configure
+> > classpath
+> > > > > > > >> visibility, so lets use it.
+> > > > > > > >
+> > > > > > > >
+> > > > > > > > Again, not obvious to me, if that file allows control of
+> > classpath
+> > > > > > > > visibility then it may be that the only issue *with* 3.5.1 =
+is
+> > the
+> > > > lack
+> > > > > > of
+> > > > > > > > documentation... now previous versions would have been addi=
+ng
+> > > > breaking
+> > > > > > > > changes from my PoV but that is the past and should not aff=
+ect
+> > the
+> > > > > > 3.5.1
+> > > > > > > > release.
+> > > > > > > >
+> > > > > > > > PRs for the probe project welcome. I am happy to try and wr=
+ite
+> > docs
+> > > > > > once
+> > > > > > > > I
+> > > > > > > > have an understanding of what the expected behaviours are
+> > > > > > > >
+> > > > > > > >
+> > > > > > > >>
+> > > > > > > >> --
+> > > > > > > >> Regards,
+> > > > > > > >> Igor
+> > > > > > > >>
+> > > > > > > >> On Tue, Sep 19, 2017, at 05:12 PM, Stephen Connolly wrote:
+> > > > > > > >> > Yes, the expectations are key. Depending on what they are
+> > we may
+> > > > > > > >> either
+> > > > > > > >> > drop 3.5.1 or go ahead as it depends on whether this is =
+more
+> > > > correct
+> > > > > > > >> than
+> > > > > > > >> > 3.5.0 or swapping one fix for a bug
+> > > > > > > >> >
+> > > > > > > >> > On Tue 19 Sep 2017 at 21:39, Igor Fedorenko <
+> > > > igor@ifedorenko.com>
+> > > > > > > >> wrote:
+> > > > > > > >> >
+> > > > > > > >> > > Just to confirm I understand what we are trying to
+> > establish
+> > > > here.
+> > > > > > > >> We
+> > > > > > > >> > > want to decide the expected/desired component injection
+> > > > behaviour
+> > > > > > > >> and
+> > > > > > > >> > > classpath visibility in the absence of package and
+> > artifact
+> > > > export
+> > > > > > > >> > > configuration (i.e. META-INF/maven/extension.xml file).
+> > Did I
+> > > > get
+> > > > > > > >> this
+> > > > > > > >> > > right?
+> > > > > > > >> > >
+> > > > > > > >> > > --
+> > > > > > > >> > > Regards,
+> > > > > > > >> > > Igor
+> > > > > > > >> > >
+> > > > > > > >> > > On Tue, Sep 19, 2017, at 03:52 PM, Robert Scholte wrot=
+e:
+> > > > > > > >> > > > Let's do it like this:
+> > > > > > > >> > > >
+> > > > > > > >> > >
+> > > > > > > >>
+> > https://cwiki.apache.org/confluence/download/attachments/2329841/
+> > > > > > classrealms.pdf?api=3Dv2
+> > > > > > > >> > > >
+> > > > > > > >> > > > Robert
+> > > > > > > >> > > >
+> > > > > > > >> > > > On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly
+> > > > > > > >> > > > <st...@gmail.com> wrote:
+> > > > > > > >> > > >
+> > > > > > > >> > > > > I think you will need a link to the PDF as
+> > attachments are
+> > > > > > > >> stripped
+> > > > > > > >> > > from
+> > > > > > > >> > > > > the ML
+> > > > > > > >> > > > >
+> > > > > > > >> > > > > On Tue 19 Sep 2017 at 19:57, Robert Scholte
+> > > > > > > >> <rf...@apache.org>
+> > > > > > > >> > > wrote:
+> > > > > > > >> > > > >
+> > > > > > > >> > > > >> Attached a single page overview.
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> Per block you'll see in the upper left corner the
+> > > > executed
+> > > > > > > >> plugin
+> > > > > > > >> > > > >> The left column contains the extensions and plugi=
+n in
+> > > > orderas
+> > > > > > > >> > > specified
+> > > > > > > >> > > > >> in
+> > > > > > > >> > > > >> the pom.xml
+> > > > > > > >> > > > >> In every classloadercolumn you'll see numbers whi=
+ch
+> > > > represent
+> > > > > > > >> the
+> > > > > > > >> > > order.
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> I hope I didn't make any mistakes.
+> > > > > > > >> > > > >> Tomorrow I have enough time to see if I understand
+> > what's
+> > > > > > > >> happening
+> > > > > > > >> > > > >> here.
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> I will come back with my conclusions.
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> Robert
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> On Tue, 19 Sep 2017 06:55:08 +0200, Igor Fedorenk=
+o <
+> > > > > > > >> > > igor@ifedorenko.com>
+> > > > > > > >> > > > >> wrote:
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >> > TL;DR your test project exposed two existing bu=
+gs,
+> > one
+> > > > > > > >> change in
+> > > > > > > >> > > > >> > behaviour and one quirk I can't explain
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > * Build `<extensions>` are loaded by two
+> > classloaders,
+> > > > > > which
+> > > > > > > >> is
+> > > > > > > >> a
+> > > > > > > >> > > bug
+> > > > > > > >> > > > >> in
+> > > > > > > >> > > > >> > DefaultProjectBuildingHelper#createProjectRealm=
+ and
+> > > > > > explains
+> > > > > > > >> why you
+> > > > > > > >> > > > >> see
+> > > > > > > >> > > > >> > extjar1/extjar2 in the output
+> > > > > > > >> > > > >> > * ClassRealm does not allow same foreign-import
+> > from
+> > > > > > multiple
+> > > > > > > >> > > > >> > classloaders, which is a bug and explains why it
+> > is not
+> > > > > > > >> possible to
+> > > > > > > >> > > > >> load
+> > > > > > > >> > > > >> > same resource from multiple plugins/extensions
+> > > > > > > >> > > > >> > * TCCL does not have access to private (i.e. not
+> > > > exported)
+> > > > > > > >> resources
+> > > > > > > >> > > > >> of
+> > > > > > > >> > > > >> > this extensions plugin, which is a change of
+> > behaviour
+> > > > > > > >> introduced by
+> > > > > > > >> > > > >> > mng-6209 fix
+> > > > > > > >> > > > >> > * Also, component injection order appears to be
+> > > > backwards,
+> > > > > > > >> but
+> > > > > > > >> maybe
+> > > > > > > >> > > > >> > Stuart can explain why.
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > Below is more detailed explanation of expected =
+and
+> > > > observed
+> > > > > > > >> > > behaviour
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > ## Component injection depends on the currently
+> > running
+> > > > > > > >> plugin
+> > > > > > > >> and
+> > > > > > > >> > > the
+> > > > > > > >> > > > >> > injection site
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > Currently running plugins have access to the
+> > following
+> > > > > > > >> component
+> > > > > > > >> > > > >> > implementations:
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > * Regular plugin has access to components
+> > implemented
+> > > > by
+> > > > > > the
+> > > > > > > >> plugin,
+> > > > > > > >> > > > >> > project build extensions, if any (via project c=
+lass
+> > > > realm
+> > > > > > > >> foreign
+> > > > > > > >> > > > >> > import) and Maven Core.
+> > > > > > > >> > > > >> > * Extension plugin has access to components
+> > > > implemented by
+> > > > > > > >> the
+> > > > > > > >> > > project
+> > > > > > > >> > > > >> > build extensions and Maven Core.
+> > > > > > > >> > > > >> > * Without a running plugin (e.g., during project
+> > > > dependency
+> > > > > > > >> > > > >> resolution),
+> > > > > > > >> > > > >> > components implemented by the project build
+> > extensions
+> > > > and
+> > > > > > > >> Maven
+> > > > > > > >> > > Core
+> > > > > > > >> > > > >> > are accessible.
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > Different injection sites have access to the
+> > following
+> > > > > > > >> component
+> > > > > > > >> > > > >> > interfaces:
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > * Maven Core has access to component interfaces
+> > > > defined by
+> > > > > > > >> the
+> > > > > > > >> core
+> > > > > > > >> > > > >> > itself (obviously)
+> > > > > > > >> > > > >> > * Project build extensions have access to
+> > **public**
+> > > > > > > >> component
+> > > > > > > >> > > > >> > interfaces defined by Maven Core and component
+> > > > interfaces
+> > > > > > > >> defined by
+> > > > > > > >> > > > >> the
+> > > > > > > >> > > > >> > build extension itself (there is no way to acce=
+ss
+> > > > component
+> > > > > > > >> > > interfaces
+> > > > > > > >> > > > >> > defined in other extensions)
+> > > > > > > >> > > > >> > * Regular plugins have access to **public**
+> > component
+> > > > > > > >> interfaces
+> > > > > > > >> > > > >> defined
+> > > > > > > >> > > > >> > by Maven Core, component interfaces **exported*=
+* by
+> > > > build
+> > > > > > > >> extensions
+> > > > > > > >> > > > >> and
+> > > > > > > >> > > > >> > component interfaces defined in the plugin itse=
+lf
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > For injection to work, injection site has to ha=
+ve
+> > > > access to
+> > > > > > > >> the
+> > > > > > > >> > > > >> > component interface and the component
+> > implementation
+> > > > must
+> > > > > > be
+> > > > > > > >> > > > >> accessible
+> > > > > > > >> > > > >> > through the current context.
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > From what I can tell, in your example all plugi=
+ns
+> > have
+> > > > > > access
+> > > > > > > >> to the
+> > > > > > > >> > > > >> > right components when using current
+> > 3.5.2-SNAPSHOT. The
+> > > > > > > >> injection
+> > > > > > > >> > > > >> order
+> > > > > > > >> > > > >> > does appear to be backwards from what I expecte=
+d,
+> > > > however.
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > ## Resources lookup fully depends on classpath
+> > > > visibility,
+> > > > > > > >> > > > >> specifically
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > * Regular plugin class realm has access to
+> > resources
+> > > > from
+> > > > > > the
+> > > > > > > >> plugin
+> > > > > > > >> > > > >> > itself, from **exported** packages of the proje=
+ct
+> > build
+> > > > > > > >> extensions
+> > > > > > > >> > > and
+> > > > > > > >> > > > >> > **public** Maven Core packages
+> > > > > > > >> > > > >> > * Extensions plugin class realm has access to t=
+he
+> > > > resources
+> > > > > > > >> from the
+> > > > > > > >> > > > >> > extensions plugin itself and from **public** Ma=
+ven
+> > Core
+> > > > > > > >> packages
+> > > > > > > >> > > > >> > * Project class realm has access to classes and
+> > > > resources
+> > > > > > > >> > > **exported**
+> > > > > > > >> > > > >> > by project build extensions and **public** Maven
+> > Core
+> > > > > > > >> packages
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > I see three problems here
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > * Maven adds build single-jar `<extensions>`
+> > elements
+> > > > > > > >> directly
+> > > > > > > >> to
+> > > > > > > >> > > > >> > project class realm **and** creates separate
+> > extensions
+> > > > > > class
+> > > > > > > >> realms
+> > > > > > > >> > > > >> for
+> > > > > > > >> > > > >> > them. Which results in duplicate classes/resour=
+ces
+> > > > loaded
+> > > > > > by
+> > > > > > > >> two
+> > > > > > > >> > > > >> > classloaders and explains why you see
+> > extjar1/extjar2
+> > > > > > output
+> > > > > > > >> (which
+> > > > > > > >> > > > >> you
+> > > > > > > >> > > > >> > shouldn't according to the explanation above)
+> > > > > > > >> > > > >> > * ClassRealm does not allow foreign-import of t=
+he
+> > same
+> > > > > > > >> package
+> > > > > > > >> from
+> > > > > > > >> > > > >> > multiple classloaders. This makes it impossible=
+ to
+> > > > load the
+> > > > > > > >> same
+> > > > > > > >> > > > >> > resource from multiple plugins/extensions.
+> > > > > > > >> > > > >> > * Extensions plugins cannot access their own
+> > private
+> > > > (i.e.
+> > > > > > > >> not
+> > > > > > > >> > > > >> exported)
+> > > > > > > >> > > > >> > resources via TCCL, this is change in behaviour
+> > > > introduced
+> > > > > > by
+> > > > > > > >> > > mng-6209
+> > > > > > > >> > > > >> > fix
+> > > > > > > >> > > > >> >
+> > > > > > > >> > > > >> > Hope this helps
+> > > > > > > >> > > > >>
+> > > > > > > >> > > > >>
+> > > > > > > >>
+> > > > -------------------------------------------------------------------=
+--
+> > > > > > > >> > > > >> 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
+> > > > > > > >> > > >
+> > > > > > > >> > >
+> > > > > > > >> > >
+> > > > > > > >>
+> > > > -------------------------------------------------------------------=
+--
+> > > > > > > >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.o=
+rg
+> > > > > > > >> > > For additional commands, e-mail:
+> > dev-help@maven.apache.org
+> > > > > > > >> > >
+> > > > > > > >> > > --
+> > > > > > > >> > Sent from my phone
+> > > > > > > >>
+> > > > > > > >>
+> > > > -------------------------------------------------------------------=
+--
+> > > > > > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > > > > >> For additional commands, e-mail: dev-help@maven.apache.org
+> > > > > > > >>
+> > > > > > > >> --
+> > > > > > > > Sent from my phone
+> > > > > > >
+> > > > > > >
+> > ---------------------------------------------------------------------
+> > > > > > > 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
+> > > > > >
+> > > > > >
+> > > >
+> > > > -------------------------------------------------------------------=
+--
+> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > > >
+> > > > --
+> > > Sent from my phone
+> >
+> > ---------------------------------------------------------------------
+> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > For additional commands, e-mail: dev-help@maven.apache.org
+> >
+> > --
+> Sent from my phone
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id ED4EB200D36
+ for <ar...@cust-asf2.ponee.io>; Mon, 23 Oct 2017 00:15:50 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id EBBA2160BEF; Sun, 22 Oct 2017 22:15:50 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 158A5160BD7
+ for <ar...@cust-asf.ponee.io>; Mon, 23 Oct 2017 00:15:49 +0200 (CEST)
+Received: (qmail 15192 invoked by uid 500); 22 Oct 2017 22:15:44 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 15181 invoked by uid 99); 22 Oct 2017 22:15:43 -0000
+Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Oct 2017 22:15:43 +0000
+Received: from localhost (localhost [127.0.0.1])
+ by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 30F0E180705
+ for <de...@maven.apache.org>; Sun, 22 Oct 2017 22:15:43 +0000 (UTC)
+X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
+X-Spam-Flag: NO
+X-Spam-Score: -1
+X-Spam-Level:
+X-Spam-Status: No, score=-1 tagged_above=-999 required=6.31
+ tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1,
+ RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=disabled
+Received: from mx1-lw-eu.apache.org ([10.40.0.8])
+ by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
+ with ESMTP id cl-kpRYqLLXG for <de...@maven.apache.org>;
+ Sun, 22 Oct 2017 22:15:40 +0000 (UTC)
+Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129])
+ by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4518E5F306
+ for <de...@maven.apache.org>; Sun, 22 Oct 2017 22:15:40 +0000 (UTC)
+Received: from giga.localnet ([86.238.16.93])
+ by mwinf5d14 with ME
+ id QmFa1w00P20Ufdy03mFaxU; Mon, 23 Oct 2017 00:15:34 +0200
+X-ME-Helo: giga.localnet
+X-ME-Date: Mon, 23 Oct 2017 00:15:34 +0200
+X-ME-IP: 86.238.16.93
+From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <he...@free.fr>
+To: Maven Developers List <de...@maven.apache.org>
+Subject: Re: migrating some code to Git
+Date: Mon, 23 Oct 2017 00:15:34 +0200
+Message-ID: <15...@giga>
+In-Reply-To: <CA...@mail.gmail.com>
+References: <30...@giga> <CA...@mail.gmail.com> <CA...@mail.gmail.com>
+MIME-Version: 1.0
+Content-Transfer-Encoding: quoted-printable
+Content-Type: text/plain; charset="iso-8859-1"
+archived-at: Sun, 22 Oct 2017 22:15:51 -0000
+
+I'm happy to do what I'm able to do
+
+for the next ones, I fear I don't know how to prepare target git repos: I'l=
+l=20
+need help
+
+Regards,
+
+Herv=E9
+
+Le dimanche 22 octobre 2017, 23:26:44 CEST Olivier Lamy a =E9crit :
+> Great!
+> Thanks to take care of this!
+>=20
+> On Mon, 23 Oct 2017 at 7:00 am, Arnaud H=E9ritier <ah...@gmail.com> w=
+rote:
+> > Awesome !
+> >=20
+> > On Sun, Oct 22, 2017 at 12:00 PM, Robert Scholte <rf...@apache.org>
+> >=20
+> > wrote:
+> > > Great job, thank you all!
+> > >=20
+> > > Robert
+> > >=20
+> > >=20
+> > > On Sun, 22 Oct 2017 11:45:02 +0200, Herv=E9 BOUTEMY <herve.boutemy@fr=
+ee.fr
+> > >=20
+> > > wrote:
+> > >=20
+> > > migration done: only remaining task is to rename "trunk" HEAD branch
+> > >=20
+> > >> inherited
+> > >> from svn history to "master" (and eventually add a MOVED_TO_GIT file=
+ in
+> > >> origin
+> > >> svn)
+> > >>=20
+> > >> The Apache git hosting provided is GitBox, unlike previous component
+> >=20
+> > that
+> >=20
+> > >> use
+> > >> Git-Wip: with GitBox, the content is modifiable both at ASF git repo
+> > >> and
+> > >> GitHub
+> > >> mirror
+> > >> You'll need some config on your side if you want to be able to push
+> > >> directly to
+> > >> GitHub: see https://gitbox.apache.org/setup/
+> > >>=20
+> > >> Thanks to infra Chris Lambertus for doing the job for us
+> > >>=20
+> > >> Regards,
+> > >>=20
+> > >> Herv=E9
+> > >>=20
+> > >> Le mardi 10 octobre 2017, 18:42:26 CEST Herv=E9 BOUTEMY a =E9crit :
+> > >>> jira issue created:
+> > >>> https://issues.apache.org/jira/browse/INFRA-15253
+> > >>>=20
+> > >>> Regards,
+> > >>>=20
+> > >>> Herv=E9
+> > >>>=20
+> > >>> Le samedi 7 octobre 2017, 12:32:00 CEST Herv=E9 BOUTEMY a =E9crit :
+> > >>> > I wrote a little shell script to check differences between tags in
+> >=20
+> > svn
+> >=20
+> > >>> and
+> > >>>=20
+> > >>> > git checkout
+> > >>> > the only differences I found for the 6 git repos are:
+> > >>> > 1. empty dirs (which exist in svn but are pruned in git)
+> > >>> > 2. one strage case in enforcer-1.2 where a few files seem to have
+> > >>>=20
+> > >>> newlines
+> > >>>=20
+> > >>> > issues
+> > >>> >=20
+> > >>> > to me, this can be safely ignored
+> > >>> >=20
+> > >>> > if nobody objects, in 72h, I'll create INFRA jira issue to switch
+> > >>> > following
+> > >>> > 6 components from svn to the current git mirror:
+> > >>> > - Doxia core
+> > >>> > - Doxia Sitetools
+> > >>> > - Enforcer
+> > >>> > - Jxr
+> > >>> > - Plugin Tools
+> > >>> > - Release
+> > >>> >=20
+> > >>> >=20
+> > >>> > Regards,
+> > >>> >=20
+> > >>> > Herv=E9
+> > >>> >=20
+> > >>> > Le samedi 7 octobre 2017, 04:47:32 CEST Herv=E9 BOUTEMY a =E9crit=
+ :
+> > >>> > > re-reading our migration process documentation [1], I see "check
+> > >>> > > especially
+> > >>> > > behaviour on checking out tag"
+> > >>> > >=20
+> > >>> > > I suppose that we could compare content between git checkout and
+> >=20
+> > svn
+> >=20
+> > >>> > > checkout for HEAD and every past release
+> > >>> > >=20
+> > >>> > > did somebody prepare a shell script for that?
+> > >>> > >=20
+> > >>> > > Regards,
+> > >>> > >=20
+> > >>> > > Herv=E9
+> > >>> > >=20
+> > >>> > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git
+> > >>> > > +Migration#GitMigration-Migrationprocessdescription
+> > >>> > >=20
+> > >>> > > Le vendredi 6 octobre 2017, 00:34:11 CEST Herv=E9 BOUTEMY a =E9=
+crit :
+> > >>> > > > great, thank you for your help
+> > >>> > > >=20
+> > >>> > > > in fact, AFAIK, Apache has already automatic svn2git exports =
+[1]
+> > >>>=20
+> > >>> that
+> > >>>=20
+> > >>> > > > are
+> > >>> > > > then mirrored to github.
+> > >>> > > > Then we already have:
+> > >>> > > > - https://github.com/apache/maven-doxia/
+> > >>> > > > - https://github.com/apache/maven-doxia-sitetools/
+> > >>> > > > - https://github.com/apache/maven-enforcer/
+> > >>> > > > - https://github.com/apache/maven-jxr/
+> > >>> > > > - https://github.com/apache/maven-plugin-tools/
+> > >>> > > > - https://github.com/apache/maven-release/
+> > >>> > > >=20
+> > >>> > > > I suppose these could be the natural targets.
+> > >>> > > > But I don't really see what checks to do on these.
+> > >>> > > >=20
+> > >>> > > > I suppose that once we are convinced this content is ok, we c=
+an
+> >=20
+> > ask
+> >=20
+> > >>> > > > infra
+> > >>> > > > to switch these to the canonical source (and disable the svn2=
+git
+> > >>> > > > exports)
+> > >>> > > >=20
+> > >>> > > > Do you see any issue in these repos?
+> > >>> > > >=20
+> > >>> > > > Regards,
+> > >>> > > >=20
+> > >>> > > > Herv=E9
+> > >>> > > >=20
+> > >>> > > > [1] http://git.apache.org/
+> > >>> > > >=20
+> > >>> > > > Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a
+> >=20
+> > =E9crit :
+> > >>> > > > > Count me in (for both actual migration and related tasks).
+> > >>> > > > >=20
+> > >>> > > > > My weapon of choice for SVN -->>GIT would be:
+> > >>> > > > > https://github.com/nirvdrum/svn2git (I managed to move dozen
+> >=20
+> > of
+> >=20
+> > >>> > > > > repos
+> > >>> > > > > few
+> > >>> > > > > years ago).
+> > >>> > > > >=20
+> > >>> > > > > Regards,
+> > >>> > > > > Dejan
+> > >>> > > > >=20
+> > >>> > > > > On 2017-10-04 01:48, Herv=C3=A9 BOUTEMY <herve.boutemy@free=
+=2Efr>
+> > >>>=20
+> > >>> wrote:
+> > >>> > > > > > I'd like to work on Plugin Tools with git
+> > >>> > > > > >=20
+> > >>> > > > > > While at it, looking at our plan [1], I see we have a few
+> >=20
+> > other
+> >=20
+> > >>> > > > > > components
+> > >>> > > > > > that are ready to migrate:
+> > >>> > > > > > - Doxia core
+> > >>> > > > > > - Doxia Sitetools
+> > >>> > > > > > - Enforcer
+> > >>> > > > > > - Jxr
+> > >>> > > > > > - Plugin Tools
+> > >>> > > > > > - Release
+> > >>> > > > > >=20
+> > >>> > > > > > What checks are required before switching these 6
+> > >>> > > > > > components?
+> > >>> > > > > > Any volunteer?
+> > >>> > > > > >=20
+> > >>> > > > > > Regards,
+> > >>> > > > > >=20
+> > >>> > > > > > Herv=C3=A9
+> > >>> > > > > >=20
+> > >>> > > > > > [1]
+> > >>> > > > > > https://cwiki.apache.org/confluence/display/MAVEN/Git+Mig=
+rat
+> > >>>=20
+> > >>> ion
+> > >>>=20
+> > >>> > > > > > ---------------------------------------------------------=
+=2D--
+> > >>>=20
+> > >>> ------
+> > >>>=20
+> > >>> > > > > > --
+> > >>> > > > > > -
+> > >>> > > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > >>> > > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > >>> > > > >=20
+> > >>> > > > > ------------------------------------------------------------
+> > >>>=20
+> > >>> --------
+> > >>>=20
+> > >>> > > > > -
+> > >>> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > >>> > > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > >>> > > >=20
+> > >>> > > > ------------------------------------------------------------
+> > >>>=20
+> > >>> ---------
+> > >>>=20
+> > >>> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > >>> > > > For additional commands, e-mail: dev-help@maven.apache.org
+> > >>> > >=20
+> > >>> > > ------------------------------------------------------------
+> > >>>=20
+> > >>> ---------
+> > >>>=20
+> > >>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > >>> > > For additional commands, e-mail: dev-help@maven.apache.org
+> > >>> >=20
+> > >>> > -----------------------------------------------------------------=
+=2D--
+> > >>> > -
+> > >>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+> > >>> > For additional commands, e-mail: dev-help@maven.apache.org
+> > >>>=20
+> > >>> -------------------------------------------------------------------=
+=2D-
+> > >>> 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
+> >=20
+> > --
+> > -----
+> > Arnaud H=E9ritier
+> > http://aheritier.net
+> > Mail/GTalk: aheritier AT gmail DOT com
+> > Twitter/Skype : aheritier
+
+
+
+---------------------------------------------------------------------
+To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
+For additional commands, e-mail: dev-help@maven.apache.org
+
+
+From TEST@TEST
+Return-Path: <de...@maven.apache.org>
+X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
+Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
+Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
+ by cust-asf2.ponee.io (Postfix) with ESMTP id C10CE200D28
+ for <ar...@cust-asf2.ponee.io>; Mon, 23 Oct 2017 14:48:01 +0200 (CEST)
+Received: by cust-asf.ponee.io (Postfix)
+ id BF8331609E0; Mon, 23 Oct 2017 12:48:01 +0000 (UTC)
+Delivered-To: archive-asf-public@cust-asf.ponee.io
+Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
+ by cust-asf.ponee.io (Postfix) with SMTP id 1919F1609CE
+ for <ar...@cust-asf.ponee.io>; Mon, 23 Oct 2017 14:47:58 +0200 (CEST)
+Received: (qmail 17390 invoked by uid 500); 23 Oct 2017 12:47:58 -0000
+Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
+Precedence: bulk
+List-Unsubscribe: <ma...@maven.apache.org>
+List-Help: <ma...@maven.apache.org>
+List-Post: <ma...@maven.apache.org>
+List-Id: "Maven Developers List" <dev.maven.apache.org>
+Reply-To: "Maven Developers List" <de...@maven.apache.org>
+Delivered-To: mailing list dev@maven.apache.org
+Received: (qmail 17379 invoked by uid 99); 23 Oct 2017 12:47:57 -0000
+Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70)
+ by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Oct 2017 12:47:57 +0000
+From: GitBox <gi...@apache.org>
+To: dev@maven.apache.org
+Subject: [GitHub] asfgit closed pull request #2: Replace module-markdown pegdown parser to flexmark-java
+Message-ID: <15...@gitbox.apache.org>
+archived-at: Mon, 23 Oct 2017 12:48:01 -0000
+
+asfgit closed pull request #2: Replace module-markdown pegdown parser to flexmark-java
+URL: https://github.com/apache/maven-doxia/pull/2
+
+
+
+
+This is a PR merged from a forked repository.
+As GitHub hides the original diff on merge, it is displayed below for
+the sake of provenance:
+
+As this is a foreign pull request (from a fork), the diff is supplied
+below (as it won't show otherwise due to GitHub magic):
+
+diff --git a/doxia-modules/doxia-module-markdown/pom.xml b/doxia-modules/doxia-module-markdown/pom.xml
+index 45067bd7..ba9bfa14 100644
+--- a/doxia-modules/doxia-module-markdown/pom.xml
++++ b/doxia-modules/doxia-module-markdown/pom.xml
+@@ -38,6 +38,12 @@ under the License.
+
+ <contributors>
+ <contributor>
++ <name>Vladimir Schneider</name>
++ <email>vladimir@vladsch.com</email>
++ <organization>vladsch.com</organization>
++ <organizationUrl>https://vladsch.com/</organizationUrl>
++ </contributor>
++ <contributor>
+ <name>Julien Nicoulaud</name>
+ <email>julien.nicoulaud@gmail.com</email>
+ <timezone>+1</timezone>
+@@ -45,11 +51,15 @@ under the License.
+ </contributor>
+ </contributors>
+
++ <properties>
++ <maven.compiler.target>1.7</maven.compiler.target><!-- required by flexmark -->
++ </properties>
++
+ <dependencies>
+ <dependency>
+- <groupId>org.pegdown</groupId>
+- <artifactId>pegdown</artifactId>
+- <version>1.2.1</version>
++ <groupId>com.vladsch.flexmark</groupId>
++ <artifactId>flexmark-all</artifactId>
++ <version>0.18.4</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.maven.doxia</groupId>
+@@ -60,5 +70,4 @@ under the License.
+ <artifactId>plexus-utils</artifactId>
+ </dependency>
+ </dependencies>
+-
+ </project>
+diff --git a/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaExtension.java b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaExtension.java
+new file mode 100644
+index 00000000..08b269f7
+--- /dev/null
++++ b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaExtension.java
+@@ -0,0 +1,50 @@
++package org.apache.maven.doxia.module.markdown;
++
++/*
++ * Licensed to the Apache Software Foundation (ASF) under one
++ * or more contributor license agreements. See the NOTICE file
++ * distributed with this work for additional information
++ * regarding copyright ownership. The ASF licenses this file
++ * to you under the Apache License, Version 2.0 (the
++ * "License"); you may not use this file except in compliance
++ * with the License. You may obtain a copy of the License at
++ *
++ * http://www.apache.org/licenses/LICENSE-2.0
++ *
++ * Unless required by applicable law or agreed to in writing,
++ * software distributed under the License is distributed on an
++ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
++ * KIND, either express or implied. See the License for the
++ * specific language governing permissions and limitations
++ * under the License.
++ */
++
++import com.vladsch.flexmark.Extension;
++import com.vladsch.flexmark.html.HtmlRenderer;
++import com.vladsch.flexmark.util.options.DataKey;
++import com.vladsch.flexmark.util.options.MutableDataHolder;
++
++/**
++ * Implements flexmark-java extension to render fenced code and indented code using doxia format
++ */
++class MarkdownDoxiaExtension implements HtmlRenderer.HtmlRendererExtension
++{
++ public static final DataKey<String> INPUT_FILE_EXTENSION = new DataKey<String>( "INPUT_FILE_EXTENSION", "md" );
++
++ @Override
++ public void rendererOptions( final MutableDataHolder options )
++ {
++
++ }
++
++ @Override
++ public void extend( HtmlRenderer.Builder rendererBuilder, String rendererType )
++ {
++ rendererBuilder.nodeRendererFactory( new MarkdownDoxiaNodeRenderer.Factory() );
++ }
++
++ public static Extension create()
++ {
++ return new MarkdownDoxiaExtension();
++ }
++}
+diff --git a/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaNodeRenderer.java b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaNodeRenderer.java
+new file mode 100644
+index 00000000..94c710f5
+--- /dev/null
++++ b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownDoxiaNodeRenderer.java
+@@ -0,0 +1,148 @@
++package org.apache.maven.doxia.module.markdown;
++
++/*
++ * Licensed to the Apache Software Foundation (ASF) under one
++ * or more contributor license agreements. See the NOTICE file
++ * distributed with this work for additional information
++ * regarding copyright ownership. The ASF licenses this file
++ * to you under the Apache License, Version 2.0 (the
++ * "License"); you may not use this file except in compliance
++ * with the License. You may obtain a copy of the License at
++ *
++ * http://www.apache.org/licenses/LICENSE-2.0
++ *
++ * Unless required by applicable law or agreed to in writing,
++ * software distributed under the License is distributed on an
++ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
++ * KIND, either express or implied. See the License for the
++ * specific language governing permissions and limitations
++ * under the License.
++ */
++
++import com.vladsch.flexmark.ast.FencedCodeBlock;
++import com.vladsch.flexmark.ast.IndentedCodeBlock;
++import com.vladsch.flexmark.html.CustomNodeRenderer;
++import com.vladsch.flexmark.html.HtmlWriter;
++import com.vladsch.flexmark.html.renderer.NodeRenderer;
++import com.vladsch.flexmark.html.renderer.NodeRendererContext;
++import com.vladsch.flexmark.html.renderer.NodeRendererFactory;
++import com.vladsch.flexmark.html.renderer.NodeRenderingHandler;
++import com.vladsch.flexmark.util.options.DataHolder;
++
++import java.util.Arrays;
++import java.util.HashSet;
++import java.util.Set;
++
++/**
++ * The node renderer that renders all the core nodes (comes last in the order of node renderers).
++ */
++@SuppressWarnings( "WeakerAccess" )
++class MarkdownDoxiaNodeRenderer implements NodeRenderer
++{
++ public MarkdownDoxiaNodeRenderer( DataHolder options )
++ {
++ }
++
++ @Override
++ public Set<NodeRenderingHandler<?>> getNodeRenderingHandlers()
++ {
++ //noinspection unchecked
++ return new HashSet<NodeRenderingHandler<?>>( Arrays.asList(
++ new NodeRenderingHandler<IndentedCodeBlock>( IndentedCodeBlock.class,
++ new CustomNodeRenderer<IndentedCodeBlock>()
++ {
++ @Override
++ public void render( IndentedCodeBlock node, NodeRendererContext context, HtmlWriter html )
++ {
++ MarkdownDoxiaNodeRenderer.this.render( node, context, html );
++ }
++ } ),
++ new NodeRenderingHandler<FencedCodeBlock>( FencedCodeBlock.class,
++ new CustomNodeRenderer<FencedCodeBlock>()
++ {
++ @Override
++ public void render( FencedCodeBlock node, NodeRendererContext context, HtmlWriter html )
++ {
++ MarkdownDoxiaNodeRenderer.this.render( node, context, html );
++ }
++ } )
++ ) );
++ }
++
++ private void render( IndentedCodeBlock node, NodeRendererContext context, HtmlWriter html )
++ {
++ html.line();
++ html.attr( "class", "source" ).tag( "div" );
++ html.srcPosWithEOL( node.getChars() ).withAttr().tag( "pre" ).openPre();
++
++ String noLanguageClass = context.getHtmlOptions().noLanguageClass.trim();
++ if ( !noLanguageClass.isEmpty() )
++ {
++ html.attr( "class", noLanguageClass );
++ }
++
++ //html.srcPosWithEOL(node.getContentChars()).withAttr(CoreNodeRenderer.CODE_CONTENT).tag("code");
++ String s = node.getContentChars().trimTailBlankLines().normalizeEndWithEOL();
++ while ( !s.isEmpty() && s.charAt( 0 ) == '\n' )
++ {
++ html.raw( "<br/>" );
++ s = s.substring( 1 );
++ }
++ html.text( s );
++
++ //html.tag("/code");
++ html.tag( "/pre" ).closePre();
++ html.tag( "/div" );
++ html.line();
++ }
++
++ private void render( FencedCodeBlock node, NodeRendererContext context, HtmlWriter html )
++ {
++ html.line();
++ html.attr( "class", "source" ).tag( "div" );
++ html.srcPosWithTrailingEOL( node.getChars() ).withAttr().tag( "pre" ).openPre();
++
++ //BasedSequence info = node.getInfo();
++ //if (info.isNotNull() && !info.isBlank()) {
++ // int space = info.indexOf(' ');
++ // BasedSequence language;
++ // if (space == -1) {
++ // language = info;
++ // } else {
++ // language = info.subSequence(0, space);
++ // }
++ // html.attr("class", context.getHtmlOptions().languageClassPrefix + language.unescape());
++ //} else {
++ // String noLanguageClass = context.getHtmlOptions().noLanguageClass.trim();
++ // if (!noLanguageClass.isEmpty()) {
++ // html.attr("class", noLanguageClass);
++ // }
++ //}
++
++ //html.srcPosWithEOL(node.getContentChars()).withAttr(CoreNodeRenderer.CODE_CONTENT).tag("code");
++ String s = node.getContentChars().normalizeEOL();
++ while ( !s.isEmpty() && s.charAt( 0 ) == '\n' )
++ {
++ html.raw( "<br/>" );
++ s = s.substring( 1 );
++ }
++ html.text( s );
++
++ //html.tag("/code");
++ html.tag( "/pre" ).closePre();
++ html.tag( "/div" );
++ html.line();
++ }
++
++ /**
++ * Factory for doxia node renderer
++ */
++ public static class Factory implements NodeRendererFactory
++ {
++ @Override
++ public NodeRenderer create( final DataHolder options )
++ {
++ return new MarkdownDoxiaNodeRenderer( options );
++ }
++ }
++}
+diff --git a/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java
+index 336795b2..3ee77bc7 100644
+--- a/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java
++++ b/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java
+@@ -19,6 +19,15 @@
+ * under the License.
+ */
+
++import com.vladsch.flexmark.Extension;
++import com.vladsch.flexmark.ast.Heading;
++import com.vladsch.flexmark.ast.HtmlCommentBlock;
++import com.vladsch.flexmark.ast.Node;
++import com.vladsch.flexmark.ast.util.TextCollectingVisitor;
++import com.vladsch.flexmark.html.HtmlRenderer;
++import com.vladsch.flexmark.profiles.pegdown.Extensions;
++import com.vladsch.flexmark.profiles.pegdown.PegdownOptionsAdapter;
++import com.vladsch.flexmark.util.options.MutableDataHolder;
+ import org.apache.commons.lang.StringEscapeUtils;
+ import org.apache.commons.lang.StringUtils;
+ import org.apache.maven.doxia.markup.HtmlMarkup;
+@@ -31,34 +40,27 @@
+ import org.codehaus.plexus.component.annotations.Requirement;
+ import org.codehaus.plexus.util.IOUtil;
+ import org.codehaus.plexus.util.xml.pull.XmlPullParser;
+-import org.pegdown.Extensions;
+-import org.pegdown.PegDownProcessor;
+-import org.pegdown.ast.HeaderNode;
+-import org.pegdown.ast.HtmlBlockNode;
+-import org.pegdown.ast.Node;
+-import org.pegdown.ast.RootNode;
+-import org.pegdown.ast.SuperNode;
... 360186 lines suppressed ...