How does maven resolve cyclic dependendencies/how should the verbose depenedency:tree display them

If I have Projects A, B, C with A depends on B, B depends on C, C depends on A does maven still include one of each A, B, C? Should the tree output be as below: Project-groupId:Project-Artifact \- A \- B \- C \- A (omitted due to cycle) If this isn't correct what is the expe

Re: Which version should maven-shared-utils have?

I don't think that should be necessary. A failed 3.3.0 release should not use up the version number. I think there are instructions on the release page for unrolling a failed release, though I haven't had cause to use them myself. On Fri, Jul 17, 2020 at 5:53 AM Dennis Lundberg wrote: > > Hi agai

[GitHub] [maven-doxia] elharo closed pull request #36: Bump commons-lang3 from 3.8.1 to 3.11

elharo closed pull request #36: URL: https://github.com/apache/maven-doxia/pull/36 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to t

Re: Does maven-filtering really require maven-shared-utils 3.3.0-SNAPSHOT?

Den fre 17 juli 2020 kl 13:56 skrev Robert Oxspring : > > > On 17 Jul 2020, at 10:42, Dennis Lundberg wrote: > > > > Hi, > > > > I'm checking the scope of releasing maven-resources-plugin. There is > > currently a transitive dependency chain like this: > > - maven-resources-plugin depends upon >

Re: Does maven-filtering really require maven-shared-utils 3.3.0-SNAPSHOT?

> On 17 Jul 2020, at 10:42, Dennis Lundberg wrote: > > Hi, > > I'm checking the scope of releasing maven-resources-plugin. There is > currently a transitive dependency chain like this: > - maven-resources-plugin depends upon > - maven-filtering 3.2.0-SNAPSHOT depends upon > - maven-shared-util

Re: Depending on snapshot versions at HEAD

On Fri, 17 Jul 2020 at 17:05, Dennis Lundberg wrote: > Den fre 17 juli 2020 kl 08:55 skrev Olivier Lamy : > > > On Fri, 17 Jul 2020 at 16:53, Dennis Lundberg > > wrote: > > > > > Hi, > > > > > > Given that I've been gone for some time from this list things might > have > > > changed. If that's t

Which version should maven-shared-utils have?

Hi again, While I was digging in VCS history I discovered something odd with maven-shared-utils. The current trunk/head in git has version 3.3.0-SNAPSHOT. But maven-shared-utils 3.3.0 was tagged during a release in 2017... https://github.com/apache/maven-shared-utils/tree/029ac4ec7b6636e8c1d32307

Does maven-filtering really require maven-shared-utils 3.3.0-SNAPSHOT?

Hi, I'm checking the scope of releasing maven-resources-plugin. There is currently a transitive dependency chain like this: - maven-resources-plugin depends upon - maven-filtering 3.2.0-SNAPSHOT depends upon - maven-shared-utils 3.3.0-SNAPSHOT That last SNAPSHOT was added in https://github.com/ap

JDK 15 is now in Rampdown Phase Two

Hi Robert , ** *Per the JDK 15 schedule, we are in Rampdown Phase Two* *[1]* Per the JDK Release Process [2] we now turn our focus to *P1 and P2 bugs*, which can be fixed with approval [3]. Late enhancements are still possible, with approval [4], but the bar is now extraordinarily high. **Pl

Re: Do we have a policy for minimum Maven version for plugins?

Thanks Anders, I found the page you mentioned at https://maven.apache.org/developers/compatibility-plan.html I've read that and also the technical details wiki page at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857 The issue in question updates to Maven 3.1.0 dependen

Re: custom default lifecycle per project

Le ven. 17 juil. 2020 à 09:31, Hervé BOUTEMY a écrit : > Le vendredi 17 juillet 2020, 08:22:10 CEST Romain Manni-Bucau a écrit : > > Le ven. 17 juil. 2020 à 00:03, Hervé BOUTEMY a > > > > I don't get what "mvn my-test" means: there is no "my-test" phase > > > and I don't understand how your cust

Re: [VOTE] Release Apache Maven Archetype version 3.2.0

Hi, +1 from me Kind regards Karl Heinz Marbaise On 13.07.20 23:50, Hervé BOUTEMY wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12346641&styleName=Text Staging repo: https://repository.apache.org/content/repositories/maven-1594

Re: custom default lifecycle per project

Le vendredi 17 juillet 2020, 08:22:10 CEST Romain Manni-Bucau a écrit : > Le ven. 17 juil. 2020 à 00:03, Hervé BOUTEMY a > > I don't get what "mvn my-test" means: there is no "my-test" phase > > and I don't understand how your custom lifecycle shares some phases with > > default lifecycle, but ha

Re: Do we have a policy for minimum Maven version for plugins?

There's been some discussion regarding this lately and my take is that we've settled on that requiring Maven 3.1.0 is ok for plugins. In the same discussion I *think* we settled on that a Java 8 requirement is ok. What I don't think we all agreed on is if it's ok to bump the requirements without a

Re: Depending on snapshot versions at HEAD

Den fre 17 juli 2020 kl 08:55 skrev Olivier Lamy : > On Fri, 17 Jul 2020 at 16:53, Dennis Lundberg > wrote: > > > Hi, > > > > Given that I've been gone for some time from this list things might have > > changed. If that's the case I'm sure someone will correct me :) > > > > But it used to be the

Do we have a policy for minimum Maven version for plugins?

Hi, Where do we currently stand when it comes to the minimum version of Maven required by our plugins? Can a version 3.x Apache Maven plugin require something newer than Maven 3.0? The reason I ask is this https://issues.apache.org/jira/browse/MSHARED-936 which has the consequence that all plugin