[GitHub] maven-wagon issue #27: Support external downloader for downloading files

Github user soiff commented on the issue: https://github.com/apache/maven-wagon/pull/27 It's not enough for unstable network connections and shows not enough log about downloadings, suppose we are behind the GFW. By the way, support external downloaders make wagon itself more flexible

[GitHub] maven-integration-testing pull request #15: [MNG-6084] Add test for JSR250 s...

Github user dantran closed the pull request at: https://github.com/apache/maven-integration-testing/pull/15 --- 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

[GitHub] maven-integration-testing issue #15: [MNG-6084] Add test for JSR250 support

Github user dantran commented on the issue: https://github.com/apache/maven-integration-testing/pull/15 already merged --- 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

[GitHub] maven-integration-testing issue #15: [MNG-6084] Add test for JSR250 support

Github user michael-o commented on the issue: https://github.com/apache/maven-integration-testing/pull/15 @dantran Can you squash? I will have a look and will merge soon. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] maven-wagon issue #27: Support external downloader for downloading files

Github user michael-o commented on the issue: https://github.com/apache/maven-wagon/pull/27 Why is `wagon-http` and `wagon-http-lightweight` not enough? --- 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

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Boils down to: Decide the list of issues part of the next release. Update JIRA to reflect that. Provide the release nodes and what else needs to be documented. Personally, cut a resolver release 1.2.0 from current resolver master and throw out tons of RCs of current core master using either 3.4.0

Re: Improving Jenkins

Am 12/21/16 um 08:04 schrieb Hervé BOUTEMY: > And remember we'll require to prepare a list of known plugins Older findbugs plugin versions are not working with 3.4. The maven-plugin-plugin 3.4 is not working with 3.4. You can downgrade to 3.3 or upgrade to 3.5. That's the plugins I know of.

Re: Roadmap to the next Maven release (Re: Improving Jenkins)

Am 12/21/16 um 13:46 schrieb Christian Schulte: > ago. The next commits from me would be for the Maven site and for the > release notes. Except that command line option. Ok. It really depends on That command line option got added with this commit:

Roadmap to the next Maven release (Re: Improving Jenkins)

Am 21.12.2016 um 08:04 schrieb Hervé BOUTEMY: > remember: we'll have to explain users why we did a breaking change > I don't think such an explanation will be possible for users: for long-dev > like me, it's hardly a valid explanation > > Can you explain in plain english some cases, please? > >