Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

From a security perspective, I would expect that core classes can not be overridden by extensions or plugins. Likewise, extension classes can not be overridden by plugins. Given the use case of defaulting resources, I would expect that the plugin resources are first, followed by plugin specifi

Re: Reactor safe/rally points

Both these use cases sound like adding incredible complexity to support less than 1% situations, and worse, encouraging monolithic builds. In the first case, the module creating a shaded jar can mark its constituent jars as optional; preventing the transitive dependencies. In the second case,

Re: Reactor safe/rally points

So doesn’t this require a new directive such as ‘ scope or similar regardless of safe/rally points? And to provide backwards compatibility, there must be a split between the legacy consumer view of the pom and the new producer view of the pom? > On Nov 5, 2017, at 11:30 PM, Stephen Connolly

Re: Reactor safe/rally points

Are these integration test for the plugin or do the integration tests use the plugin? If the former, then the invoker plugin is appropriate. If the latter, then a non-code, non-transitive dependency scope is a possibility. Again, this new scope has the backwards compatibility problem.. > On

Re: Build vs Consumer POM study

Hervé, Great work! Some possible additions for the wiki page: Naming Conventions consumer pom must continue to be named pom.xml build pom shall be called build.xml alternate build inputs could be build.json or build.yaml EcoSystem Impacts projects distributing source code through maven central

Plugin embedded configuration property configuration (cross posted after no response in maven users)

I'm creating a new plugin where i would like the to have "embedded" configuration. public abstract class MyAbstractMojo extends AbstractMojo { @Parameter private Embedded embedded; Where the ”embedded" configuration pojo has property injection with default values. @Named public class

maven-gpg-plugin updates

Who can work with me to get maven-gpg-plugin updated? In particular, I’d like to add goals to sign and checksum files that are not artifacts. See MGPG-43 . Can a committer to another Apache project commit to maven plugin repositories? regards,