Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Am 03/12/17 um 15:36 schrieb Karl Heinz Marbaise: > Hi, > > So after I finalized the implementation which seemed to be ok for > now...the IT's are currently not working based on particular reason > (explanations later). > > I would like to know the opinion of the Maven DEV's about this: > >

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Hi, So if no one has objections against this change I would like to do the merge to master monday evening... I will wait for the IT's results first ... Kind regards Karl Heinz Marbaise On 12/03/17 19:47, Karl Heinz Marbaise wrote: Hi Hervé, On 12/03/17 19:40, Hervé BOUTEMY wrote: IIUC

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Hi Hervé, On 12/03/17 19:40, Hervé BOUTEMY wrote: IIUC You can publish such poms with ${revision}, ${sha1} and/or ${changelist} in central from the early begining: even MNG-5576 just removed a warning I didn't remember on that...Thanks for pointing out this. Then the new commit just make

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

IIUC You can publish such poms with ${revision}, ${sha1} and/or ${changelist} in central from the early begining: even MNG-5576 just removed a warning Then the new commit just make it work better, in more complex multi-module situations: looks reasonable I just pushed 2 commits: the first one

Re: merging MNG-6115-2 branch to master

MNG-6186 created to track the issue https://issues.apache.org/jira/browse/MNG-6186 Le dimanche 12 mars 2017, 17:18:06 CET Hervé BOUTEMY a écrit : > Le samedi 11 mars 2017, 15:05:18 CET Stephen Connolly a écrit : > > +1 from me. > > > > Obviously would be better if upstream was fixed that we

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

my own topics: What is working well: 1. we're managing to do releases with confidence on what's inside 2. there are some discussions (even if not in an efficient way: IMHO, some changes should become proposals in the Wiki) 3. Jenkins hook to check branches (even if not perfect, it works

Re: merging MNG-6115-2 branch to master

Le samedi 11 mars 2017, 15:05:18 CET Stephen Connolly a écrit : > +1 from me. > > Obviously would be better if upstream was fixed that we didn't need the > copy but pragmatism says this is the fix for 3.5.0 > > Extra brownie points for raising the issue upstream and fencing the > additions with

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

On Sun 12 Mar 2017 at 14:36, Karl Heinz Marbaise wrote: > Hi, > > So after I finalized the implementation which seemed to be ok for > now...the IT's are currently not working based on particular reason > (explanations later). > > I would like to know the opinion of the Maven

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Let's try ... * What is working well 1. Automations/Processes improvements with Jenkins 2. Many more interactions to get the release out (it revivified the dev community) 3. After so many years we have coloured logging !!! LOL * What is not working well 1. Our SCM notifications are really not

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Here's my list: Working well: 1. Jenkinsfile and multibranch 2. Actually discussing changes before merging 3. We got a release at last with coloured logging Needs improvement: 1. I was not happy at all with the chaos in trying to plan out the scope of 3.5.0 2. Very difficult to determine which

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Thanks Robert for seeding contributions . On Sun 12 Mar 2017 at 11:59, Robert Scholte wrote: > Let me kick off with my list: > > What is working well: > 1. It looks like we're going to have a new official Maven release soon. > 2. Some take their responsibility to start a

Re: Timeline for 3.5.0-alpha-2 / MNG-6057

Hi, So after I finalized the implementation which seemed to be ok for now...the IT's are currently not working based on particular reason (explanations later). I would like to know the opinion of the Maven DEV's about this: The following scenario: This feature has been introduced in Maven

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Let me kick off with my list: What is working well: 1. It looks like we're going to have a new official Maven release soon. 2. Some take their responsibility to start a discussion. It is good to rate the impact of changes if we want to stay one of the worlds standards. 3. We're all

[ANN] GitPubSub multi-branch notification now working on builds.apache.org

My weekend project: https://github.com/stephenc/asf-gitpubsub-jenkins-plugin was a success (Need to find a home for it at the ASF (as it doesn't make sense at Jenkins / outside of ASF) Now when you push a change to maven.git the branch / commit should trigger a build within seconds. There are