Re: Apache Maven JDeps Plugin

Sun, 15 Feb 2015 08:29:24 -0800

That's exactly the reason why I hadn't started it. Ordering based on version is simple, but you probably need to respect the other requirements as well.
I see some challenges here: how to switch between the two without changing the pom.xml or toolchains.xml? 
I have some ideas: let me work on a solid solution for this.

thanks,
Robert
Op Sun, 15 Feb 2015 16:48:01 +0100 schreef Hervé BOUTEMY <[email protected]>: 


generic toolchain ordering doesn't seem feasible

jdk toolchain ordering, since we know fields, can be done: version is the
easiest one to order. But then there are other properties: how to order them, 
since they are full open?

it will be the same if you implement order in jdeps plugin: how to order
Oracle JDK 1.8 with OpenJDK 1.8 and IBM JDK 1.8?
the question of ordering isn't as trivial as expected: sometimes, some user 
may want not only the latest but another condition

Regards,

Hervé

Le dimanche 15 février 2015 11:59:11 Robert Scholte a écrit :

Hi Hervé,
yes, you are right, it is indeed the last one specified in the toolchains 
with type 'jdk'.
I'm still wondering if I should make Toolchains Comparable, so we can
indeed order them.
In that case it would really be the latest.

thanks,
Robert

Op Sun, 15 Feb 2015 07:05:05 +0100 schreef Hervé BOUTEMY

<[email protected]>:
> Hi Robert,
>
> I just had a look at jdeps doc, and was suprosed by "the
> maven-jdeps-plugin
> can pick up the latest jdk toolchain": latest, really?
>
> Then I had a look at the code: IIUC, it uses *the last one* declared in 
> toolchains.xml, but not really the latest since there is no sort on
> version in
> code, isn't it?
>
> Regards,
>
> Hervé
>
> Le samedi 14 février 2015 16:32:23 Robert Scholte a écrit :
>> Hi,
>>
>> 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 plugin >> which can do the analysis during the build of a Java project. Call it a 
>> thin Maven wrapper around the JDeps tool.
>>
>> The sources can be found here:
>> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jdeps-plugin/ 
>>
>> 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
>>
>> There's a SNAPSHOT version availabe at
>> https://repository.apache.org/content/repositories/snapshots/
>>
>> The plugin is still in development, but now would be an appropriate
>> 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.
>>
>> thanks,
>> Robert Scholte
>>
>> ps. Quite a lot of users relate the plugin version to the Maven version. 
>> 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 though it 
>> is
>> not released yet. Chances are that Maven 3.2.6 will be released before 
>> Maven JDeps Plugin 3.0
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to