+1
> On May 31, 2022, at 7:25 AM, Tamás Cservenák wrote:
>
> Howdy,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12351791
>
> There are still some issues left in JIRA:
> https://issues.apache.org/jira/projects/MINDEXER/
>
> Stagin
+1
> On May 26, 2022, at 6:43 AM, Michael Osipov wrote:
>
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12331357
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/SCM/issues
>
> St
+1
> On May 25, 2022, at 11:41 AM, Slawomir Jaranowski
> wrote:
>
> Hi,
>
> We solved 24 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12349728
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=proje
jakarta.inject working simultaneously
for a co-existence and/or transition. Again Stuart, correct me if I’m wrong.
Jason
> On May 16, 2022, at 1:14 PM, Slawomir Jaranowski
> wrote:
>
> But from other side we can use JSR-330 in Mojo [1]
>
> so we will:
>
> @Parameter( d
+1
> On May 14, 2022, at 6:26 AM, Tamás Cservenák wrote:
>
> +1
>
> On Sun, May 8, 2022, 11:29 Hervé BOUTEMY wrote:
>
>> Hi,
>>
>> We solved 14 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350929&styleName=Text&projectId=12323721
>>
>> Staging repo:
>> htt
+1
jvz
> On May 4, 2022, at 8:39 AM, Guillaume Nodet wrote:
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/0.8.0/
>
> The changelog is available at
>
> https://github.com/apache/maven-mvnd/blob/master/CHANGELOG.md#080-2022-05-04
>
> I've fixed a
specific feedback?
Jason
> On May 4, 2022, at 8:39 AM, Guillaume Nodet wrote:
>
> I've staged a candidate release at
> https://dist.apache.org/repos/dist/dev/maven/mvnd/0.8.0/
>
> The changelog is available at
>
> https://github.com/apache/maven-mvnd/blob/maste
+1
jvz
> On Mar 21, 2022, at 3:27 AM, Hervé BOUTEMY wrote:
>
> +1
>
> Reproducible Builds ok: reference done with JDK 8 on *nix
>
> notice that I had to rebuild from Git because it failed from source release
> zip:
>
> [INFO] Running org.apache.maven.it.VerifierTest
> [ERROR] Tests run: 6,
---
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
t; To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
cripts by default
>
>
> Enjoy,
>
> -The Apache Maven team
>
>
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apach
+1
jvz
> On Dec 13, 2021, at 4:09 PM, Hervé BOUTEMY wrote:
>
> Hi,
>
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721&version=12350068&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1679/
> https:/
Both of those (#622 and #630) look like important changes to merge.
Getting the caching extension used and those interfaces exercised by the
community is only a good thing.
Given there’s only one extension in that area right now, even if the extension
point interfaces had to change to accommod
their first or add different tests. We’ll get there.
Let’s just get it into the hands of users.
jvz
> On Dec 12, 2021, at 1:05 PM, Robert Scholte wrote:
>
> Jason,
>
> my point is that i DID write integration tests as part of the donation to
> better understand the code, im
Clearly no one here disagrees with the goal of having robust testing for
software that is made available to users.
As to the timing of that testing being complete for the wrapper, to the
satisfaction of those objecting to a release, I will argue.
Do we wait four years for adequate testing? I’m
+1
jvz
> On Dec 10, 2021, at 4:30 AM, Guillaume Nodet wrote:
>
> I've refactored the build to be a single-module build.
> I agree that maven-caching is not the most descriptive, I'd be pleased with
> * maven-build-cache-extension*
>
> Guillaume
>
---
Everything builds and it generates the wrapper for a project in a way will be
familiar to existing users. The switch for current users should, hopefully, be
painless and transparent.
Nice work Robert and Hervé. I put a notice on the GitHub page for the Takari
version about the impending release
velopment/guide-testing-releases.html
>
> Vote open until 2021-11-19T18:00Z
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mai
without *any* special switches, config, or
> POM.xml tweaking,
> and *all* maven-*-plugins will perform the necessary steps on their own (e.
> g. compiler
> runs multiple times as the compiler plugins knows this is needed when it sees
> /java/nu
...SKIPPED -
> Maven version 3.7.0-SNAPSHOT not in range [3.5.3-SNAPSHOT,3.5.4-SNAPSHOT]
>
>
> which are 62 IT's in total
>
> Should we keep them or should we remove them?
>
> Several of them are Maven 2 related...?
>
> Kind regards
> Karl Heinz Marbaise
>
> [1]: https://issues.apache.org/jira/browse/MNG-6744
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
>> DefaultModelBuilder.
>> They both implement the ModelBuilder interface, but the one that
>> extensions like to overwrite is the implementation of DefaultModelBuilder.
>> So I'd prefer to stick to "core" as proposed my Stuart.
>>
>> thanks for the confirma
this change, and I’m able to run polyglot
example projects again, so I assume the Tycho POM-less are happy again as well
but hopefully someone can verify.
Jason
> On Oct 18, 2019, at 2:04 PM, Robert Scholte wrote:
>
> Hi,
>
> with the help from Stuart McCulloch we've been ab
Links look better now. Thanks!
—jason
On July 28, 2018 at 2:05:02 AM, Karl Heinz Marbaise (khmarba...@gmx.de) wrote:
Hi Jason,
On 27/07/18 23:41, Jason Dillon wrote:
> On this page:
>
> https://maven.apache.org/mailing-lists.html
>
> It looks like the sub/unsub/
up showing a “Page Not Found”.
The Archive links look okay.
The Other Archives are mostly okay, but the nabble.com links are broken too?
* * *
Is anyone aware of this and/or is there a way to fix these so that community
members can sub/unsub to lists?
—jason
Yes please, thank you :-]
—jason
On May 24, 2017 at 2:38:24 PM, Igor Fedorenko (i...@ifedorenko.com) wrote:
I'd like to ask for somebody to second my change described in
[MNG-6233]. The change cleans up mixture of jsr330 and plexus
annotations used in maven-resolver-provider, leaving
still be using older versions of the shell, I’d
like to ask them to test the latest SNAPSHOTS and report back any issues.
Cheers,
—jason
> -Original Message-
> From: Michael Osipov
>
> Am 2017-03-16 um 13:39 schrieb Stephen Connolly:
> > https://reference.apache.org/committer/node-hosting
> >
> > So if somebody really feels that we need exotic node types... and is
> > willing to provide such a node and hook it up...
>
> T
Cool info.
But I seriously thought this was a spam message the first 3 times I read it.
Subject exotic - check
link - check
1 sentence body - check
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Thursday, March 16, 2017 08:39
> To: Maven
Working on a plugin right now and it needs to work in 3.0 as well as 3.3.
Scratching my head on can we use slf4j in 3.0 or is there a backwards
compatibility logic to put in.
-Jason
. I’m not really concerned with one person who seems not to
understand this. My concern is about destroying the trust we’ve built up over
the years in one fell swoop.
> On Nov 17, 2016, at 12:10 AM, Stephen Connolly
> wrote:
>
> Jason, your hyperbole has slipped again. There is no
15, 2016, at 3:42 PM, Christian Schulte wrote:
>
> Am 11/15/16 um 23:41 schrieb Jason van Zyl:
>>
>> You obviously don’t work with anyone who has a system with any number of
>> users. No one has said the system cannot change, but you repeatedly keep
>> changin
> On Nov 15, 2016, at 12:31 PM, Christian Schulte wrote:
>
> Am 11/15/16 um 17:17 schrieb Jason van Zyl:
>> -1
>>
>> No one has likely to have read the information
>
> The reporter of the issue clearly has ;-)
>
>> and you’re reasoning is illogical.
--
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
--
Jason van
Danke
> On Nov 10, 2016, at 2:07 PM, Michael Osipov wrote:
>
> Am 2016-11-09 um 16:56 schrieb Jason van Zyl:
>> Brevity, compactness and if you look at any modern codebase that’s a the
>> practice. It’s what you should have done in the first place.
>
> Done.
>
&
Brevity, compactness and if you look at any modern codebase that’s a the
practice. It’s what you should have done in the first place.
> On Nov 8, 2016, at 10:35 AM, Michael Osipov wrote:
>
> Am 2016-11-08 um 17:04 schrieb Jason van Zyl:
>> Please use a static import if you c
Please use a static import if you can.
> On Nov 7, 2016, at 1:08 PM, micha...@apache.org wrote:
>
> [MRESOLVER-4] Use java.util.Objects#requireNonNull to intercept invalid input
>
>
> Project: http://git-wip-us.apache.org/repos/asf/maven-resolver/repo
> Commit: http://git-wip-us.apache.org/repo
Okay, good luck. Let me know if you change your mind and need improvements to
gossip.
Cheers,
—jason
On October 22, 2016 at 10:20:08 AM, Hervé BOUTEMY (herve.bout...@free.fr) wrote:
thanks for sharing what you had, this really helped me work on the topic,
testing and learning misc
-cases for folks fiddling with
the logging impl/config so much, vs just using the tool as it comes.
If you folks want to drop it and hack in something else, it won’t hurt my
feelings. If you need help to adjust Gossip to do something I can probably
help.
—jason
So your approach was to fork some code, instead of trying to fix Gossip? I
haven’t been paying much attention just trying to understand why you would fork
instead of working with Jason Dillon to get that added? Did he not respond or
you couldn’t make a PR?
Jason
> On Oct 17, 2016, at 1:11
I believe we definitely need RCs in this case.
> On Oct 9, 2016, at 1:17 PM, Michael Osipov wrote:
>
> Am 2016-10-09 um 14:10 schrieb Jason van Zyl:
>> The preparation of detailed released notes to be reviewed. The last
>> release was almost a year ago, and an enormous
-
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
Thanks,
Jason
--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.c
l on these 3 choices?
>
> Regards,
>
> Hervé
>
> Le mercredi 3 août 2016 16:04:36 Jason van Zyl a écrit :
>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver
>> for the package names is more consistent with the other naming in th
lte wrote:
>
> Mercury2? ... Caduceus (Hypothetical moon of Mercury)
>
> On Fri, 05 Aug 2016 15:34:04 +0200, Tamás Cservenák
> wrote:
>
>> ... Mercury
>>
>> On Thu, Aug 4, 2016 at 11:09 PM Jason van Zyl wrote:
>>
>>> When in doubt I h
When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and Tycho.
None of them very useful for people to understand what they actually do. I
think I’m done with catchy names. I’m old.
> On Aug 4, 2016, at 4:33 PM, Christian Schulte wrote:
>
> Am 08/04/16 um 22:22 schr
; over the network (hostname and port) using a protocol. No URL involved.
> No filesystem involved. Just thoughts.
>
> Regards,
> --
> Christian
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.
.org
>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>> -
&g
it happened because if they trace through Aether code everyone who does
seems it didn’t happen there. That aspect is a mess. This should be consistent
for plugins and the application resolution but it currently is not.
> On Jul 29, 2016, at 8:50 PM, Jason van Zyl wrote:
>
> The mode
see the full stack trace of the...
>
> Cause the package phase did add artifacts to the projects...
>
> So the question comes up: How can this be prevented...
>
> The following works:
>
> mvn package..deploy
>
>
> Furthermore I'm thinking about doing things
e I'm thinking about doing things like this:
>
> mvn [test]
>
> To run only the life cycle phase test ...without the preliminary phases...
>
> WDYT ?
>
> Kind regards
&g
PM, Christian Schulte wrote:
>
> Am 28.07.2016 um 19:18 schrieb Jason van Zyl:
>> I’m a vehement -1 to changing the artifactIds or structure without a plan.
>
> +1
>
> If something does not need to be renamed, then don't rename it. If something
> needs to be renamed, don
Christian Schulte:
>> Am 07/28/16 um 17:37 schrieb Andreas Sewe:
>>> Jason van Zyl wrote:
>>>> It’s all Maven specific, it’s always been Maven specific and that’s
>>>> unlikely to change after how many years? Even if it can employ
>>>> different strategi
are wrong. Tycho uses p2 to resolve artifacts.
> Removing "Maven" and just call it Artifact Resolver API (ara) solves this.
> It's the API for resolving artifacts in Maven.
> But, it might just be me interpreting this wrong.
>
Artifact Resolution API is fine too.
>
idea?
>>>> Is there a preference in the community?
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> ---
g else and get a lot more control over logging with your
favorite backend.
—jason
“good”, “bad”, “warning”, etc concepts.
* * *
In short, I would not recommend jumping directly into making ansi coloring of
output part of the api proper and exposing to the community for extension at
this time w/o further consideration and planning for how it would impact the
platform generally.
—jason
On June 15, 2016 at 12:07:32 AM, Christian Schulte (c...@schulte.it) wrote:
Am 06/15/16 um 00:17 schrieb Jason Dillon:
> Making the colors configurable seems like a lot of overhead for what is
> otherwise fairly simple.
>
> I’d recommend leaving the colors asis for now, get thi
release of mvn + ansi color support.
—jason
On June 14, 2016 at 3:04:20 PM, Olivier Lamy (ol...@apache.org) wrote:
On 15 June 2016 at 05:25, wrote:
> Repository: maven
> Updated Branches:
> refs/heads/master ecdb0bc2b -> e7a783db1
>
>
> [MNG-3507] keep green
(very very very
old preference I’ve had for a long time so much I forgot it was my preference).
We can certainly make things explicitly yellow though if that is preferred over
simply bold.
—jason
pluggable aspect, and if you were
using logbook backend it would be meaningless and potentially confusing.
—jason
On June 2, 2016 at 8:37:18 PM, Manfred Moser (manf...@simpligility.com) wrote:
If we plan to switch it to on be default at a later stage we could
automatically disable it in batch mode
say I’ve done any exhaustive testing
of this.
To be able to tell if System.out is an ANSI-aware terminal it may need a bit
more love ala jline or more helpers in jansi to do more properly?
—jason
gt;>>>>>>>>
>>>>>>>>>> very simple via JConsole and running the different versions...
>>>>>>>>>>
>>>>>>>>>> I have summarized this here:
>>>>>>>>
immediately because it looked like
>> SLF4J 1.7.22 was on its way. Sorry for the inconvenience caused.
>>
>> Regards,
>
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h
This is what I wrote for people trying to contribute to core:
http://takari.io/2014/06/01/contributing-to-maven-core.html
And what I use to smoke test contributed PRs:
https://gist.github.com/jvanzyl/16da25976f8ad27293fa
> On May 19, 2016, at 3:00 PM, Karl Heinz Marbaise wrote:
>
>
Uwe Barthel wrote:
>
> Hi Jason,
>
> I tried to reproduce the IT failure at master.
>
> Fetched https://github.com/apache/maven - master - last commit:
> 4b35102f0e3302e15a80d3ddb756463601b9217a
> Fetched https://github.com/apache/maven-integration-testin
number of ITs
that are failing. I’d really like to not have to git bisect back to a working
state so if you’ve been making changes to core please run the ITs locally and
double check what you’ve done.
Thanks,
Jason
--
Jason van Zyl
Founder
> 6.6.1
>
>
>
>
>
>
>
>
> com.h3xstream.findsecbugs
>
>
> findsecbugs-plugin
>
>
> 1.4.5
>
>
>
>
>
>
>
>
sworlds.launcher.Launcher
> TERM_PROGRAM_VERSION=303.2
> PWD=/Users/do/Downloads/maven-MNG-6003-196234a
> MAVEN_CMD_LINE_ARGS= help:system
> TERM_PROGRAM=Apple_Terminal
> SHLVL=1
> __CF_USER_TEXT_ENCODING=0x1F5:0:3
> com.apple.java.jvmTask=CommandLine
> DISPLAY=/tmp/launch-iwR
ml.
>>>
>>> The process for retiring a plugin is described here:
>>> https://maven.apache.org/developers/retirement-plan-plugins.html
>>>
>>> The vote is open for 72 hours.
>>>
>>> [ ] +1 Yes, it's about time
>>> [ ] -1
--
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>
> -
If it were something structured I’d probably start with GMaven. I can write
Java in an IDE faster than ad-hoc Groovy so I really only thought of the
one-off cases and custom logic vis-a-vis the in-line plugins.
> On May 8, 2016, at 5:49 PM, Francois-Xavier Bonnet
> wrote:
>
> R
verywhere - including ideS - is a must and why
> polyglot maven didnt get as must market as it should IMHO.
>
> Also being able to order in the pom itself execution by reference would
> solve a lot of headaches.
> Le 8 mai 2016 17:04, "Jason van Zyl" a écrit :
>
>>
ven-plugin
>
> Regards,
> Francois-Xavier Bonnet
Thanks,
Jason
--
Jason van Zyl
Founder, Takari and Ap
broke how Maven works in CI servers that would not be nice.
> On Apr 17, 2016, at 8:37 AM, Michael Osipov wrote:
>
> Am 2016-04-17 um 17:24 schrieb Jason van Zyl:
>> So will the proposed behavior be I upgrade Maven, I don’t have JAVA_HOME set
>> manually and Maven will e
> [2]
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=196234a95f7d5ade0b0b905308c2083e856cd121
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.
Jason, if you have a built version, do you mind adding it as a download to
the release files?
I can make a binary of this, though I do plan on fixing it up so that folks can
build it in the near future.
Build up here for the moment:
https://www.dropbox.com/sh/yvt1g43r2pr2scj
icial jline2 stuff can be done.
Jason, if you have a built version, do you mind adding it as a download to
the release files?
I can make a binary of this, though I do plan on fixing it up so that folks can
build it in the near future.
Do you have interest in supporting further or prefer not to
On March 3, 2016 at 5:42:56 AM, Tamás Cservenák (ta...@cservenak.net) wrote:
Maven Shell?
https://github.com/jdillon/mvnsh
Does anyone actually use this?
—jason
my environment? I am on OSX and
> use java 1.7.0_79-b15 to run the tests.
>
> --
> Regards,
> Igor
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: de
;>> version
>>>> false
>>>>
>>>>
>>>>
>>>> {code}
>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (
o +1 for removing that variable completely in 3.4 or whatever version is
> appropriate for such a change.
>
> Regards,
> --
> Christian
>
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
kMCmd
>> +set "MVN_HOME=%MVN_HOME:~0,-1%"
>> goto stripMHome
>>
>> :checkMCmd
>> -if exist "%M2_HOME%\bin\mvn.cmd" goto init
>> +if ex
gt;>
>>>>> Any objection?
>>>>> I still didn't create corresponding Jira issue, but will do if
>>> popsitive
>>>>> feedback
>>>>>
>>>>> Regards,
>>>>>
>
nsion
> 3. in desired project just add .mvn/extensions.xml with
>
>
>
>
> org.apache.maven.logging
> maven-logback-logging
> 1.0-SNAPSHOT
>
>
>
>
> Please note: this is all "draft", just from my bed... :)
>
>
>
> On Sat, Jan 9, 2016 at 3:
edit extensions.xml
>> for you), and later maybe enhance it with some other goals too (to manage
>> complete extensions.xml for example?)...
>>
>> ===
>>
>> Also, as we have people leaning for log4j2 or logback backends, I'd like
>> to stir
e once. I think either way is doable and
Ceki has agreed to review the code. If Igor will let me I’ll try the suggested
techniques with his code.
> Den 8 jan 2016 13:38 skrev "Jason van Zyl" :
>
>> Ralph,
>>
>> The simple fact of the matter is that Log4J2 appears
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,
lph Goers wrote:
>
> He claims that Log4j 2 isn’t popular enough. The real reason, as you
> probably know, is that Jason seriously dislikes me, although he would never
> actually say that as his reason.
>
> Ralph
>
>> On Jan 7, 2016, at 10:56 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 downloaded on demand. I think for Maven
>&g
ivate by moving a jar
> ?
>
> On Thu, Jan 7, 2016 at 2:51 PM, Jason van Zyl wrote:
>
>> And I liked this extension and wanted it! I only thought it inappropriate
>> because the deps were not there by default in the core, and that we said
>> we’d discuss it. Even t
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 differen
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:
>&g
> 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" thi
they
> do! So the bar for committer rights is much (much) lower than at Apache. I
> don't think the above comparison is fair toward log4j2.
>
> Cheers,
> Paul
>
> On Wed, Jan 6, 2016 at 4:09 PM, Jason van Zyl wrote:
>
>>
>>> On Jan 6, 2016, at
> 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
7;).inE.count()
==>62389
gremlin> g.V('vc', 'org.apache.logging.log4j:log4j-core').inE.count()
==>3134
These are incoming edges across all versions of said coordinate.
> On Jan 6, 2016, at 11:15 AM, Jason van Zyl wrote:
>
> As we said p
motivated much here in
these discussions but I’m vehemently opposed to integrating Log4J2.
> On Jan 6, 2016, at 7:55 AM, Arnaud Héritier wrote:
>
> thanks for this valuable comment Jason :(
>
> On Wed, Jan 6, 2016 at 1:46 PM, Jason van Zyl wrote:
>
>> -1
>>
tion, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>&
It’s safe to nuke it.
> On Dec 28, 2015, at 4:16 PM, Michael Osipov wrote:
>
> Hi folks,
>
> is it safe to delete that MANIFEST.MF file [1]? It has been hand-crafted by
> Jason back in 2006-12-07 for OSGi usage but it terribly outdated.
>
> I have no experience with O
1 - 100 of 6853 matches
Mail list logo
