Return-Path: 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 AF1E5185F8 for ; Sun, 13 Dec 2015 22:23:42 +0000 (UTC) Received: (qmail 5059 invoked by uid 500); 13 Dec 2015 22:23:37 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 4927 invoked by uid 500); 13 Dec 2015 22:23:37 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 4916 invoked by uid 99); 13 Dec 2015 22:23:37 -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, 13 Dec 2015 22:23:37 +0000 Received: from robertscholte.dynamic.ziggo.nl (5248749D.cm-4-1b.dynamic.ziggo.nl [82.72.116.157]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id A832C1A0042 for ; Sun, 13 Dec 2015 22:23:36 +0000 (UTC) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Maven Developers List" Subject: Re: Bug or feature: executing plugin without version References: Date: Sun, 13 Dec 2015 23:23:31 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Robert Scholte" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) Hi Paul, with your pom.xml I get 2.10 as expected, with both G:A:goal and prefix:goal. Tested with M3.0.5 and M3.1.1 and 3.3.3 Sorry, can't reproduce. Robert Op Thu, 10 Dec 2015 17:50:39 +0100 schreef Paul Benedict : > Here is the POM: > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd"> > > 4.0.0 > z > ztest > 0.1-SNAPSHOT > pom > > > > > > org.apache.maven.plugins > maven-dependency-plugin > 2.10 > > > > > > > > With JDK 6 on my box, I am using Maven 3.1.1. > > Running this: > mvn -X org.apache.maven.plugins:maven-dependency-plugin:tree > > I get this: > [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-dependency-plugin:2.8:tree' with basic > configurator > > It should be 2.10 if the POM was consulted. > > PS: I did a little archaeological digging. Evidently, the Super POM for > 3.1.1 locks the Dependency Plugin to 2.8 [1], which explains why 2.8 is > being selected. There is also this curious comment in there (and still > exists in 3.3.9): > > > It seems to me this is a bug: the Super POM is being preferred over the > Plugin Management of my POM. > > [1] https://maven.apache.org/ref/3.1.1/maven-model-builder/super-pom.html > > Cheers, > Paul > > On Thu, Dec 10, 2015 at 7:25 AM, Adrien Rivard > wrote: > >> Hi, >> >> It works correctly for me, tested with : >> >> >> >> >> >> org.codehaus.mojo >> versions-maven-plugin >> 2.1 >> >> >> >> >> >> >> and "mvn >> org.codehaus.mojo:versions-maven-plugin:display-dependency-updates" >> >> >> Are you sure you did'nt miss something ? like wrong artifactId/groupId >> maybe ? >> >> >> >> On Wed, Dec 9, 2015 at 9:41 PM, Paul Benedict >> wrote: >> >> > groupId:artifactId:goal >> > >> > Cheers, >> > Paul >> > >> > On Wed, Dec 9, 2015 at 2:38 PM, Robert Scholte >> > wrote: >> > >> > > I'd say bug. Are you using prefix:goal or groupId:artifactId:goal ? >> > > >> > > Robert >> > > >> > > Op Wed, 09 Dec 2015 17:19:32 +0100 schreef Paul Benedict < >> > > pbenedict@apache.org>: >> > > >> > > >> > > Scenario: I executed a plugin goal on command line and specified a >> > version >> > >> (1.5). I then did it again without specifying a version. For the >> latter, >> > >> Maven chose the latest version (1.6) from my remote repository. >> > >> >> > >> I was curious about the version selection; so I edited my POM and >> added >> > a >> > >> /build/pluginManagement/plugin to lock down the version. When I >> executed >> > >> without the version on the command line again, the latest (1.6) was >> > still >> > >> selected. >> > >> >> > >> Don't you think that when I omit the version on the command line, >> if >> the >> > >> plugin version is specified in the POM, it should use the >> configuration? >> > >> Is >> > >> this a bug or an intended feature? It's at least very surprising. >> > >> >> > >> I need to execute a particular version of a plugin in a shell >> script, >> > but >> > >> I >> > >> don't want to specify the version in the script. I'd rather have it >> > locked >> > >> in the POM but obviously the POM is not consulted in this case. >> WDYT? >> > >> >> > >> Cheers, >> > >> Paul >> > >> >> > > >> > > >> --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org >> > > For additional commands, e-mail: dev-help@maven.apache.org >> > > >> > > >> > >> >> >> >> -- >> Adrien Rivard --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org