Re: Version ranges and snapshots

Hi Jon, Le dimanche 15 février 2015 21:41:52 Jon Harper a écrit : > Hi, > since there were no answers, I'm not sure I wrote to the correct mailing > list for this problem. good mailing list, but can of worm :) > Can anyone direct me to someone who is interested in > working on this issue ? I can

Re: Version ranges and snapshots

Hi, since there were no answers, I'm not sure I wrote to the correct mailing list for this problem. Can anyone direct me to someone who is interested in working on this issue ? For info, the docs have been saying the following for 7+ years: "groupId, artifactId, version: These elements are self-ex

Re: Apache Maven JDeps Plugin

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

Re: Apache Maven JDeps Plugin

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 o

Re: [VOTE] Release Apache Maven PDF Plugin version 1.3

Hi Robert, you were faster with creating the appropriate JIRA ;-).. Thanks for finding it... On 2/15/15 4:39 PM, Robert Scholte wrote: +1, although the logs of the ITs are not clean. [INFO] Ignoring api call removed in maven 3, no reports are generated! [DEBUG] java.lang.NoSuchMethodError: or

Re: [VOTE] Release Apache Maven PDF Plugin version 1.3

+1, although the logs of the ITs are not clean. [INFO] Ignoring api call removed in maven 3, no reports are generated! [DEBUG] java.lang.NoSuchMethodError: org.apache.maven.plugin.PluginManager.verifyReportPlugin(Lorg/apache/maven/model/ReportPlugin;Lorg/apache/maven/project/MavenProject;Lorg/a

Re: Archetype in git

Infra turns out to have a strong preference for leaving SVN 'as is'. I got a dispensation to add a readme pointing across to git. So we might want to plan to follow that pattern. On Sun, Feb 15, 2015 at 12:45 AM, Hervé BOUTEMY wrote: > perhaps adding instruction on the git migration Wiki page [1

Re: Build failed in Jenkins: maven-plugins » Apache Maven RAR Plugin #2651

Hi, there problem seemed to be caused by that not all jenkins nodes have been updated correctly...which means there are some folders left over and haven't been removedwhich i don't understand... If you had the folder on your system as well that sounds like a problem with SVN.. I ha

Re: Build failed in Jenkins: maven-plugins » Apache Maven RAR Plugin #2651

Just checked on my system, it had that folder as well. Removing it and rebuilding it again didn't make it appear again. So I guess there was a configuration-issue in the past, but because it is next to the target-directory it won't be cleaned up with the 'mvn clean'. thanks, Robert Op Sun, 15

Re: Apache Maven JDeps Plugin

Op Sun, 15 Feb 2015 07:09:37 +0100 schreef Hervé BOUTEMY : another topic: "When using Apache Maven 3.2.6 you don't need to include the <<>>; the <<>> can pick up..." looking at the code, IIUC: the plugin doesn't use the jdk toolchain configured (or not) for the whole build with maven-toolc

Re: Apache Maven JDeps Plugin

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 schree

Re: Archetype in git

perhaps adding instruction on the git migration Wiki page [1] would help having easier and consistent work done on every migration Regards, Hervé [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-KeepingtrackofauthorativeSCMforeachplugin Le lundi 9 février 2015

Re: [VOTE] Release Apache Maven PDF Plugin version 1.3

+1 Regards, Hervé Le mercredi 11 février 2015 19:43:58 Karl Heinz Marbaise a écrit : > Hi, > > We solved 9 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932&version=189 > 50 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/issues/?jql=pro

Re: Apache Maven JDeps Plugin

another topic: "When using Apache Maven 3.2.6 you don't need to include the <<>>; the <<>> can pick up..." 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 select a jdk toolchain based on its own pre

Re: Build failed in Jenkins: maven-plugins » Apache Maven RAR Plugin #2651

a maven-archiver directory appears on Jenkins [1] but not on my machine Does anybody know why? Regards, Hervé [1] https://builds.apache.org/job/maven-plugins/ws/maven-rar-plugin/ Le samedi 14 février 2015 12:36:56 Apache Jenkins Server a écrit : > See >

Re: Apache Maven JDeps Plugin

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 c