+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
@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
+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=12347024=Text
There are still a couple of issues left in JIRA:
+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
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
+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=1230=Text
>
> Staging repo:
>
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:
>
+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=12343925=Text
>
> https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
>
> Staging repo:
>
nterpreted 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 ticket MASSEMBLY-775
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
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.
:33:53, Hervé BOUTEMY wrote:
>>>> disagree
>>>>
>>>> We have the repo configuration which brings a location for every Git
>>>> repository:
>>>> https://maven.apache.org/scm.html
>>>> or https://github.com/apache/maven-sources/
&g
+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=12346480=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1545/
>
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 Struber
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
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
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
> 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
+1
LieGrue,
strub
Am 08.06.2015 um 12:32 schrieb Jason van Zyl ja...@takari.io:
+1
On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921version=12331393
There
+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 stephane.nic...@gmail.com:
+1
S.
On Wed, May 13, 2015 at 8:55 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
Hi,
+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
kristian.rosenv...@gmail.com:
+1
27. apr. 2015 16.01 skrev Stephen Connolly
stephen.alan.conno...@gmail.com:
+1 (you beat me to my vote on core,
indeed, then it passed twice ;)
LieGrue,
strub
Am 27.04.2015 um 17:01 schrieb Jason van Zyl ja...@takari.io:
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 strub...@yahoo.de wrote:
+1
only did simple checks
+1
tested with 2 projects without issues.
LieGrue,
strub
Am 24.04.2015 um 21:08 schrieb Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
We solved 10 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250version=12329009
Staging repo:
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 khmarba...@gmx.de:
Hi,
here is my +1.
need two more binding VOTES...
Kind regards
Karl
+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
, Mark Struberg strub...@yahoo.de
(mailto:strub...@yahoo.de) wrote:
+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
+1 sounds like a plan.
LieGrue,
strub
Am 24.04.2015 um 18:55 schrieb Andreas Gudian andreas.gud...@gmail.com:
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
24.04.2015 um 14:08 schrieb Jason van Zyl ja...@takari.io:
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 strub...@yahoo.de wrote:
maybe I missed some change, but I
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 strub...@yahoo.de wrote:
Re-tested with 3.3.2 and it doesn’t work there neither on my box. 3.0.5 and
3.1.1 work fine
not sure if this has
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
+1
LieGrue,
strb
Am 19.04.2015 um 14:28 schrieb Robert Scholte rfscho...@apache.org:
Hi,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824version=12331215
There are still a couple of issues left in JIRA:
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
works fine over here.
rat fine as well.
+1
LieGrue,
strub
On Thursday, 8 January 2015, 21:21, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi,
We solved 12 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150version=20681
There are still a couple of issues
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
JDK16RTUser();
}
}
public static IRTUser getInstance() { return instance; }
This approach has worked fine for me on multiple occasions.
Jochen
On Thu, Nov 27, 2014 at 9:39 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
Today I had a discussion with Robert about how we can
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 pmoloney...@gmail.com
wrote:
Hi
I had written this rule for the enforcer plugin which actually checks the
label of jdk version in
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
+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
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
+1
really like the new logo (or better any of those owls).
LieGrue,
strub
On Tuesday, 25 November 2014, 12:02, Arnaud Héritier aherit...@gmail.com
wrote:
+1
thx
On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
+1
On 25 November
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 t.cserve...@gmail.com
wrote:
Don’t worry about the details. All the kidnapped people will get what they
deserve ;)
Thanks,
, Hervé Boutemy, Karl-Heinz Marbaise,
Mark Struberg
21:00-22:00 (IST) Stephen Connolly
The current time for me is 8am Friday - with a 30-40 minute drive to the
office before hand ( in order to start work at 9:15ish ).
Any earlier would be harsh for me, but better for any .au folk
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
Op Thu, 01 May 2014 12:15:45 +0200 schreef Mark Struberg
strub...@yahoo.de:
Hi!
Building with Java8 breaks
+1
LieGrue,
strub
On Thursday, 1 May 2014, 10:22, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
+1
2014-05-01 6:48 GMT+02:00 Olivier Lamy ol...@apache.org:
my +1
On 29 April 2014 15:24, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Apache
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,
+1 (binding)
LieGrue,
strub
On Wednesday, 12 March 2014, 22:53, Andreas Gudian andreas.gud...@gmail.com
wrote:
Hi,
long ago since we released the last Surefire version. It's about time we
change that ;-).
We solved 16 issues:
+1
and thanks for pushing this, Dennis!
LieGrue,
strub
On Saturday, 8 March 2014, 23:50, Dennis Lundberg denn...@apache.org wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723
There are still a couple of
+1
LieGrue,
strub
On Thursday, 6 March 2014, 22:19, Hervé BOUTEMY herve.bout...@free.fr wrote:
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEADr2=1434717diff_format=h
Staging repo:
+1
LieGrue,
strub
On Saturday, 8 March 2014, 17:13, Hervé BOUTEMY herve.bout...@free.fr 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=11761version=187
+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 bimargul...@gmail.com
wrote:
Hi,
maven-release is a component that provides the maven-release-manager
and the
+1
LieGrue,
strub
On Thursday, 13 February 2014, 18:42, Andreas Gudian andreas.gud...@gmail.com
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
+1
LieGrue,
strub
On Monday, 3 February 2014, 11:21, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
+1
spot checks to confirm that Robert beat me to my standard tests: pass
On 2 February 2014 11:11, Robert Scholte rfscho...@apache.org wrote:
+1
rat: only
+1
LieGrue,
strub
- Original Message -
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Developers List dev@maven.apache.org
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
+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 aherit...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Saturday, 14 September
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 strub...@yahoo.de wrote:
+1, that's what we also use in DeltaSpike and dozen other projects.
pushChanges=false + localCheckout=true for the win
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 2:20 PM, Mark Struberg strub...@yahoo.de wrote:
+1, that's
succeeded.
LieGrue,
strub
From: Fred Cooke fred.co...@gmail.com
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
Sent: Saturday, 14 September 2013, 21:43
Subject: Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
I believe
the release. I can't keep it on my machine until the vote passes.
On Sep 14, 2013, at 2:20 PM, Mark Struberg strub...@yahoo.de
wrote:
+1, that's what we also use in DeltaSpike and dozen other
projects.
pushChanges=false + localCheckout=true for the win!
LieGrue,
strub
I found that most people use
pushChangesfalse and
localCheckouttrue
Which renders most of the tag stuff useless in GIT.
LieGrue,
strub
- Original Message -
From: Fred Cooke fred.co...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Saturday, 10 August 2013,
+1
LieGrue,
strub
- Original Message -
From: Andreas Gudian andreas.gud...@gmail.com
To: Maven Developers List dev@maven.apache.org
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
+1
did run it the last 2 days on many of my projects without any issues.
LieGrue,
strub
- Original Message -
From: Brian Fox bri...@infinity.nu
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Tuesday, 4 June 2013, 18:13
Subject: Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
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 bmat...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Wednesday, 29 May 2013, 8:47
Subject: Re:
+1
LieGrue,
strub
- Original Message -
From: Robert Scholte rfscho...@apache.org
To: Maven Developers List dev@maven.apache.org
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
+1 (for the vote)
and +1 for waiting the full 72h ;)
LieGrue,
strub
- Original Message -
From: Tamás Cservenák ta...@cservenak.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Thursday, March 7, 2013 3:11 PM
Subject: Re: [VOTE] Release Maven Indexer 5.1.1
T rue,
+1
LieGrue,
strub
- Original Message -
From: Ralph Goers ralph.go...@dslextreme.com
To: Maven Developers List dev@maven.apache.org
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,
+1
works fine. Tested with a few big real world projects.
rat looks fine, signature ok.
LieGrue,
strub
- Original Message -
From: Olivier Lamy ol...@apache.org
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Tuesday, February 19, 2013 4:28 PM
Subject: [VOTE] Apache
+1
LieGrue,
strub
- Original Message -
On Feb 15, 2013 12:40 AM, Olivier Lamy ol...@apache.org
wrote:
ping. one binding +1 is still missing.
Thanks
2013/2/11 Olivier Lamy ol...@apache.org:
+1
2013/2/7 Olivier Lamy ol...@apache.org:
Hi,
I'd like to release Maven
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,
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
+1
LieGrue,
strub
- Original Message -
From: Olivier Lamy ol...@apache.org
To: Maven Developers List dev@maven.apache.org
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
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
+1
LieGrue,
strub
- Original Message -
From: Robert Scholte rfscho...@apache.org
To: Maven Developers List dev@maven.apache.org
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
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
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 -
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
-1.5 anymore with this new version
of maven!
LieGrue,
strub
- Original Message -
From: ceki c...@qos.ch
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Tuesday, December 11, 2012 10:13 PM
Subject: Re: Logback in Maven Core
On 11.12.2012 21:28, Mark Struberg wrote
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
+1
LieGrue,
strub
- Original Message -
From: Kristian Rosenvold kristian.rosenv...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Monday, December 10, 2012 9:32 AM
Subject: Re: Logging
As for options; there is also the option of accepting that the
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 ja...@tesla.io
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
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
sorry, you are right, should have been slf4j-simple, etc.
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Monday, December 10, 2012 11:20 AM
Subject: Re: Logging
Another thing to remember is that logback is a
+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
basically all stuff which integrates maven does *funky logging stuff*...
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Friday, December 7, 2012 7:25 AM
Subject: Re: [VOTE] Maven 3.1.0
I'm interested to help
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
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
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 information.
Dan
On Dec 7, 2012, at 7:32 AM, Mark Struberg strub
.
On Fri, Dec 7, 2012 at 7:57 AM, Mark Struberg strub...@yahoo.de
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 extracted information. They will now just fall on their knees
because
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 bimargul...@gmail.com
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub
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
- Original Message -
From: Kristian Rosenvold kristian.rosenv...@gmail.com
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
Cc:
Sent: Wednesday, December 5, 2012 10:53 AM
Subject: Re: apache/maven-3 at Github
2012/12/5 Mark Struberg strub...@yahoo.de
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 ja...@tesla.io
To: Maven
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
sounds great, have Oliviers branch running locally myself without issues.
LieGrue,
strub
- Original Message -
From: Arnaud Héritier aherit...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Saturday, December 1, 2012 9:17 AM
Subject: 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 aherit...@gmail.com
To: Maven Developers List dev@maven.apache.org
Cc:
Sent:
List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
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
@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
+1 for 3.1.0-m1
LieGrue,
strub
- Original Message -
From: Hervé BOUTEMY herve.bout...@free.fr
To: Maven Developers List dev@maven.apache.org
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
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 right
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
From: Jason van Zyl ja...@tesla.io
To: Maven Developers List dev@maven.apache.org; Mark Struberg
strub...@yahoo.de
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 strub...@yahoo.de wrote:
That's all broken
That's a tricky one.
1st: this is probably already optimized away by the XML reader.
2nd:what about this configuration
url
someurl_handed_over_to_scm
/url
In this case we really must get rid of the whitespaces, otherwise we would
probably create lots of issues with plugins.
LieGrue,
1 - 100 of 599 matches
Mail list logo
