Re: relativePath for parent poms in our plugins

2019-12-21 Thread Mark Struberg
To be honest, I didn't even know that there is a 'main project' with tons of git-submodules to emulate our old maven master build. I still wonder whether it has any benefit to have the relativePath in our plugins. It is useful if you have a reactor build where maven then knows how to search for

Re: relativePath for parent poms in our plugins

2019-12-21 Thread Romain Manni-Bucau
Le sam. 21 déc. 2019 à 15:03, Hervé BOUTEMY a écrit : > how does the current relativePath work less than without it? > Does it really break anything more than just "people don't understand the > value" then consider it "wrong"? > Well, it is unlikely but it can break the build yes, at least if i

Re: [RESULT] [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Stephen Connolly
Nope on PMC quorum, but here’s my +1 to make it legal On Sat 21 Dec 2019 at 14:19, Hervé BOUTEMY wrote: > Hi, > > The vote has passed with the following result: > > +1 : Karl Heinz Marbaise, Mark Struberg, Hervé Boutemy > > PMC quorum reached > > I will promote the artifacts to the central repo.

Re: [VOTE] - Integration Tests of Maven Core

2019-12-21 Thread Karl Heinz Marbaise
Hi, On 21.12.19 15:23, Enrico Olivelli wrote: +1 Please also update the release guide That should be done of course. thanks for the hint. Enrico Il sab 21 dic 2019, 15:18 Karl Heinz Marbaise ha scritto: I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which preserves t

Re: [VOTE] - Integration Tests of Maven Core

2019-12-21 Thread Enrico Olivelli
+1 Please also update the release guide Enrico Il sab 21 dic 2019, 15:18 Karl Heinz Marbaise ha scritto: > I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which > preserves the state of the history and furthermore we should create a > tag after each Maven Core release. > > V

[RESULT] [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Hervé BOUTEMY
Hi, The vote has passed with the following result: +1 : Karl Heinz Marbaise, Mark Struberg, Hervé Boutemy PMC quorum reached I will promote the artifacts to the central repo. - To unsubscribe, e-mail: dev-unsubscr...@ma

[VOTE] - Integration Tests of Maven Core

2019-12-21 Thread Karl Heinz Marbaise
I suggest to create a tag 3.6.3 in Integration Tests of Maven Core which preserves the state of the history and furthermore we should create a tag after each Maven Core release. Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise -

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Hervé BOUTEMY
here is my +1 Regards, Hervé Le lundi 16 décembre 2019, 19:37:00 CET Hervé BOUTEMY a écrit : > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&ve > rsion=12346480&styleName=Text > > Staging repo: > https://repository.apache.org/content/re

Re: relativePath for parent poms in our plugins

2019-12-21 Thread Hervé BOUTEMY
how does the current relativePath work less than without it? Does it really break anything more than just "people don't understand the value" then consider it "wrong"? in addition, I know that intermittent Maven contributor will clone only one Git repository, but I personally work on every Maven

Re: relativePath for parent poms in our plugins

2019-12-21 Thread Romain Manni-Bucau
Agree with Robert, git clone && mvn install must always work and be straight forward if we want people to be able to help/work imho. Le sam. 21 déc. 2019 à 13:33, Robert Scholte a écrit : > that only works for the very, very few that uses this repository. > It should work as to how contributors

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Mark Struberg
+1 LieGrue, strub > Am 16.12.2019 um 19:37 schrieb Hervé BOUTEMY : > > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12346480&styleName=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1545/ >

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Karl Heinz Marbaise
Hi, tested with several Maven versions, JDK's... +1 from me. Kind regards Karl Heinz Marbaise On 16.12.19 19:37, Hervé BOUTEMY wrote: Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12346480&styleName=Text Staging repo: https://reposi

Re: relativePath for parent poms in our plugins

2019-12-21 Thread Robert Scholte
that only works for the very, very few that uses this repository.  It should work as to how contributors work with it, otherwise you'll see other issues compared to them. Robert On 21-12-2019 12:33:53, Hervé BOUTEMY wrote: disagree We have the repo configuration which brings a location for ever

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Hervé BOUTEMY
Having a value in master is useful: you get reproducible SNAPSHOTs Regards, Hervé Le samedi 21 décembre 2019, 09:41:34 CET Stephen Connolly a écrit : > On Tue 17 Dec 2019 at 08:14, Hervé BOUTEMY wrote: > > I forgot to mention: > > notice that thanks to maven-release-plugin 3.0.0-M1, the > > pro

Re: relativePath for parent poms in our plugins

2019-12-21 Thread Hervé BOUTEMY
disagree We have the repo configuration which brings a location for every Git repository: https://maven.apache.org/scm.html or https://github.com/apache/maven-sources/ The relative paths are calculated against that. And I recently even added aggregator poms to build absolutely everything in one

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

2019-12-21 Thread Stephen Connolly
On Tue 17 Dec 2019 at 08:14, Hervé BOUTEMY wrote: > I forgot to mention: > notice that thanks to maven-release-plugin 3.0.0-M1, the > project.build.outputTimestamp property was automatically updated 2 times > during the release: > - [1] during the release preparation phase > - [2] when preparing