Custom packaging

Hi, I'm writing a plugin that intends to support custom packaging types. The plugin's components.xml looks like: org.apache.maven.lifecycle.mapping.LifecycleMapping my-custom-type

[GitHub] [maven-doxia] dependabot[bot] opened a new pull request #40: Bump httpclient from 4.5.12 to 4.5.13

dependabot[bot] opened a new pull request #40: URL: https://github.com/apache/maven-doxia/pull/40 Bumps httpclient from 4.5.12 to 4.5.13. [![Dependabot compatibility

[GitHub] [maven-site] kwin commented on pull request #205: [MNG-6994] clarify repository order

kwin commented on pull request #205: URL: https://github.com/apache/maven-site/pull/205#issuecomment-704502139 Anything else left to change before this can be merged? This is an automated message from the Apache Git Service.

Re: [VOTE] Release Maven Resolver version 1.6.1

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 02.10.20 20:32, Michael Osipov wrote: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Maven Resolver version 1.6.1

I need more binding votes. Master is back do not and does not affect this release. @elharo, shall I still cast your vote as -1? Michael Am 2020-10-02 um 20:32 schrieb Michael Osipov: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853

Re: [VOTE] Release Maven Resolver version 1.6.1

Am 2020-10-06 um 01:32 schrieb Dan Tran: +1 none-binding However, I still see random compilation failure at my multiple thread build. I am hoping the latest maven-resolver would make it go away :-) Please share, I can quite quickly determine whether this is Resolver or not. On Sun, Oct 4,

Re: [maven-resolver] branch master updated (aa5e9b1 -> b85faae)

Am 2020-10-05 um 23:39 schrieb Hervé BOUTEMY: moving the plugin to release profile, then have a release build different from the usual SNAPSHOT build does not look a good idea if we need to avoid building with JDK 7 because JDK 8 is required, it's up to Jenkins file to select We already do that

Maven EAR Plugin 3.1.0 bugs - review pending. Was: [ANN] Apache Maven EAR Plugin 3.1.0 Released

Hi, There was a major bug found in Maven EAR Plugin 3.1.0 (i.e. regression comparing to previous version - 3.0.2) - https://issues.apache.org/jira/browse/MEAR-287. This bug makes Maven EAR Plugin 3.1.0 unusable for such a common scenario like building of maven project without invocation of clean

Re: Unexpected dependency requirement when performing "package", but not "install"

I just wanted to mention that I saw that a pull request containing a fix for this nuisance was made the same day I opened the ticket in Jira. This is impressive and very much appreciated, so thank you for that! Hoping to see this fix in the next milestone release of Surefire, then! Have a great