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

--first-parent On Wed 15 Mar 2017 at 00:39, Christian Schulte wrote: > Am 03/14/17 um 01:27 schrieb Jeff Jensen: > >> The date of the commit is not the date it got committed to master, but > the > > date it got committed to some branch, no longer existing after the > commit. > > If this is the w

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

Am 03/14/17 um 01:27 schrieb Jeff Jensen: >> The date of the commit is not the date it got committed to master, but the > date it got committed to some branch, no longer existing after the commit. > If this is the way GIT works, so be it. I just don't like it. It could not > be more confusing. > >

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

Hi, On 11/03/17 22:56, Stephen Connolly wrote: Hi all, I think it is a good thing if we take stock of where we are and how we are doing. I would really appreciate if everyone could take a few minutes to respond with their top three of two areas: * What is working well 1. Using Jenkinsfile wi

Distribution file permission issue with current master (attachment).

$ rm -rf apache-maven-3.5.0-SNAPSHOT rm: apache-maven-3.5.0-SNAPSHOT/lib/jansi-native: Permission denied rm: apache-maven-3.5.0-SNAPSHOT/lib: Directory not empty rm: apache-maven-3.5.0-SNAPSHOT: Directory not empty $ find apache-maven-3.5.0-SNAPSHOT apache-maven-3.5.0-SNAPSHOT apache-maven-3.5.0-SN

Distribution file permission issue with current master.

Hi, see the attachment. After unzipping the binary distribution, I cannot delete it anymore without updating file permissions. Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional com

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

Hi Laird, On 13/03/17 23:22, Laird Nelson wrote: On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Gentle reminder. If you can see this thread, you are entitled to contribute. This thread is about discovering where the Maven project can improve how we wo

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

Am 03/14/17 um 21:24 schrieb Stephen Connolly: > Not so easy. Was attempted before and hit issues with gpg signing. Can you remember what issues that were? It will sign the temporary pom java.io.File the same way the install plugin will install that and the deploy plugin will deploy that. Complete

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

Not so easy. Was attempted before and hit issues with gpg signing. Not in scope for 3.5.0 On Tue 14 Mar 2017 at 18:58, Christian Schulte wrote: > Am 12.03.2017 um 15:36 schrieb Karl Heinz Marbaise: > > Hi, > > > > So after I finalized the implementation which seemed to be ok for > > now...the I

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

i really appreciate how smooth running about 20 of our inhouse projects with the alpha did went. Concerning git clients: - a really.nice CLI client is called tig, you should try it. Running tig --all is revealing most things you are used to from UI clients. All in all I found the discussions ver

Re: Maven Resolver 1.1

Am 03/14/17 um 21:24 schrieb Christian Schulte: > Hi, > > are there any plans to release another Maven Resolver 1.0.x? Can I > update the POMs to 1.1-SNAPSHOT? See the comments I added in this > commit: >

Maven Resolver 1.1

Hi, are there any plans to release another Maven Resolver 1.0.x? Can I update the POMs to 1.1-SNAPSHOT? See the comments I added in this commit: I would need to add some methods to the Re

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

Am 12.03.2017 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: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Thanks for the reminder. :-) Working well: 1. Strong release lead 2. CI in better shape 3. Good momentum (right now) Not working well: 1. Scope slipping. "Just one more small thing..." 2. Not a shared view on version meaning (e.g. what's a bug fix release?) 3. Hard to keep up on ML discussions ba