[GitHub] maven issue #121: [MNG-6206] display deprecation build warning in case when ...

Github user dejan2609 commented on the issue: https://github.com/apache/maven/pull/121 I'm happy to help ! Regards. --- 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

[GitHub] maven pull request #121: [MNG-6206] display deprecation build warning in cas...

Github user dejan2609 closed the pull request at: https://github.com/apache/maven/pull/121 --- 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 pull request #123: [MNG-6207] display deprecation build warning for de...

GitHub user dejan2609 opened a pull request: https://github.com/apache/maven/pull/123 [MNG-6207] display deprecation build warning for dependencies with scope 'system' declaration Note: this PR is created instead of #119 @khmarbaise: FYI You can merge this pull request

[GitHub] maven pull request #119: [MNG-6207] display build WARNING if deprecated 'sys...

Github user dejan2609 closed the pull request at: https://github.com/apache/maven/pull/119 --- 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 #119: [MNG-6207] display build WARNING if deprecated 'system' sc...

Github user dejan2609 commented on the issue: https://github.com/apache/maven/pull/119 @khmarbaise Ok, I'll open new PR then. --- 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

[GitHub] maven issue #119: [MNG-6207] display build WARNING if deprecated 'system' sc...

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/119 Sorry...Can please make the PR new based on the current master of the apache-maven, cause I didn't realized that this PR must be done before the other...Thanks in advance... --- If your project

[GitHub] maven issue #121: [MNG-6206] display deprecation build warning in case when ...

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/121 I have merged the pull request to Maven master. So you can close the pull request here on GitHub. Thanks for our help. --- If your project is set up for it, you can reply to this email and have

Re: Artifact "has been attached with deprecated code" warning

Hi Buillaum, On 06/06/17 23:24, Guillaume Boué wrote: Thanks for confirming this Karl. So in this case, I think that part of the code in maven-artifact-transfer can be safely deleted (calling setRepository and catching an exception). The repository to deploy to is set on the main artifact

[GitHub] maven-surefire issue #141: SUREFIRE-1331: Bump version number for 3.0.0 rele...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/141 @britter I think the version is not mandatory right now. I have to anyway replay each commit and squash in one on the top of future origin master. --- If your project is set up for it,

[GitHub] maven-indexer pull request #17: Migration to Lucene 6.1.0

GitHub user scela opened a pull request: https://github.com/apache/maven-indexer/pull/17 Migration to Lucene 6.1.0 This PR migrates maven-indexer to Lucene 6.1.0. I did 'maven clean verify' and the tests seem to succeed. I'll be around to refine it in case the need

Re: Looking for a collaborator to work on an experimental fork of the maven-dependency-plugin

On Jun 5, 2017 20:51, "Paul Hammant" wrote: The publishing binaries to Github isn't the problem I'm trying to solve - it is the acquisition of deps as builds needs them. Want to take this offline ? - Paul That is interesting problem to solve. Unfortunatelly I don' t have