Re: Another yearly bug squash

In Surefire I already made a cleanup. Those open ones are still valid. Thx. On Fri, Dec 25, 2015 at 12:05 AM, Michael Osipov <1983-01...@gmx.net> wrote: > Hi folks, > > I'd like to do another bug squash like a did last year. > We currently have 132 unresolved bugs which haven't been updated for

[GitHub] maven-surefire pull request: [SUREFIRE-1135] Improve ignore messag...

Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/79#issuecomment-167356250 @mbocek This PR was merged with master. Thx for contributing. Please close it. --- If your project is set up for it, you can reply to this email and have your

MNG-5896: Speed up builds by parallel POM downloads

When building a project with dependencies not yet available in the local repository, I noticed that Maven first downloads the dependency POMs sequentially and then proceeds downloading the dependency JARs with up to 5 threads in parallel, which is not optimal when the POMs are served by a

Re: [VOTE] Release Apache Maven Shared Component: File Management Version 3.0.0

+1 On Fri, Dec 25, 2015 at 2:50 PM, Karl Heinz Marbaise-3 [via Maven] < ml-node+s40175n5856227...@n5.nabble.com> wrote: > Hi, > > We solved 9 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20file-management-3.0.0 > > There are still a

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

-0 I think we are still using fluido. And some users too. I don't mind the others but this one is used a lot included by us. So I don't understand such rush to retire that? I guess we are in an Opensource foundation which we do not have pressure for maintenance etc... On 25 December 2015 at

Re: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

Nobody is retiring Fluido Skin but only those in the subject. > Gesendet: Sonntag, 27. Dezember 2015 um 01:10 Uhr > Von: "Olivier Lamy" > An: "Maven Developers List" > Betreff: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven > Stylus

Re: MNG-5896: Speed up builds by parallel POM downloads

This is interesting. I think the plan I to move aether under the maven project (at least I was asked to grant my contributions to aether to allow dual licensing under ASL on the basis of moving the code here... Still not sure what the status is) so I suspect until that gets resolved aether will be

Re: Retiring Maven Skins

+1 no objections to: Retire: Maven Application Skin, Maven Classic Skin, Maven Stylus Skin Active: Maven Default Skin, Maven Fluido Skin On Thu, Dec 24, 2015 at 10:50 PM, Mirko Friedenhagen-2 [via Maven] < ml-node+s40175n5856095...@n5.nabble.com> wrote: > +1 > > Regards > Mirko > -- > Sent from

Re: Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

haha so sorry for the noise :-) On 27 December 2015 at 11:20, Michael Osipov <1983-01...@gmx.net> wrote: > Nobody is retiring Fluido Skin but only those in the subject. > > > Gesendet: Sonntag, 27. Dezember 2015 um 01:10 Uhr > > Von: "Olivier Lamy" > > An: "Maven Developers

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

Oliver, it's not a pressure. Such activities have already started, like retiring Maven 2, old parallel Maven 3 codelines, Eclipse plugin. I guess this is very important because we would only concentrate on one goal, for instance plugins @Java 1.6 and Maven 4. Makes sense? Of course we are

[GitHub] maven-plugins pull request: [MPMD-209] Upgrade to PMD 5.3.0

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