Re: Log4j Warning

Hi Arnaud, Do you plan a Release Version to merge this branch o master in Maven? On Tue, Jan 5, 2016 at 7:18 AM, Arnaud Héritier [via Maven] < ml-node+s40175n5857870...@n5.nabble.com> wrote: > Just because only 2.4 was available when I updated this feature branch few > months ago. > > Le mardi 5

Re: Log4j Warning

I really would like to see this branch landing in 3.4 for exemple. I think I opened a thread in october about this and didn't have a lot of feedback. The main problem is that with this branch I have some conflicts about slf4j api 1.5/1.6+ with some plugins that I don't really explain : https://gith

Re: [VOTE] Release Apache Maven JAR Utilities version 1.2

If the next version requires Maven 3, then its version number should be 3.0.0 Den 3 jan 2016 12:53 skrev "Michael Osipov" : > Am 2016-01-03 um 12:37 schrieb Hervé BOUTEMY: > >> the site uses old skin, because parent pom was not upgraded to 22: is this >> intentional? >> > > Yes, this is intentiona

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

GitHub user mcculls opened a pull request: https://github.com/apache/maven/pull/77 [MNG-5958] restore binary compatibility of Lifecycle.setPhases https://issues.apache.org/jira/browse/MNG-5958 While MNG-5805 restored binary compatibility of Lifecycle.getPhases it didn't do

Re: Question concerning common code for plugins

Hi, Looking at the list of affected plugins, they are all packaging plugins. How about maven-shared-packaging? Den 29 dec 2015 18:40 skrev "Karl Heinz Marbaise" : > Hi, > > currently i have identified several code parts like: > > handling of classifier (validation), creation of jar file names (re

[GitHub] maven pull request: MNG-4463: Version ranges cannot be used for ar...

Github user jvanzyl commented on the pull request: https://github.com/apache/maven/pull/64#issuecomment-169312032 No problem, many of us were on holiday and we'll sort it out eventually. --- If your project is set up for it, you can reply to this email and have your reply appear on Gi

Re: Log4j Warning

-1 Do not merge this branch. > On Jan 6, 2016, at 4:05 AM, Tibor Digana wrote: > > Hi Arnaud, > Do you plan a Release Version to merge this branch o master in Maven? > > On Tue, Jan 5, 2016 at 7:18 AM, Arnaud Héritier [via Maven] < > ml-node+s40175n5857870...@n5.nabble.com> wrote: > >> Just b

Re: Log4j Warning

thanks for this valuable comment Jason :( On Wed, Jan 6, 2016 at 1:46 PM, Jason van Zyl wrote: > -1 > > Do not merge this branch. > > > On Jan 6, 2016, at 4:05 AM, Tibor Digana wrote: > > > > Hi Arnaud, > > Do you plan a Release Version to merge this branch o master in Maven? > > > > On Tue, Ja

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user atanasenko commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169321926 +1 Turns out people do use this method.. Stuart, thanks for fixing! --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user michael-o commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169331471 @jvanzyl This looks like a safe merge. I would pull if you don't mind. --- If your project is set up for it, you can reply to this email and have your reply appear on Gi

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user michael-o commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169331588 @mcculls It would be great if you could an IT to the Core IT Suite. A negative and positive one. --- If your project is set up for it, you can reply to this email and h

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user atanasenko commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169332865 @michael-o, @mcculls I can also assist with tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If you

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user michael-o commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169349132 @atanasenko Давай, спасибо! --- 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

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user mcculls commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169349800 @atanasenko thanks, that would be helpful --- 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 d

Re: to delete windows build ?

I want to cut the release version 2.4.3 of m-shade-p. On Fri, Dec 18, 2015 at 4:37 PM, Hervé BOUTEMY wrote: > is there something to do on m-shade-p before releasing 2.4.3? > because this fixed plugin version would perfectly fit the parent poms > release I > have to do... > > Regards, > > Hervé

End Of Life Apache Maven 2.x

Hi devs, Do we have CMS for this page? http://maven.apache.org/maven-2.x-eol.html I should update plugin version to the latest Maven 2 compatible. -- Cheers Tibor

Re: Log4j Warning

I like colors :) So i was going to hack my private distribution :) On Wed, Jan 6, 2016 at 1:55 PM, Arnaud Héritier [via Maven] < ml-node+s40175n5857980...@n5.nabble.com> wrote: > thanks for this valuable comment Jason :( > > On Wed, Jan 6, 2016 at 1:46 PM, Jason van Zyl <[hidden email] >

Re: Log4j Warning

As we said previously when the the question arose again there would be a discussion. You may not remember, but I expect there to be a discussion. I have built a graph of Maven Central to analyze the rank (count of all incoming edges) for Log4J2 and Logback and it is clear from those numbers that

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user jvanzyl commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169376675 @michael-o +1, thanks very much! --- 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 h

Re: Log4j Warning

These are the numbers I arrived at, happy to run them with different coordinates but thought these were representative: gremlin> g.V('vc', 'log4j:log4j').inE.count() ==>84570 gremlin> g.V('vc', 'ch.qos.logback:logback-classic').inE.count() ==>62389 gremlin> g.V('vc

Re: Log4j Warning

great, more constructive feedback :-) Thanks Jason Both projects are well known and widely used even if log4j v2 is younger with less downloads such figures are not really representative with all caches/repositories managers I think. About logback vs log4j I have really no real preference technic

Re: Log4j Warning

+2 Am 2016-01-06 um 17:15 schrieb Jason van Zyl: As we said previously when the the question arose again there would be a discussion. You may not remember, but I expect there to be a discussion. I have built a graph of Maven Central to analyze the rank (count of all incoming edges) for Log4J2

Re: Log4j Warning

Just to make it clear. There are other Apache TLPs which are a one-man-show too and used almost everywhere ... this isn't anymuch better Am 2016-01-06 um 18:25 schrieb Arnaud Héritier: great, more constructive feedback :-) Thanks Jason Both projects are well known and widely used even if log4j

Would be possible to inject com.google.inject.Injector in a mojo or other component?

Hi, I have some components that implement the same interface. all of them are being properly registered by sisu. @Named(CommonMojoConstants.OCUS_PACKAGING) @Typed(Arcr.class) @Singleton public class IpArcrComponent implements Arcr I'm needing to control the injection in one speci

Maven Wagon provider docs

When I go to any of the Wagon provider pages [1], their project documentation is absent. Things like generated API reports, source reports, etc. are nowhere online. Is this intended, and how come? [1] https://maven.apache.org/wagon/wagon-providers/wagon-http/ Cheers, Paul

Re: Maven Wagon provider docs

Never mind. I found them. However, I would like to criticize the UI choices in this skin. I find it very counterintuitive that a menu tucked into a global header would change links based on your location. Global headers (or what looks like one here) should have permanent navigation items regardless

[VOTE] Release Apache Maven Shade Plugin version 2.4.3

Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12333879 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/i#issues/?jql=project+%3D+MSHADE+AND+status+%3D+Open+ORDER+BY+priority+DESC Staging repo: https://rep

Re: Log4j Warning

> On Jan 6, 2016, at 12:25 PM, Arnaud Héritier wrote: > > great, more constructive feedback :-) > Thanks Jason > > Both projects are well known and widely used even if log4j v2 is younger > with less downloads such figures are not really representative with all > caches/repositories managers I

[GitHub] maven pull request: [MNG-5958] restore binary compatibility of Lif...

Github user michael-o commented on the pull request: https://github.com/apache/maven/pull/77#issuecomment-169481891 Great, I will wait for the ITs and try both and merge. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Re: Log4j Warning

I am writing regarding this statement: "Ceki may do more commits but it’s certainly not a one man show. 76 contributors for Logback and 8 contributors for Log4J2." The numbers in themselves do not tell a full story. It's in appropriate to conclude that since 76 > 8, therefore logback is a better c

Re: Log4j Warning

A contributor on that page is not a comparison of committers vs not. People who have made pull requests to Maven are listed as contributors. Just as they would for Log4J2. A measure, albeit one, of the overall diversity of contribution. > On Jan 6, 2016, at 5:27 PM, Paul Benedict wrote: > > I

Re: Log4j Warning

Jason, I am sorry but to disagree with you. Your statistics are still not telling a full story. I can glance at the commit graphs of these 76 logback contributors rather quickly to see really how "diverse" this community is. * 35 (~45%) only ever made 1 contribution * 18 (~25%) have only ever made

Re: Log4j Warning

> On Jan 6, 2016, at 5:46 PM, Paul Benedict wrote: > > Jason, I am sorry but to disagree with you. Your statistics are still not > telling a full story. I can glance at the commit graphs of these 76 logback > contributors rather quickly to see really how "diverse" this community is. > > * 35 (~

Re: Would be possible to inject com.google.inject.Injector in a mojo or other component?

Hi Cristiano, Maven core doesn’t expose the “com.google.inject” package to plugins, which means the Injector class seen by your plugin is different to the class seen by core (this is due to classworlds isolation) which is why injecting the Injector is not currently possible. If the “com.google.

Re: Log4j Warning

I meant to say it’s not a simple thing even to make one simple change in an open source project. Typing after chopping wood it’s easy to miss some lttrs :-) > On Jan 6, 2016, at 5:49 PM, Jason van Zyl wrote: > >> >> On Jan 6, 2016, at 5:46 PM, Paul Benedict wrote: >> >> Jason, I am sorry but

Re: Log4j Warning

Arnaud, When I started this log4j2 branch, I was tired with this political no trough discussion etc.. (so I didn't move forward...) So except if you want to waste your time, try an other approach. IMHO I think the best is probably to create a plugin which update/configure a local distro with th

migrating Surefire to 3.0-RC1

I missing this import in MOJO after migrating plugin to 3.0 import org.apache.maven.shared.artifact.resolve.ArtifactResolver; The doc [1] says that maven-artifact-transfer should be used but it does not have yet a release version, or? org.apache.maven.shared maven-artifact-transfer 0.0.1

Re: Log4j Warning

@olamy instead of a plugin I would have loved to do this as an extension but I'm not sure it is technically possible. But clearly it would make sense for me to have this as an extension as now we have more more things possible in this area. @jason I won't fight, I just want some colors in our ugly

Re: migrating Surefire to 3.0-RC1

P=NP maven-compat made the trick org.apache.maven maven-compat On Thu, Jan 7, 2016 at 12:09 AM, Tibor Digana-2 [via Maven] < ml-node+s40175n5858124...@n5.nabble.com> wrote: > I missing this import in MOJO after migrating plugin to 3.0 > > > import org.apache.maven.shared.artifact.resolve

Re: Log4j Warning

I mean a plugin which update the local install. i.e: mvn logging:update-dist -dimplementation=log4j2 -DlocalInstall= (optional per default the current used install) This will download the artifacts and install them in the target local distro. That's a sort of extension. Maybe I don't understand wh

Re: Log4j Warning

Something that we can configure directly in ${maven.multiModuleProjectDirectory}/.mvn/extensions.xml 1. 2. 3. 4. org.apache.maven.ext 5. log4j2 6. 1.0 7. 8. or in the pom 1. 2. 3. 4. org.apache.maven.ext 5. log4j2 6. 1.0 7. 8. 9.

Re: Log4j Warning

Jason, I really don’t care which logging framework Maven uses. There isn’t going to be much difference between Logback and Log4j 2 in a batch process like Maven, although asynchronous loggers might speed up larger builds somewhat. However, these comparisons are still incorrect. Log4j is using t

Re: Log4j Warning

I’ve no issue with the fix to make any implementation to work, just the merging of the log4j2 branch in general. > On Jan 6, 2016, at 7:20 PM, Ralph Goers wrote: > > Jason, > > I really don’t care which logging framework Maven uses. There isn’t going to > be much difference between Logback an

Re: Log4j Warning

This isn't a mail to convince anyone between Log4J2 or Logback. I have updated my Maven installation with Log4J2, instead of the default, which worked fine. I missed one thing and I hope with different log implementations we still could do this "right". Maven has a nice command line parameter to

Re: Log4j Warning

It is already possible to implement advanced logging as an extension. This was what I did when my offer to provide multi-threaded logging support in the core was turned down on this list few months ago. So at this point the discussion/decision is purely political. -- Regards, Igor On Wed, Jan 6,