Re: maven git commit: [MNG-6165] Deprecate and replace incorrectly spelled public API

Can we make the deprecated methods final, please? It's still binary compatible when final. If someone has overridden such a deprecated method, he will get a compile time error and will notice he needs to override the new method instead. Am 02/04/17 um 00:21 schrieb micha...@apache.org: > Repositor

MNG-6166 for FIX-3.5.0

Who seconds MNG-6166 for FIX-3.5.0? It has been discovered that one test relied on a non-existing dep in Central as well as Plexus Containers 1.6 too. Upgrade to 1.7.1 resolve the missing dependency issue. Michael - To unsubsc

Re: MNG-6146 for 3.5.0

Am 2017-02-02 um 21:39 schrieb Christian Schulte: Am 02/02/17 um 21:08 schrieb Michael Osipov: Who seconds [MNG-6146] Several small stylistic and spelling improvements to code and documentation for FIX-3.5.0? +1 I'd also +1 the API corrections FIX-3.5.0 as long as the old signatures are prese

[GitHub] maven issue #101: Spelling api

Github user jsoref commented on the issue: https://github.com/apache/maven/pull/101 done --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] maven issue #97: .travis and SonarQube.com support

Github user trajano commented on the issue: https://github.com/apache/maven/pull/97 Build is failing due to https://issues.apache.org/jira/browse/MNG-6166 after I synced with main branch --- If your project is set up for it, you can reply to this email and have your reply appear on G

JDK 9 EA Build 155 is available on java.net

Hi Robert & Kristian, *JDK 9 Early Access* b155 is available on java.net There have been a number of fixes to bugs reported by Open Source projects since the last availability email : * b155 - JDK-8167273 : Calendar.getDisplayNames inconsistent with

Re: Can we disable emails to commits@ for branches?

Am 02/03/17 um 19:54 schrieb herve.bout...@free.fr: > sure: isn't git supposed to solve everything? > > :) Maybe as a first step it would be cool if the subject of the emails could be updated to include the branch the commit is about. So that you do not need to open the mail just to find out it's

Re: Can we disable emails to commits@ for branches?

sure: isn't git supposed to solve everything? :) Regards, Hervé - Mail original - De: "Stephen Connolly" À: "Maven Developers List" , i...@soebes.de Envoyé: Vendredi 3 Février 2017 13:07:50 Objet: Re: Can we disable emails to commits@ for branches? On 3 February 2017 at 12:02, Karl He

Re: Can we disable emails to commits@ for branches?

On 3 February 2017 at 12:02, Karl Heinz Marbaise wrote: > Hi, > > On 03/02/17 12:43, Hervé BOUTEMY wrote: > >> commits on branches are useful to know that work is done >> > > Yes... > > >> rebase commits are not useful >> > > True... > > >> I don't know if there is an option to avoid expanded reb

Re: Can we disable emails to commits@ for branches?

Hi, On 03/02/17 12:43, Hervé BOUTEMY wrote: commits on branches are useful to know that work is done Yes... rebase commits are not useful True... I don't know if there is an option to avoid expanded rebase (each commit of the rebase is shown) but just have one "rebase on ..." Would b

[GitHub] maven issue #101: Spelling api

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/101 Created as MNG-6165. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so,

Re: Can we disable emails to commits@ for branches?

commits on branches are useful to know that work is done rebase commits are not useful I don't know if there is an option to avoid expanded rebase (each commit of the rebase is shown) but just have one "rebase on ..." Any git experts on that? Regards, Hervé Le jeudi 2 février 2017, 03:35:52

[GitHub] maven pull request #100: Spelling non-API change

Github user asfgit closed the pull request at: https://github.com/apache/maven/pull/100 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl