Plugin specific command line options?

Is there a way to pass command line options but only have one plugin see it? My understanding is that plugins just read from system properties. So to pass 'skip' to a plugin I would use -Dskip but what if two plugins use the same 'skip' ? -- We’re hiring if you know of any awesome Java Devops

Re: Plugin specific command line options?

No ... all plugins pick up all user properties. If two plugins use the same name then both will pick it up and react however implemented. Thats why you should establish plugin specific parameter names for user properties in your specific plugin. So if you have a plugin called foo with the goal

[ANN] Apache Maven Invoker 3.0.0 Released (shared component)

The Apache Maven team is pleased to announce the release of the Apache Maven Invoker, version 3.0.0 This API is concerned with firing a Maven build in a new JVM. It accomplishes its task by building up a conventional Maven command line from options given in the current request, along with

Re: Custom range resolver

On Tue, 24 Jan 2017 14:04:54 +0100, Łukasz Dywicki wrote: I been digging with my collegue aroudn maven ranges for some time and we reached point where we would like to customize them. Because we are using OSGi and maven resolver embedded in Karaf (which is also aether

Re: Custom range resolver

I saw some support for custom extensions in some takari artifacts which allows to do integration testing. Anyhow I managed to override defaults by creating custom plexus components.xml for test which is fine because it literally simulates what extension does with custom export package. I will take