[GitHub] maven issue #123: [MNG-6207] display deprecation build warning for dependenc...

Github user dejan2609 commented on the issue: https://github.com/apache/maven/pull/123 Just on more thing that recalled from my memory: I did tried to execute tests (http://maven.apache.org/core-its/core-it-suite) like this: `mvn clean test -Prun-its` but I received warning that

[GitHub] maven pull request #123: [MNG-6207] display deprecation build warning for de...

Github user dejan2609 closed the pull request at: https://github.com/apache/maven/pull/123 --- 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

[GitHub] maven issue #123: [MNG-6207] display deprecation build warning for dependenc...

Github user dejan2609 commented on the issue: https://github.com/apache/maven/pull/123 Just for the record: somehow it slipped of my mind that `package` phase doesn't execute integration tests (http://maven.apache.org/ref/3.5.0/maven-core/lifecycles.html#default_Lifecycle) and hence

Re: maven-compiler-plugin + default-value for illegal-access

Interesting, based on the output of "java -X" and "javac -X" you're right. Kind of a surprise to me, but in that case this is not an issue for the maven-compiler-plugin Robert On Sat, 10 Jun 2017 23:54:32 +0200, Guillaume Boué wrote: Wouldn't illegal-access be a

[GitHub] maven issue #112: Fix snapshot regular expression

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/112 If you like to get your pull request being integrated it is required to open an [issue on jira](https://issues.apache.org/jira/browse/MNG) and change your commit message accordingly. Something

[GitHub] maven issue #123: [MNG-6207] display deprecation build warning for dependenc...

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/123 Second build after fixing the checkstyle issues has worked. Integration into master done. You can close the pull request. Thank for your help to make Maven better. --- If your project is set up

[GitHub] maven issue #123: [MNG-6207] display deprecation build warning for dependenc...

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/123 First build has failed based on [violated checkstyle rules](https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/MNG-6207/1/console). So best is before you open a pull

Maven Shared Utils

Hi, currently there are 11 issues solved in the component... If there isn't something which currently blocks a release of this component I would like to start a release of maven-shared-utils-3.2.0 on Tuesday of no one objects here? Kind regards Karl Heinz Marbaise

Re: [MNG-6164] Collections inconsistently immutable

Am 2017-05-28 um 20:55 schrieb Hervé BOUTEMY: Le dimanche 28 mai 2017, 19:50:03 CEST Michael Osipov a écrit : How many cases are changed? In which areas of Maven API? That is the information I need to vote for this change, knowing the effective impact it will have As far as I can see for the