Bug or feature: executing plugin without version

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

Re: Inclusion of Maven on SDKMAN

Hi Marco, Thanks for the explanations. I understand that you would give Maven PMC a key (or one per PMC member to better track, we'll see later) to update status of every released Maven version: yes, having Maven PMC in charge of its choices against Maven community using SDKMAN seems a decent

Re: Inclusion of Maven on SDKMAN

yes, Jenkins and SDKMAN are not the same beasts, but they share some common ground: ideas from one may need to be adjusted. IIUC, discovery of available Maven versions could work on SDKMAN exactly like Jenkins Then there is the choice on default: for Maven, we publish the recommended version

Re: Bug or feature: executing plugin without version

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 < > pbened...@apache.org>: > > >

Re: Bug or feature: executing plugin without version

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 : Scenario: I executed a plugin goal on command line and specified a version (1.5). I then did it again without specifying a version.