Re: Maven Extension Configuration

Yes it is, Karl Heinz beat me already in 2015! -- Origineel bericht -- Van: "Falko Modler" Aan: dev@maven.apache.org Verzonden: 31-8-2021 23:21:33 Onderwerp: Re: Maven Extension Configuration Hi Robert, this is basically https://issues.apache.org/jira/browse/MNG-5897, no? I left a fe

Re: Maven Extension Configuration

Sounds reasonable, probably like mojo, with properties override so maybe @Param support too or so. Le mar. 31 août 2021 à 23:21, Falko Modler a écrit : > Hi Robert, > > this is basically https://issues.apache.org/jira/browse/MNG-5897, no? > > I left a few thouhts there a while ago. > > Cheers, >

Re: Maven Extension Configuration

Hi Robert, this is basically https://issues.apache.org/jira/browse/MNG-5897, no? I left a few thouhts there a while ago. Cheers, Falko Am 31.08.2021 um 22:50 schrieb Robert Scholte: Hi, I see quite some Maven extensions that rely on configuration. There's no convention for this, so they all

Maven Extension Configuration

Hi, I see quite some Maven extensions that rely on configuration. There's no convention for this, so they all pick their own format and location. Looking at the build-cache it seems there's again configuration required. I think with Maven 4 we should make it possible to add a configuration-b

Re: Apache Maven Shade Plugin command line usage

Hi We can set property values foe most params. Side note: an option you can use is an extension which would auto configure shade plugin. Customizes mvn instance (ext/ or using a custom launcher/cp) over the project descriptors. Le mar. 31 août 2021 à 19:05, Fischer, Wolfram a écrit : > Hi all

Apache Maven Shade Plugin command line usage

Hi all, we (research team) use the Apache Maven Shade Plugin to identify bloated code. We execute the shade plugin with the minimizeJar option and compare the classes which end up in the generated fat jar with the complete set of classes from the project and its direct and transitive dependenci

Re: No more default plugin groups in Maven 4?

On Tue, Aug 31, 2021 at 6:01 PM Michael Osipov wrote: > It should not change. The bundled code contain two plugin groups: > > https://github.com/apache/maven/blob/92d2c2e3b43ca214989f0f517aa90f1525f0ff2e/maven-core/src/main/java/org/apache/maven/execution/DefaultMavenExecutionRequestPopulator.jav

Re: No more default plugin groups in Maven 4?

Am 2021-08-31 um 17:35 schrieb Mickael Istria: Hi all, While trying LemMinX-Maven againt Maven 4 4.0.0-alpha1-SNAPSHOT, I noticed that our tests that don't set a groupId for some plugins (implicit `org.apache.maven.plugins`) start to fail. It seems to me that the default plugin groups are not po

No more default plugin groups in Maven 4?

Hi all, While trying LemMinX-Maven againt Maven 4 4.0.0-alpha1-SNAPSHOT, I noticed that our tests that don't set a groupId for some plugins (implicit `org.apache.maven.plugins`) start to fail. It seems to me that the default plugin groups are not populated any more in Maven 4. Do I get it right? I