Re: Why I can run plugin:goal in command line even though plugin wasonly defined under pluginManagement?

2018-02-24 Thread Bernd Eckenfels 
It is true: for plugins where the prefix is not found by Default, you can still 
start them with

mvn org.apache.tomcat.maven:tomcat7-maven-plugin:run
Gruss
Bernd
-- 
http://bernd.eckenfels.net

Von: Sigmond Hola
Gesendet: Samstag, 24. Februar 2018 11:03
An: Maven Users List
Betreff: Re: Why I can run plugin:goal in command line even though plugin 
wasonly defined under pluginManagement?

HI bernd,

thanks for reply, but that's not true.

Take tomcat-maven-plugin as example, if you dont defined it under
 or , then following
error will reported if you run  mvn tomcat7:rununder command line:

No plugin found for prefix 'tomcat7' in the current project and in the
plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
>
>
Best regards.


On Sat, Feb 24, 2018 at 4:39 PM, Bernd Eckenfels 
wrote:

> Hello,
>
> You can always run goals on the command line, even if they are not defined
> in the POM at all. If maven finds the plugin in the POM it knows what
> version to use and it allows to specify a Prefix instead of
> group:artifact[:version]:goal.
> Gruss
> Bernd
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> From: Sigmond Hola 
> Sent: Saturday, February 24, 2018 7:01:04 AM
> To: users@maven.apache.org
> Subject: Why I can run plugin:goal in command line even though plugin was
> only defined under pluginManagement?
>
> I defined a specific plugin under  , but
> not under  , but I can still run goals of this plugin
> with  mvn
> plugin:goal.
>
> As far as I understand is only used to configuring the
> plugin information, but not actually import them, right? then how can I use
> the goals of this plugin  in the command line?
>
> Thanks for reply.
>
> Bests.
> --Sig
>

Re: New JDK 9 module chasing tool (was: Getting a list of "to be modularized" dependencies in topological order?)

2018-02-24 Thread Mark Raynsford 
On 2018-02-24T09:47:02 +1000
Paul King  wrote:

> Looks good.
> 
> A small bit of feedback.  I tried using it on a project (Groovy) with
> an "all" artifact that has no jar - just references other jars. Even
> when I specified "pom" it tried to look for the jar
> artifact. Despite the error stacktrace it continued and still seemed
> to produce the correct result. I don't know whether it's possible to
> reduce such noise.

Interesting. Could you file a bug?

There's a known problem in that if the root project you're analyzing
isn't in Maven Central, you will see a (harmless) error stacktrace as
the resolver tries to resolve it from Central. There's an easy fix for
this, I just haven't done it yet. 

-- 
Mark Raynsford | http://www.io7m.com



pgpK7CmSPCotl.pgp
Description: OpenPGP digital signature

Re: Why I can run plugin:goal in command line even though plugin was only defined under pluginManagement?

2018-02-24 Thread Sigmond Hola 
HI bernd,

thanks for reply, but that's not true.

Take tomcat-maven-plugin as example, if you dont defined it under
 or , then following
error will reported if you run  mvn tomcat7:rununder command line:

No plugin found for prefix 'tomcat7' in the current project and in the
plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
>
>
Best regards.


On Sat, Feb 24, 2018 at 4:39 PM, Bernd Eckenfels 
wrote:

> Hello,
>
> You can always run goals on the command line, even if they are not defined
> in the POM at all. If maven finds the plugin in the POM it knows what
> version to use and it allows to specify a Prefix instead of
> group:artifact[:version]:goal.
> Gruss
> Bernd
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> From: Sigmond Hola 
> Sent: Saturday, February 24, 2018 7:01:04 AM
> To: users@maven.apache.org
> Subject: Why I can run plugin:goal in command line even though plugin was
> only defined under pluginManagement?
>
> I defined a specific plugin under  , but
> not under  , but I can still run goals of this plugin
> with  mvn
> plugin:goal.
>
> As far as I understand is only used to configuring the
> plugin information, but not actually import them, right? then how can I use
> the goals of this plugin  in the command line?
>
> Thanks for reply.
>
> Bests.
> --Sig
>

Re: Why I can run plugin:goal in command line even though plugin was only defined under pluginManagement?

2018-02-24 Thread Bernd Eckenfels 
Hello,

You can always run goals on the command line, even if they are not defined in 
the POM at all. If maven finds the plugin in the POM it knows what version to 
use and it allows to specify a Prefix instead of group:artifact[:version]:goal.
Gruss
Bernd

Gruss
Bernd
--
http://bernd.eckenfels.net

From: Sigmond Hola 
Sent: Saturday, February 24, 2018 7:01:04 AM
To: users@maven.apache.org
Subject: Why I can run plugin:goal in command line even though plugin was only 
defined under pluginManagement?

I defined a specific plugin under  , but
not under  , but I can still run goals of this plugin with  mvn
plugin:goal.

As far as I understand is only used to configuring the
plugin information, but not actually import them, right? then how can I use
the goals of this plugin  in the command line?

Thanks for reply.

Bests.
--Sig