Return-Path: 
 <dev-return-113584-apmail-maven-dev-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-dev-archive@www.apache.org
Delivered-To: apmail-maven-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8CF3A17EF8
	for <apmail-maven-dev-archive@www.apache.org>;
 Fri, 20 Feb 2015 03:51:42 +0000 (UTC)
Received: (qmail 46958 invoked by uid 500); 20 Feb 2015 03:51:42 -0000
Delivered-To: apmail-maven-dev-archive@maven.apache.org
Received: (qmail 46880 invoked by uid 500); 20 Feb 2015 03:51:42 -0000
Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@maven.apache.org>
List-Help: <mailto:dev-help@maven.apache.org>
List-Post: <mailto:dev@maven.apache.org>
List-Id: "Maven Developers List" <dev.maven.apache.org>
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Delivered-To: mailing list dev@maven.apache.org
Received: (qmail 46863 invoked by uid 99); 20 Feb 2015 03:51:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Feb 2015 03:51:41 +0000
X-ASF-Spam-Status: No, hits=0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE
X-Spam-Check-By: apache.org
Received-SPF: error (athena.apache.org: local policy)
Received: from [194.158.98.14] (HELO mail-1y.bbox.fr) (194.158.98.14)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Feb 2015 03:51:35 +0000
Received: from herve-desktop.localnet (static-176-183-252-218.ncc.abo.bbox.fr
 [176.183.252.218])
	by mail-1y.bbox.fr (Postfix) with ESMTP id 1CD5A7A
	for <dev@maven.apache.org>; Fri, 20 Feb 2015 04:48:54 +0100 (CET)
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: Apache Maven JDeps Plugin
Date: Fri, 20 Feb 2015 04:48:54 +0100
Message-ID: <4689913.Fbk4u2TbD3@herve-desktop>
User-Agent: KMail/4.13.3 (Linux/3.13.0-45-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <op.xt3ixctmkdkhrr@robertscholte>
References: <op.xt1z39bskdkhrr@robertscholte>
 <2275382.XyDea9d0OZ@herve-desktop> <op.xt3ixctmkdkhrr@robertscholte>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Virus-Checked: Checked by ClamAV on apache.org

ok, I just updated the index page to try to improve explanations about =
this=20
unusual/new toolchains use case (ie not trying to be consistent across=20=

plugins)

notice that if you use ToolchainManagerPrivate like maven-toolchains-pl=
ugin=20
does, you even don't require Maven 3.2.6 to do that

Regards,

Herv=E9

Le dimanche 15 f=E9vrier 2015 12:16:14 Robert Scholte a =E9crit :
> Op Sun, 15 Feb 2015 07:09:37 +0100 schreef Herv=E9 BOUTEMY
>=20
> <herve.boutemy@free.fr>:
> > another topic:
> > "When using Apache Maven 3.2.6 you don't need to include the <<<mav=
en-
> > toolchain-plugin>>>; the <<<maven-jdeps-plugin>>>
> >=20
> >  can pick up..."
> >=20
> > looking at the code, IIUC: the plugin doesn't use the jdk toolchain=

> > configured
> > (or not) for the whole build with maven-toolchain-plugin but will s=
elect
> > a jdk
> > toolchain based on its own preference
> >=20
> > isn't it?
>=20
> yes. Up until Maven 3.2.5 the maven-toolchain-plugin was responsible =
for
> reading the toolchains.xml, so in a multimodule project the same file=
 was
> read over and over again.
> This has been rewritten. Now it is read only once on startup. This al=
so
> made it possible to read it without the maven-toolchain-plugin, which=

> makes sense in this case. You probably want to verify if your current=

> (older JDK) code is ready according to jdeps (newer JDK, i.e. 8 and a=
bove).
>=20
> This is the magic line:
> List<Toolchain> tcs =3D
> =09(List<Toolchain>) getToolchainsMethod.invoke( toolchainManager, se=
ssion,
> "jdk",
> =09Collections.singletonMap( "version", "[1.8,)" ) );
> The final arguments defines the restriction.
> We could make a mojo parameter for this, so users can lock it to a
> specific tool.
>=20
> thanks,
> Robert
>=20
> > Regards,
> >=20
> > Herv=E9
> >=20
> > Le samedi 14 f=E9vrier 2015 16:32:23 Robert Scholte a =E9crit :
> >> Hi,
> >>=20
> >> during FOSDEM 2015 a few members of the Apache Maven team visited =
a talk
> >> of Oracle, presented by Rory O'Donnell and Dalibor Topic.
> >> Their talk ended with encouraging everybody to use the JDeps tool =
to
> >> analyze your dependencies in preparation of JDK9s jigsaw.
> >> On behalf of the Maven team I've picked up the task to develop a p=
lugin
> >> which can do the analysis during the build of a Java project. Call=
 it a
> >> thin Maven wrapper around the JDeps tool.
> >>=20
> >> The sources can be found here:
> >> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jdeps-pl=
ugin/
> >>=20
> >> The documentation can be found here:
> >> http://maven.apache.org/plugins-archives/maven-jdeps-plugin-LATEST=
/maven-> >> jde ps-plugin/
> >> http://maven.apache.org/plugins-archives/maven-jdeps-plugin-LATEST=
/maven-> >> jd
> >> eps-plugin/usage.html
> >>=20
> >> There's a SNAPSHOT version availabe at
> >> https://repository.apache.org/content/repositories/snapshots/
> >>=20
> >> The plugin is still in development, but now would be an appropriat=
e
> >> moment
> >> to share your thoughts on what this plugin should do. For instance=
:
> >> break
> >> the build if the project depends on JDK internal APIs (already
> >> implemented).
> >> So please, share your ideas.
> >>=20
> >> thanks,
> >> Robert Scholte
> >>=20
> >> ps. Quite a lot of users relate the plugin version to the Maven ve=
rsion.
> >> For that reason the maven-jdeps-plugin version starts with 3.0,
> >> indicating
> >> you need to use at least Maven-3.
> >> ps2. Documentation already refers to Apache Maven 3.2.6, even thou=
gh it
> >> is
> >> not released yet. Chances are that Maven 3.2.6 will be released be=
fore
> >> Maven JDeps Plugin 3.0
> >>=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