Re: Maven 3.2.6 - Release ?

Happy to be on standby if you need any help while trying to cut a core release. I use a bunch of scripts and helpers that you’re welcome too if you want them. > On Oct 12, 2015, at 5:10 PM, Karl Heinz Marbaise wrote: > > Hi, > > i have tried to backport the following issues: > > https://issue

Re: MNG-5858 - Question

There are cases where this would break. It’s not a pattern I see very often but when projects put their parent/aggregator pom in a directory of its own there is no pom.xml at the upper most level of the project. I know that Fred got bitten by a .mvn/ directory way up near the root of the file s

Re: MNG-5858 - Question

Hi, On 10/12/15 10:42 PM, Andreas Gudian wrote: Good idea! Funny enough, I've seen multi-module projects that wouldn't work with this - they have an aggregator pom on the top-level, with: componentA/common componentA/server componentB/common .. So they skip a level of aggregator poms (in

Re: Intend to release release 2.5.3

+1 > On 12 Oct 2015, at 18:01, Benson Margulies wrote: > > To me, it's a pretty urgent situation when the current version of the > release plugin blows up; what if we end up unable to release the > release plugin? So, absent any objections or further discussion of the > plexus-utils version, I i

Maven 3.2.6 - Release ?

Hi, i have tried to backport the following issues: https://issues.apache.org/jira/browse/MNG-5793 https://issues.apache.org/jira/browse/MNG-5742 from 3.3.X to a (currently local) 3.2.6-branch which was very easy ..and it works as i expect... Is there something else i need to pay attention to

Re: MNG-5858 - Question

Good idea! Funny enough, I've seen multi-module projects that wouldn't work with this - they have an aggregator pom on the top-level, with: componentA/common componentA/server componentB/common .. So they skip a level of aggregator poms (in the componentX-directories). I'd consider that an edg

Re: Maven Core Branch Cleanup

Hi, cleaning up done... heads 23 hours agomaster shortlog | log | tree 8 days ago slf4j-log4j2.4 shortlog | log | tree 6 weeks ago MNG-5878 shortlog | log | tree 9 months agoconfigurator shortlog | log | tree 19 months ago maven-3.1.x shortlog | lo

Re: Maven Core Branch Cleanup

Anyone wishing to retain these branches can just go ahead and fork the girhub repo, they' 2015-10-12 20:20 GMT+02:00 Jason van Zyl : > You can nuke all my branches. They are either integrated, irrelevant, or easy > to recreate. > >> On Oct 12, 2015, at 2:11 PM, Karl Heinz Marbaise wrote: >> >> H

Re: Intend to release release 2.5.3

+1 (non binding): committer Very well! Yeah, discussion was enough, we need actions like this. Maintain dep. Mgt. in the future as well. On Mon, Oct 12, 2015 at 6:01 PM, Benson Margulies wrote: > To me, it's a pretty urgent situation when the current version of the > release plugin blows up; wh

Re: Maven Core Branch Cleanup

You can nuke all my branches. They are either integrated, irrelevant, or easy to recreate. > On Oct 12, 2015, at 2:11 PM, Karl Heinz Marbaise wrote: > > Hi, > > i have taken a look onto the list of branches on maven core which is a list > of 17 beanches but where many of them haven't been tou

MNG-5858 - Question

Hi, based on the changes we have made to identify the folder where ".mvn" is located i would suggest to enhance the check with checking the pom.xml file as well...So i would suggest to enhance the find_maven_basedir() function like the following: local basedir="$(pwd)" local wdir="$(pw

Maven Core Branch Cleanup

Hi, i have taken a look onto the list of branches on maven core which is a list of 17 beanches but where many of them haven't been touched for years (yes i'm using plural)... MNG-3004 Updated 6 years ago by Daniel Fabulich MNG-4388 Updated 6 years ago by bentmann MNG-1803 Updated 5 years ago

Re: Intend to release release 2.5.3

+1 On Mon, Oct 12, 2015 at 9:01 AM, Benson Margulies wrote: > To me, it's a pretty urgent situation when the current version of the > release plugin blows up; what if we end up unable to release the > release plugin? So, absent any objections or further discussion of the > plexus-utils version,

Intend to release release 2.5.3

To me, it's a pretty urgent situation when the current version of the release plugin blows up; what if we end up unable to release the release plugin? So, absent any objections or further discussion of the plexus-utils version, I intend start the process for 2.5.3 tomorrow, since I already made the

Re: Can anyone explain this missing plexus utils class?

On Sun, Oct 11, 2015 at 11:39 PM, Dan Tran wrote: > For the current case, maven-release-plugin correctly pick up > plexus-utils-3.0.10 since it is locked by maven-release's > dependencyManagement. This is the correct behavior > > To fix this issue at project/consumer level, one must have pluginMa

Re: [VOTE] Release Apache Maven maven-plugin parent-pom version 28

+1 > On 11 Oct 2015, at 02:56, Benson Margulies wrote: > > Hi, > > 2 changes in JIRA. Many other commits. > > > ** Bug >* [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference menu >* [MPOM-89] - Unbalanced versions of Maven Invoker Plugin > > There are no pending issues