Re: migrating Surefire to 3.0-RC1

2016-01-08 Thread Kristian Rosenvold
I would recommend that you instead update the existing wiki page that we use to gather "tips" about migrating plugins: https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies Kristian 2016-01-08 1:18 GMT+01:00 Tibor Digana : > Hi Andreas, > > See Robert's cha

Re: Log4j Warning

2016-01-08 Thread Tamás Cservenák
If there would be a vote about questions written below, I'd vote +1 to all of them: - No any kind of logging backend should enter core, ever. Project already agreed on use of SLF4j _facade_ (I consider slf4j as NOT violating this requirement. It is very elastic by letting you choose backend for it

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
> On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: > > On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: > >> No, I don’t that useful. If it’s an extensions then it can be activated >> using the .mvn/extensions.xml and downloaded on demand. I think for Maven >> 4.x we just bite the bullet an

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4.3

2016-01-08 Thread Kristian Rosenvold
+1 2016-01-07 18:59 GMT+01:00 Tibor Digana : > `+1 > > On Wed, Jan 6, 2016 at 10:05 PM, Tibor Digana-2 [via Maven] < > ml-node+s40175n5858080...@n5.nabble.com> wrote: > > > Hi, > > > > We solved 4 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
Ralph, The simple fact of the matter is that Log4J2 appears to have little to no user traction at all. This suggests to me that the community forked into the next generation by way of Logback and Log4J2. The community appears to have gone in the direction of Logback. By a very large margin, at

[GitHub] maven-integration-testing pull request: [MNG-5958] restore binary ...

2016-01-08 Thread michael-o
Github user michael-o commented on the pull request: https://github.com/apache/maven-integration-testing/pull/13#issuecomment-169988105 Just trying to run the ITs without your patch first. --- If your project is set up for it, you can reply to this email and have your reply appear on

Re: migrating Surefire to 3.0-RC1

2016-01-08 Thread Tibor Digana
Hi Kristian, I do not have edit permissions in confluence. Who can grant me? On Fri, Jan 8, 2016 at 9:41 AM, Kristian Rosenvold-4 [via Maven] < ml-node+s40175n5858379...@n5.nabble.com> wrote: > I would recommend that you instead update the existing wiki page that we > use to gather "tips" about

Re: Log4j Warning

2016-01-08 Thread Ralph Goers
On traction we can agree to disagree. Logback may be more popular but we are pretty busy answering user's questions, and making enhancements and fixes. I follow the Logback lists and actually see less activity there. And I continue to see users ask frameworks to support Log4j 2. Frankly, I was s

[GitHub] maven-integration-testing pull request: [MNG-5958] restore binary ...

2016-01-08 Thread michael-o
Github user michael-o commented on the pull request: https://github.com/apache/maven-integration-testing/pull/13#issuecomment-170016837 Seems like I can't run the tests in a locked down environment, regardless of a Nexus instance and am HTTP proxy. Artifact resolution always points to

[GitHub] maven-integration-testing pull request: [MNG-5958] restore binary ...

2016-01-08 Thread atanasenko
Github user atanasenko commented on the pull request: https://github.com/apache/maven-integration-testing/pull/13#issuecomment-170025305 I've had troubles running tests when following official guidelines [1]. But changing 'mvn clean test ...' to 'mvn clean install ...' helped.

[Jigsaw] Fwd: Specifying module paths

2016-01-08 Thread Robert Scholte
FYI, a new idea to solve our modulepath issue. Any feedback is appreciated. thanks, Robert Forwarded Message Subject:Specifying module paths Date: Thu, 07 Jan 2016 15:39:43 -0800 From: Jonathan Gibbons To: jigsaw-dev This is a follow-up to some of the recent em

Re: [Jigsaw] Fwd: Specifying module paths

2016-01-08 Thread Paul Benedict
It sounds like Maven will have to generate many .properties file in a build. 1) Modules to compile main source 2) Modules to compile test source 3) Modules to execute tests 4) And what about forking? I am concerned #4 is going to create issues unless the .properties file name is unique enough. Per

Re: Log4j Warning

2016-01-08 Thread Dennis Lundberg
Hi, The sometimes heated discussion in this thread shows that there are strong opinions about logging implementation. That for me is a reason to not bundle one by default. Let us focus on making it as simple as possible for our end users to configure which one they want to use. I'm not familiar

Running core ITs with external resolution

2016-01-08 Thread Michael Osipov
Hi folks, I cannot pass any core IT w/ external resolution. The outcome in the logs is almost the same: "could not find artifact org.apache.maven:maven-settings:jar:2.0 in central (file:target/null)" and alike. Running tests with Maven 3.3.3 with mvn clean install -Prun-its -Dmaven.it.cent

Re: Log4j Warning

2016-01-08 Thread Gary Gregory
On Fri, Jan 8, 2016 at 4:12 AM, Jason van Zyl wrote: > > > On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: > > > > On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: > > > >> No, I don’t that useful. If it’s an extensions then it can be activated > >> using the .mvn/extensions.xml and downloa

Re: migrating Surefire to 3.0-RC1

2016-01-08 Thread Andreas Gudian
Adding maven-compat for the test did the trick for now in my case. If only I had read that wiki page before, because it actually describes this already... :-D 2016-01-08 14:55 GMT+01:00 Tibor Digana : > Hi Kristian, > > I do not have edit permissions in confluence. Who can grant me? > > On Fri,

[GitHub] maven-surefire pull request: Adding individual rerun times to XML ...

2016-01-08 Thread Tibor17
Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/96#issuecomment-170148843 @lamyaa Hi how are you? We should recover activity on this issue. As for your information, I created a separate branch 3.0-rc1 and the master branch is re

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
You’re welcome. I do try to bring a chuckle to everyone’s day. > On Jan 8, 2016, at 3:48 PM, Gary Gregory wrote: > > On Fri, Jan 8, 2016 at 4:12 AM, Jason van Zyl wrote: > >> >>> On Jan 7, 2016, at 9:17 PM, Gary Gregory wrote: >>> >>> On Thu, Jan 7, 2016 at 7:26 AM, Jason van Zyl wrote: >>

Re: Log4j Warning

2016-01-08 Thread Jason van Zyl
> On Jan 8, 2016, at 3:21 PM, Dennis Lundberg wrote: > > Hi, > > The sometimes heated discussion in this thread shows that there are strong > opinions about logging implementation. That for me is a reason to not > bundle one by default. > > Let us focus on making it as simple as possible for o

Re: Log4j Warning

2016-01-08 Thread Tamás Cservenák
So, just for fun (and healing flue): https://github.com/apache/maven/compare/slf4j-gossip Does colouring by default in 80kb "extra" payload (but removes slf4-simple and many other cruft). Now, _the theory_ says, that an extension could do Log.configure( ILoggerFactory ) And from that moment on

[GitHub] maven-surefire pull request: Adding individual rerun times to XML ...

2016-01-08 Thread lamyaa
Github user lamyaa commented on the pull request: https://github.com/apache/maven-surefire/pull/96#issuecomment-170191124 @Tibor17 Hi Tibor. I'm doing great, thanks. Congrats on the release! :) I'll work on this in the next couple of days to resolve conflicts and test it again

[GitHub] maven-surefire pull request: Adding individual rerun times to XML ...

2016-01-08 Thread Tibor17
Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/96#issuecomment-170199857 >>Should I then make a new pull request for 3.0-rc1? no, no. Just keep going in the master. Thx. On Sat, Jan 9, 2016 at 5:15 AM, lamyaa wrote: