Re: [VOTE] Release Apache Software Foundation Parent POM version 35

+1 LieGrue,strub On Thursday, 12 June 2025 at 21:31:26 CEST, Matthias Bünger wrote: +1 (nb) Am 10.06.2025 um 07:06 schrieb Sylwester Lachiewicz: > +1 > > pon., 9 cze 2025, 22:59 użytkownik Slawomir Jaranowski < > s.jaranow...@gmail.com> napisał: > >> Hi, >> >> We solved 5 issues: >> ht

Re: Loging api in JSR-330 component

+1Technically from a pure ClassLoader point our very own makes more sense.We can probably think about Lambda to resolve the String lazily.Insofar the SLF4J api is outdated as well. And of course internally we might still route to slf4j. But we should not expose those classes to the plugins if n

Re: Loging api in JSR-330 component

    @Inject     private Logger??? logger; That would imo depend on the package of the Logger in the import. There could be producers for both our internal maven logging api and SLF4J. LieGrue,strub On Friday, 22 January 2021, 19:19:47 CET, Slawomir Jaranowski wrote: It is not only a

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.2

+1 LieGrue,strub On Sunday, 24 January 2021, 00:02:35 CET, Sylwester Lachiewicz wrote: Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12347024&styleName=Text There are still a couple of issues left in JIRA: https://issues.apa

Re: cdi-api leaking?

+1 for dropping. Also already had problems with it. LieGrue, strub > Am 01.12.2020 um 17:50 schrieb Romain Manni-Bucau : > > Up, > > Encountered a few bugs related to this regression, wonder how we want to > tackle it. > My 2cts would be to drop cdi-api and replace the single used > annotation

Re: DirectoryScanner, exclusions wins or loose over inclusions?

Don't we configure those patterns mostly directly in the poms? Ditching our own DirectoryScanner would likely require a huge amount of existing projects to rewrite their config when they update some plugins. Don't think this is really worth it. Plus the Java7 directoryScanner is not really faste

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

+1 Thanks Hervé, was on my list for the next weeks as well ;) LieGrue, strub > Am 09.02.2020 um 10:24 schrieb Hervé BOUTEMY : > > Hi, > > We solved 28 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=1230&styleName=Text > > Staging repo: > http

Re: [maven-shade-plugin] 3.2.2 status and open PRs

I'll try to give it a look over the weekend. LieGrue, strub > Am 16.01.2020 um 23:31 schrieb Falko Modler : > > Hi Karl Heinz, > > thanks for this clarification. > > So now there is only one last ticket left for 3.2.2 and the PR for it > looks good to be merged: > https://github.com/apache/ma

Re: [VOTE] Release Apache Parent POM version 22

+1 LieGrue, strub > Am 05.01.2020 um 18:45 schrieb Hervé BOUTEMY : > > Hi, > > We solved N issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12343925&styleName=Text > > https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22 > > S

Re: Absolute and relative paths in plugins and descriptors

hould be interpreted as an absolute > path, and AFAIK the warning is there already for ages so I don't mind > changing the behavior. > > thanks, > Robert > On 1-1-2020 23:26:00, Mark Struberg wrote: > Hi lords and ladies! > > I try to get my head around the ticke

Absolute and relative paths in plugins and descriptors

Hi lords and ladies! I try to get my head around the ticket MASSEMBLY-775. It is related to MASSEMBLY-746 and MASSEMBLY-665. The problem is basically that a reference to /somedirectory is interpreted as absolute path on *nix and as relative path on Win*. And sometimes we have code of the form

Re: More checkstyle API changes

But the main purpose is not to have multiple frameworks run with it. That's the main difference to surefire. The maven-checkstyle-plugin is rather pretty much hardcoded to a specific checkstyle version. While you _could_ technically exchange the checkstyle dependency it is not really intended.

Re: relativePath for parent poms in our plugins

t;> >>>> Robert >>>> On 21-12-2019 12:33:53, Hervé BOUTEMY wrote: >>>> disagree >>>> >>>> We have the repo configuration which brings a location for every Git >>>> repository: >>>> https://maven.apache.org/scm.htm

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1

+1 LieGrue, strub > Am 16.12.2019 um 19:37 schrieb Hervé BOUTEMY : > > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12346480&styleName=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1545/ >

Re: [massembly] code question

rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le jeu. 19 déc. 2019 à 14:39, Mark Struberg a &

[massembly] code question

Hi! Feeling a bit rusty, so I thought I better ask for a 2nd opinion. To me it looks like the following code block is really obsolete and did not make anything useful ever since https://github.com/apache/maven-assembly-plugin/blob/master/src/main/java/org/apache/maven/plugins/assembly/archive/t

relativePath for parent poms in our plugins

Hi folks! Looking at massembler right now I stumbled across a parentPom section maven-plugins org.apache.maven.plugins 33 ../../pom/maven/maven-plugins/pom.xml This was perfectly fine when we had all in SVN under one big project. But nowadays - having all in GIT - I'd we should remove

Re: Jenkins and Maven 3.0.5 or JDK 7

Hi folks! Having dozen sub repos in GIT is still a PITA. Also git-submodules is still sub-optimal and at best a smallish helper. For me personally there is one major decision point if it comes to deciding whether to hav one big repo or multiple smaller ones: the deliverable. Is there exactly o

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

> I like this idea of avoiding force pushing, but I'm not git expert to know > exactly if this gives exactly the intended result = start clean and not > have noise when doing bisects or git blame It's clean for our own repo but might probably screw up cloned repos as they cannot just git-pull an

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

+1 LieGrue, strub > Am 08.06.2015 um 12:32 schrieb Jason van Zyl : > > +1 > >> On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise wrote: >> >> Hi, >> >> We solved 14 issues: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393 >> >> There are still a c

Re: [VOTE] Add Manfred Moser as committer

+1 on Manfred, even thought he is already^^ LieGrue, strub PS: usually committer votes are held on the private lists…:wq > Am 13.05.2015 um 17:13 schrieb Stephane Nicoll : > > +1 > > S. > > On Wed, May 13, 2015 at 8:55 AM, Hervé BOUTEMY > wrote: > >> Hi, >> >> I'd like to introduce Manfred

Re: [VOTE] ASF Parent POM Version 17

nope, go on you even have 4 already: Kristian, Jason, you, me http://people.apache.org/committers-by-project.html#maven-pmc LieGrue, strub > Am 27.04.2015 um 20:37 schrieb Karl Heinz Marbaise : > > Hi, > > here is my +1. > > need two more binding VOTES... > > Kind regards > Karl Heinz Marb

Re: [VOTE] ASF Parent POM Version 17

+1 tested with 2 projects without issues. LieGrue, strub > Am 24.04.2015 um 21:08 schrieb Karl Heinz Marbaise : > > Hi, > > We solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12329009 > > Staging repo: > https://repository.apache.org/cont

Re: [VOTE] Release Wagon 2.9

indeed, then it passed twice ;) LieGrue, strub > Am 27.04.2015 um 17:01 schrieb Jason van Zyl : > > You have checked Maven 3.3.3 so really you have already checked Wagon 2.9 :-) > > On Apr 27, 2015, at 10:59 AM, Mark Struberg wrote: > >> +1 >> >> only

Re: [VOTE] Release Wagon 2.9

+1 only did simple checks (work) and checked source. looks good so far LieGrue, strub > Am 27.04.2015 um 16:52 schrieb Kristian Rosenvold > : > > +1 > 27. apr. 2015 16.01 skrev "Stephen Connolly" < > stephen.alan.conno...@gmail.com>: > >> +1 (you beat me to my vote on core, but you can have

Re: [VOTE] Maven 3.3.3 Release

set MAVEN_SKIP_RC=1 when invoking mvn >> with the combined MAVEN_OPT setting. This should stop it getting reset in >> the mvn script and allow the debug settings to pass through. >>> >>> On Apr 26, 2015, at 2:12 AM, Mark Struberg >> (mailto:strub...@yahoo.de)> w

Re: [VOTE] Maven 3.3.3 Release

+1 The problem I have with mvnDebug on OSX cmd line seems to be there in older 3.3.x versions already. So 3.3.3 is at least better than 3.3.2. We should really fix this in the next version. But otherwise the release looks good. LieGrue, strub > Am 25.04.2015 um 23:45 schrieb Mark Derricutt :

Re: mvnDebug with problems

+1 sounds like a plan. LieGrue, strub > Am 24.04.2015 um 18:55 schrieb Andreas Gudian : > > In the windows script, I introduced a new variable for the debug settings - > perhaps we can do the same for the shell scripts. > > Am Freitag, 24. April 2015 schrieb Francisco Collao Gárate : > >> Yep

Re: [VOTE] Maven 3.3.3 Release

that's where we changed the scripts. > > I'm using your exact MAVEN_OPTS and it's working here to startup and debug in > Eclipse. > > On Apr 24, 2015, at 8:20 AM, Mark Struberg wrote: > >> Re-tested with 3.3.2 and it doesn’t work there neither on my box.

Re: [VOTE] Maven 3.3.3 Release

rue, strub > Am 24.04.2015 um 14:08 schrieb Jason van Zyl : > > Working fine here. The scripts haven't changed since the end of February. > > Anyone else confirm an issue with remote debugging? > > On Apr 24, 2015, at 3:24 AM, Mark Struberg wrote: > >> maybe I

Re: [VOTE] Maven 3.3.3 Release

maybe I missed some change, but I cannot run mvnDebug anymore. It nicely says that I start in debug mode, but doesn’t open a debug port and neither doesn’t wait for me to attach. Anything I missed, or is this really a regression? txs and LieGrue, strub > Am 22.04.2015 um 14:22 schrieb Jason

Re: [VOTE] Release Apache Maven Release Plugin version 2.5.2

+1 LieGrue, strb > Am 19.04.2015 um 14:28 schrieb Robert Scholte : > > Hi, > > We solved 13 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12331215 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=p

libs in mavens /lib folder

Hi! I'm quite confused by the sheer amount of libs we already have in our lib folder. For maven-3.2.1 this is 133957 7. Mai 2013 aether-api-0.9.0.M2.jar 12637 14. Feb 2014 aether-api.license 34117 7. Mai 2013 aether-connector-wagon-0.9.0.M2.jar 12637 14. Feb 2014 aether-connector-wagon.license 1

Re: incremental compiler questions

Hi Martin! The maven-compiler plugin already does this. But once a single change is detected then we need to recompile the _whole_ module because of the reasons explained by Igor. Pro of JDT: you can e.g. also see if there were only 'internal' changes and thus the other dependencies don't need

Re: [VOTE] Release Apache Maven WAR Plugin version 2.6

works fine over here. rat fine as well. +1 LieGrue, strub > On Thursday, 8 January 2015, 21:21, Karl Heinz Marbaise > wrote: > > Hi, > > We solved 12 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&version=20681 > > There are still a couple of issues left in

Re: javac bootclasspath and java8

Hi Paul! Txs, this is definitely one possible direction in which we could aim. LieGrue, strub > On Saturday, 29 November 2014, 11:18, Paul Moloney > wrote: > > Hi > > I had written this rule for the enforcer plugin which actually checks the > label of jdk version in toolchains against out

Re: javac bootclasspath and java8

;>the like.) >>- Have a factory class, with code like the following: >> >>private static final IRTUser instance = newRTUser(); >> >>private static IRTUser newInstance() { >> try { >>return new JDK18RTUser(); >> } catch (Throwable t0)

Re: Ivy style versions propagating in Maven central

+1 if they like to use Mavens infrastructure then they also need to play according to those rules. Anyone likes to talk with the Ivy guys? They have to fix this. Another question is what we do with those existing poms in maven.central? Do we convert them? What about sha1, md5 and asc in that c

Re: javac bootclasspath and java8

Hi! > This lets you selectively forbid certain methods The problem is that the methods used are perfectly fine. The API methods used in our program do exist even in Java6. But they get coerced to different methods when compiling with Java8. And those new methods do not exist in Java7 and ol

javac bootclasspath and java8

Hi! Today I had a discussion with Robert about how we can solve a problem I had over at Apache OpenWebBeans: https://issues.apache.org/jira/browse/OWB-952 As a short summary: the classes provided in rt.jar of Java8 are slightly different than the ones from Java7 and 6. Similar big differences

Re: [VOTE] Change project logo and adopt owl as mascot

+1 really like the new logo (or better any of those owls). LieGrue, strub > On Tuesday, 25 November 2014, 12:02, Arnaud Héritier > wrote: > > +1 > > thx > > > On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> +1 >> >> On 25 November

Re: ApacheCon EU 2014, Budapest

Hiho! I will attend and arrive monday morning. Sigfried Göschl will also be in Budapest. LieGrue, strub > On Wednesday, 5 November 2014, 9:32, Tamas Cservenak > wrote: > > Don’t worry about the details. All the kidnapped people will get what they > deserve ;) > > Thanks, > ~t~ > > > On

Re: Hangout summary?

k Derricutt wrote: >> > On 4 Jul 2014, at 9:33, Robert Scholte wrote: >> >> If I'm correct, following have joined at least 2 times or are Maven PMC >> >> 22:00-23:00 (CEST) Robert Scholte, Hervé Boutemy, Karl-Heinz Marbaise, >> >> Mark Struberg >

Re: [DISCUSS] [apache-parent] Xdoclint for Java8 support

ld could have failed due to the changes of the javadoc executable. >Add to that message the xdoclint options to get the original behavior. > >regarding the parent, we probably also want to add -reference ( as  >suggested by one of the Oracle developers ) > >thanks, >Robert >

[DISCUSS] [apache-parent] Xdoclint for Java8 support

Hi! Building with Java8 breaks buiding JavaDocs many existing maven projects. And thus most times also breaks releasing them. The reason is that they enabled all warnings and errors now by default. This means that we get tons of oddly broken builds because it also breaks for missing @param, etc

Re: [VOTE] Apache Maven Shade Plugin 2.3

+1 LieGrue, strub > On Thursday, 1 May 2014, 10:22, Kristian Rosenvold > wrote: > > +1 > > > > 2014-05-01 6:48 GMT+02:00 Olivier Lamy : > >> my +1 >> >> >> On 29 April 2014 15:24, Olivier Lamy wrote: >> > Hi, >> > I'd like to release Apache Maven Shade Plugin 2.3. >> > The main

Re: [VOTE] Release Maven Surefire Plugin version 2.17

+1 (binding) LieGrue, strub On Wednesday, 12 March 2014, 22:53, Andreas Gudian wrote: Hi, > >long ago since we released the last Surefire version. It's about time we >change that ;-). > >We solved 16 issues: >https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19536

Re: [VOTE] Release Apache Maven Filtering version 1.2

+1 LieGrue, strub > On Saturday, 8 March 2014, 17:13, Hervé BOUTEMY wrote: > > +1 > > Regards, > > Hervé > > Le jeudi 6 mars 2014 22:08:10 Robert Scholte a écrit : >> Hi, >> >> We solved 5 issues: >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=187 >> 29

Re: [VOTE] Release ASF Parent POM version 14

+1 LieGrue, strub > On Thursday, 6 March 2014, 22:19, Hervé BOUTEMY wrote: > > Hi, > > Changes since the last release: > http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h > > Staging repo: > https://repository.apache.org/content/repositories/o

Re: [VOTE] Release Apache Maven Checkstyle Plugin version 2.12

+1 and thanks for pushing this, Dennis! LieGrue, strub > On Saturday, 8 March 2014, 23:50, Dennis Lundberg wrote: > > Hi, > > We solved 15 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=19723 > > There are still a couple of issues left i

Re: [VOTE] Release Maven Release version 2.5

+1 (binding) src looks good, did a small local test release on a simple project which did run fine. txs and LieGrue, strub On Sunday, 23 February 2014, 15:50, Benson Margulies wrote: Hi, > >maven-release is a component that provides the maven-release-manager >and the maven-release-plugi

Re: [VOTE] Maven 2.x is end of life

+1 LieGrue, strub On Thursday, 13 February 2014, 18:42, Andreas Gudian wrote: +1 > >:-) > >Am Donnerstag, 13. Februar 2014 schrieb Hervé BOUTEMY : > >> +1 >> >> Regards, >> >> Hervé >> >> Le jeudi 13 février 2014 15:14:03 Stephen Connolly a écrit : >> > We have not made a release of Maven

Re: [VOTE] Release Apache Maven SCM Publish Plugin version 1.0

+1 LieGrue, strub > On Monday, 3 February 2014, 11:21, Stephen Connolly > wrote: > > +1 > > spot checks to confirm that Robert beat me to my standard tests: pass > > > > On 2 February 2014 11:11, Robert Scholte wrote: > >> +1 >> >> rat: only approved licenses >> sha1: correct >>

Re: Maven Core moving to 1.6

+1 LieGrue, strub - Original Message - > From: Stephen Connolly > To: Maven Developers List > Cc: > Sent: Saturday, 5 October 2013, 9:35 > Subject: Re: Maven Core moving to 1.6 > > +1 > > > On Saturday, 5 October 2013, Jason van Zyl wrote: > >> Given the vote we had about relea

Re: Leaving Maven Core POMs at major.minor-SNAPSHOT

se bugs against a non-exist any version! >> >> On Saturday, 14 September 2013, Jason van Zyl wrote: >> >> > We need a slight modification of this strategy because the changes > need >> to >> > be pushed somewhere so that people can examine the tag if th

Re: Leaving Maven Core POMs at major.minor-SNAPSHOT

e VOTE has succeeded. LieGrue, strub > > From: Fred Cooke >To: Maven Developers List ; Mark Struberg > >Sent: Saturday, 14 September 2013, 21:43 >Subject: Re: Leaving Maven Core POMs at major.minor-SNAPSHOT > > > >I believe the str

Re: Leaving Maven Core POMs at major.minor-SNAPSHOT

wrote: > >> We need a slight modification of this strategy because the changes need to >> be pushed somewhere so that people can examine the tag if they want during >> the release. I can't keep it on my machine until the vote passes. >> >> On Sep 14, 2013, at

Re: Leaving Maven Core POMs at major.minor-SNAPSHOT

e the tag if they want during the > release. I can't keep it on my machine until the vote passes. > > On Sep 14, 2013, at 2:20 PM, Mark Struberg wrote: > >> +1, that's what we also use in DeltaSpike and dozen other projects. >> pushChanges=fal

Re: Leaving Maven Core POMs at major.minor-SNAPSHOT

+1, that's what we also use in DeltaSpike and dozen other projects. pushChanges=false + localCheckout=true for the win! LieGrue, strub - Original Message - > From: Arnaud Héritier > To: Maven Developers List > Cc: > Sent: Saturday, 14 September 2013, 19:45 > Subject: Re: Leaving Ma

Re: What is the correct Git SCM URL for a branch?

I found that most people use false and true Which renders most of the stuff useless in GIT. LieGrue, strub - Original Message - > From: Fred Cooke > To: Maven Developers List > Cc: > Sent: Saturday, 10 August 2013, 15:19 > Subject: Re: What is the correct Git SCM URL for a branc

Re: [VOTE] Release Maven Surefire Plugin version 2.15

+1 LieGrue, strub - Original Message - > From: Andreas Gudian > To: Maven Developers List > Cc: > Sent: Friday, 7 June 2013, 8:29 > Subject: [VOTE] Release Maven Surefire Plugin version 2.15 > > Hi, > > This is my first release, so please check carefully what I may have missed > :

Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)

+1 did run it the last 2 days on many of my projects without any issues. LieGrue, strub - Original Message - > From: Brian Fox > To: Maven Developers List > Cc: > Sent: Tuesday, 4 June 2013, 18:13 > Subject: Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4) > > +1 > > On Sat, Jun 1, 2013

Re: [VOTE] Apache 3.1.0-alpha-1

alpha-1 to n works fine imo. We should not loose pace by holding up the effort with such minor stuff. LieGrue, strub - Original Message - > From: Baptiste Mathus > To: Maven Developers List > Cc: > Sent: Wednesday, 29 May 2013, 8:47 > Subject: Re: [VOTE] Apache 3.1.0-alpha-1 > > L

Re: [VOTE] Release Maven Release Plugin version 2.4.1

+1 LieGrue, strub - Original Message - > From: Robert Scholte > To: Maven Developers List > Cc: > Sent: Monday, March 25, 2013 9:17 PM > Subject: Re: [VOTE] Release Maven Release Plugin version 2.4.1 > > +1 > > Op Sat, 23 Mar 2013 11:57:49 +0100 schreef Robert Scholte  > : > >>

Re: [VOTE] Release Maven Indexer 5.1.1

+1 (for the vote) and +1 for waiting the full 72h ;) LieGrue, strub - Original Message - > From: Tamás Cservenák > To: Maven Developers List > Cc: > Sent: Thursday, March 7, 2013 3:11 PM > Subject: Re: [VOTE] Release Maven Indexer 5.1.1 > >T rue, it will pass in 3 hrs from now. >

Re: [VOTE] formally end support for Maven 1

+1 LieGrue, strub - Original Message - > From: Ralph Goers > To: Maven Developers List > Cc: > Sent: Wednesday, March 6, 2013 8:06 PM > Subject: Re: [VOTE] formally end support for Maven 1 > > +1 > > > Ralph > > On Mar 2, 2013, at 7:18 AM, Benson Margulies wrote: > >> Based on

Re: [VOTE] Apache Maven 3.0.5

+1 works fine. Tested with a few big real world projects. rat looks fine, signature ok. LieGrue, strub - Original Message - > From: Olivier Lamy > To: Maven Developers List > Cc: > Sent: Tuesday, February 19, 2013 4:28 PM > Subject: [VOTE] Apache Maven 3.0.5 > > Hi, > We fixed 1 i

Re: [VOTE] Maven Pmd Plugin 3.0 (take 2)

+1 LieGrue, strub - Original Message - >>> On Feb 15, 2013 12:40 AM, "Olivier Lamy" > wrote: >> >>> ping. one binding +1 is still missing. >>> Thanks >>> >>> 2013/2/11 Olivier Lamy : +1 2013/2/7 Olivier Lamy : > Hi, > I'd like to release Maven Pmd Pl

Re: EOL of 1.5 as minimum

What are the big features and possibilities we gain from 1.6? Build systems are pretty late in the chain. We should still be able to build on systems which are 2+ years old. Is there a technical reason to restrict this or is it just that we don't actively support it anymore (not doing IT, etc

Re: [VOTE] ASF Parent pom 13 and Maven parent pom 23

Yes, exactly as Robert explained. Previously to this change we created broken JARs. People always had to do mvn clean install :/ We will continue working on this area. The goal is that a mvn verify on a project creates reliable results and only does the work it really needs to do. Though in ge

Re: [VOTE] ASF Parent pom 13 and Maven parent pom 23

+1 LieGrue, strub - Original Message - > From: Olivier Lamy > To: Maven Developers List > Cc: > Sent: Thursday, January 17, 2013 9:17 PM > Subject: [VOTE] ASF Parent pom 13 and Maven parent pom 23 > > Hi, > I'd like to release both ASF Parent pom 13 and Maven parent pom 23 > > ASF

Re: Logging

Sorry Stephen, I find this comparison unfair. Please look how much code has been written and is necessary to get slf4j (and any other non MojoLogger impl) really running. And for making it fully work it will need even more work because we first need to ship all plugins with an upgraded maven-pl

Re: [VOTE] Maven Shared Utils 0.2

+1 LieGrue, strub - Original Message - > From: Robert Scholte > To: Maven Developers List > Cc: > Sent: Sunday, December 16, 2012 12:23 PM > Subject: Re: [VOTE] Maven Shared Utils 0.2 > > +1 > > Op Sun, 16 Dec 2012 04:21:50 +0100 schreef Kristian Rosenvold  > : > >> Thanks ! ht

Re: Logback in Maven Core

I only do those benchmarks on a desktop linux box with the cpu governer set to a fixed frequency. Imo that's the only way to get reproducible numbers. Especially when working on a notebook it also depends how much heat the notebook can dissipate. I've seen my MBP not using his full turbo when he

Re: Logback in Maven Core

-1.5 anymore with this new version of maven! LieGrue, strub - Original Message - > From: ceki > To: Maven Developers List > Cc: > Sent: Tuesday, December 11, 2012 10:13 PM > Subject: Re: Logback in Maven Core > > On 11.12.2012 21:28, Mark Struberg wrote: > >

Re: Logback in Maven Core

btw, jason mentioned that lots of apache frameworks already use SLF4J. And he prominently mentioned CXF. Now here comes the bitter truth: THEY DROPPED IT AGAIN! They now use a java.util.logging.Logger facade to redirect to log4j, slf4j or whatever http://svn.apache.org/repos/asf/cxf/trunk/api/s

Re: Logback in Maven Core

folks, don't you see it? we cannot use logback as this is a LocationAwareLogger and would break all projects which use slf4j < 1.6 and older. Please go back to the original mail from 4 month where Ceki himself explained it! So -1 on logback LieGrue, strub - Original Message - > Fro

Re: Logging

sorry, you are right, should have been slf4j-simple, etc. - Original Message - > From: Anders Hammar > To: Maven Developers List > Cc: > Sent: Monday, December 10, 2012 11:20 AM > Subject: Re: Logging > >> Another thing to remember is that logback is a LocationAwareLogger afaik >>

Re: Logging

To be honest. Slf4J is really mature. The fact that we need some 'special treatment' for maven worries me. Are we are trying to do things with slf4j-simple it never was intended for? Again: I think sjf4j is really mature, so I guess the error is on our side. And you also mentioned that Ceki did s

Re: [DISCUSS] the art of logging - was: [VOTE] Maven 3.1.0

ars, etc if you did not do a full clean upfront... We added a few ITs for it, but obviously not enough. Hope those additional changes are also backed by ITs. LieGrue, strub > > From: Jason van Zyl >To: Maven Developers List ; Mark Struberg > &g

Re: Logging

+1 LieGrue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Monday, December 10, 2012 9:32 AM > Subject: Re: Logging > > As for options; there is also the option of accepting that the > technical challenges were slightly larger than a

Re: Logging

Another thing to remember is that logback is a LocationAwareLogger afaik (log4j-simple is not!) thus it suffers from the API compat problem. By exposing it in the maven core class realm we might trash all projects with slf4j < 1.6. This even got acknowledged by Ceki... This was the reason why we

Re: [DISCUSS] the art of logging - was: [VOTE] Maven 3.1.0

+1, that sounds like a good balance between old compat behaviour and moving forward! > Strategies to write a plugin using slf4j-api from core without requiring > Maven > 3.1 still need to be found: Maybe that's easier than you think. Just declare an slf4j-api dependency to the plugin. If the

Re: [DISCUSS] the art of logging - was: [VOTE] Maven 3.1.0

still there have been twice as many problem reports as +1. Afaik we've never shipped a release in such a bad state to be honest. LieGrue, strub - Original Message - > From: Benson Margulies > To: Maven Developers List ; Mark Struberg > > Cc: > Sent: Friday, D

Re: [DISCUSS] the art of logging - was: [VOTE] Maven 3.1.0

e. >> >> >> On Fri, Dec 7, 2012 at 7:57 AM, Mark Struberg > wrote: >> >>> Daniel, please think through these old project scenarios. Those old >>> projects did ship their own slf4j impl + config and parsed their own > logs >>> and extrac

Re: [VOTE] Maven 3.1.0

; current trunk. I cannot see how we can seriously release this to users right > now. > > > > I don't consider them broken.  I consider them fixed.    Old plugins that > use SLF4J now get there information properly integrated with the rest of the > maven informatio

Re: [VOTE] Maven 3.1.0

__ > From: Stephen Connolly >To: Maven Developers List ; Mark Struberg > >Sent: Friday, December 7, 2012 12:48 PM >Subject: Re: [VOTE] Maven 3.1.0 > > >But not all of those *need to*. At least until now they have needed to, but >going forward they may

Re: [VOTE] Maven 3.1.0

basically all stuff which integrates maven does *funky logging stuff*... - Original Message - > From: Anders Hammar > To: Maven Developers List > Cc: > Sent: Friday, December 7, 2012 7:25 AM > Subject: Re: [VOTE] Maven 3.1.0 > >> I'm interested to help working on adding a metadata

Re: apache/maven-3 at Github

rue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List ; Mark Struberg > > Cc: > Sent: Wednesday, December 5, 2012 10:53 AM > Subject: Re: apache/maven-3 at Github > > 2012/12/5 Mark Struberg : >> But to make this more clear, we wi

Re: apache/maven-3 at Github

But to make this more clear, we will only accept pull changes if they come along with an identical JIRA with the diff. You also must make sure that you are the only one who has changed something in the contribution. It's way to easy to fake author Ids on github... The committer which applies th

Re: Re-spinning 3.1.0

>Downloads from central in the last 12 months: > >Logback: 1,136,846 >Log4J2: 6,748 Do you have the number for all log4j artifacts? log4j2 just got released but is a native successor of log4j1. LieGrue, strub > > From: Jason van Zyl >To: Maven Developers L

Re: Re-spinning 3.1.0

> How many times does someone really need a different implementation? Sorry Jason, thats bollocks and you know it. > That is the pattern of most forms of > integration because trying to account for many implementations interacting > together have unknown side affects. You are wrong and ri

Re: 3.1.0 decision making

+1 for 3.1.0-m1 LieGrue, strub - Original Message - > From: Hervé BOUTEMY > To: Maven Developers List > Cc: > Sent: Saturday, December 1, 2012 7:03 PM > Subject: Re: 3.1.0 decision making > > Le samedi 1 décembre 2012 18:52:51 Dennis Lundberg a écrit : >> I would -1 any suggestion

Re: 3.1.0 decision making

@Benson >No one, as far as I recall, objected, but perhaps my memory is selective. just for the record: I did cast -1 on the commit and explained my objections ... I obviously don't like it but I wont 'veto' it as those technical questions are simply majority votes. And there are quite some devs

Re: [VOTE] Maven 3.1.0

st ; Mark Struberg > >Sent: Saturday, December 1, 2012 11:20 AM >Subject: Re: [VOTE] Maven 3.1.0 > > >Couldn't we use the shading plugin to not expose the original implementation >(logback, log4k, whatever ..) but a repackaged one to avoid conflicts with >plugins whic

Re: Re-spinning 3.1.0

There is btw out of the box @InjectLogger support for Log4j2 in guice. A few projects are using this already without problems it seems. LieGrue, strub - Original Message - > From: Arnaud Héritier > To: Maven Developers List > Cc: > Sent: Saturday, December 1, 2012 10:42 AM > Subje

Re: Re-spinning 3.1.0

sounds great, have Oliviers branch running locally myself without issues. LieGrue, strub - Original Message - > From: Arnaud Héritier > To: Maven Developers List > Cc: > Sent: Saturday, December 1, 2012 9:17 AM > Subject: Re: Re-spinning 3.1.0 > > Hi Jason, > >   Couldn't we have

Re: [VOTE] Maven 3.1.0

what is complex with say am openjpa enhancer mojo? Still this will break depending what the project configures in it's persistence.xml. Just an idea for now: The safe route might be a plugin-plugin annotatation which tells us 'plugin uses slf4j' in that case it gets exposed, in other cases it do

Re: [VOTE] Maven 3.1.0

to be proved wrong... LieGrue, strub > > From: Jason van Zyl >To: Maven Developers List ; Mark Struberg > >Sent: Friday, November 30, 2012 9:08 PM >Subject: Re: [VOTE] Maven 3.1.0 > > > > >On Nov 30, 2012, at 11:55 AM, Mark Struberg wrote: > >Th

Re: [VOTE] Maven 3.1.0

That's all broken by design as already predicted 2 months ago. Imo the only portable way is to NOT expose slf4j in the Core Realm at all. The other way would be to introduce a plugin-plugin configuration which says logging yes/no. LieGrue, strub - Original Message - > From: Stephen C

  1   2   3   4   5   6   >