[GitHub] maven-doxia-tools pull request #2: HttpURLConnectionLinkValidator

GitHub user trajano opened a pull request: https://github.com/apache/maven-doxia-tools/pull/2 HttpURLConnectionLinkValidator Deprecate the OnlineHTTPLinkValidator and used the HttpURLConnection to utilize what is provided by the JDK including certificates and SSL updates.

Re: [maven] Git Push Summary

Trying to get gitpubsub integrated with Jenkins so builds are triggered immediately (Found a bug in my slap-dash plugin, waiting for Jenkins to restart... then *should* be working and we can reconfigure polling to daily) On Sat 11 Mar 2017 at 23:51, wrote: > Repository:

[GitHub] maven pull request #107: Fixes to various JIRA issues.

GitHub user ChristianSchulte opened a pull request: https://github.com/apache/maven/pull/107 Fixes to various JIRA issues. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChristianSchulte/maven master Alternatively you can

[DISCUSS] Retrospective on Maven 3.5.0-alpha-1

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 * What is not working well I'll consolidate the responses after 72h and

Re: Timeline for 3.5.0-alpha-2

Benedikt has started a vote for CLI-1.4[1], which should be used as replacement for our own MergedCommandLine. I'll leave it up to you if this is worth adding to alpha-2 Robert [1]

Re: merging MNG-6115-2 branch to master

+1 from me.. Kind regards Karl Heinz On 11/03/17 17:47, Robert Scholte wrote: +1 On Sat, 11 Mar 2017 16:05:18 +0100, Stephen Connolly wrote: +1 from me. Obviously would be better if upstream was fixed that we didn't need the copy but pragmatism says this

Re: merging MNG-6115-2 branch to master

+1 On Sat, 11 Mar 2017 16:05:18 +0100, Stephen Connolly wrote: +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

Re: merging MNG-6115-2 branch to master

+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 comments to say "TODO rework/remove when jansi fixes XYZ-123" On Sat 11 Mar

merging MNG-6115-2 branch to master

there has been some discussion about the way to solve temp file creation for native libs used by JAnsi https://issues.apache.org/jira/browse/MNG-6115 Is it ok to merge MNG-6115-2 branch with this commit http://git-wip-us.apache.org/repos/asf/maven/commit/c36cf425 to master? Regards, Hervé