Alright, feel free to continue on with the release. I have some failing
unit tests in this branch that seem to be related to hacky tests that try
to avoid cleanups rather than the implementation itself.
On 26 August 2017 at 14:31, Ralph Goers wrote:
> I moved the test classes that were dependent
I have restarted the release build.
Ralph
> On Aug 26, 2017, at 12:29 PM, Matt Sicker wrote:
>
> Should I update the @since to 2.9.1 then, or is the release on hold for
> now? I've got the code working and docs are pretty updated at this point.
>
> On 26 August 2017 at 14:14, Gary Gregory wro
I moved the test classes that were dependent on log4j-server to that project.
Ralph
> On Aug 26, 2017, at 11:27 AM, Ralph Goers wrote:
>
> Scratch that. It seems Log4j now has a dependency on log4j-server? That must
> be released before a release build can be run. Why does the main project hav
Should I update the @since to 2.9.1 then, or is the release on hold for
now? I've got the code working and docs are pretty updated at this point.
On 26 August 2017 at 14:14, Gary Gregory wrote:
> IMO, the simplest solution is to bring log4j-server back into the main
> repo.
>
> Gary
>
> On Aug 2
IMO, the simplest solution is to bring log4j-server back into the main repo.
Gary
On Aug 26, 2017 12:27, "Ralph Goers" wrote:
> Scratch that. It seems Log4j now has a dependency on log4j-server? That
> must be released before a release build can be run. Why does the main
> project have a depend
Scratch that. It seems Log4j now has a dependency on log4j-server? That must be
released before a release build can be run. Why does the main project have a
dependency on that?
Ralph
> On Aug 26, 2017, at 11:21 AM, Ralph Goers wrote:
>
>
> I am just about to start the release build of 2.9 so
I am just about to start the release build of 2.9 so please hold off on
committing.
Ralph
> On Aug 26, 2017, at 10:54 AM, Matt Sicker wrote:
>
> I've finally got some time this weekend and am working on merging this
> today. Strangely enough, my old branch merged with no git merge conflicts,
I've finally got some time this weekend and am working on merging this
today. Strangely enough, my old branch merged with no git merge conflicts,
so it shouldn't be too hard to integrate at this point. I'll be handling
documentation updates along with trying to copy over all the old property
names
I hope you fell better soon Matt.
Gary
On Wed, Aug 23, 2017 at 12:35 PM, Matt Sicker wrote:
> May not get a chance to work on this tonight. Haven't been feeling too well
> today or yesterday. :(
>
> On 21 August 2017 at 18:38, Matt Sicker wrote:
>
> > I won't be free until Wednesday night at t
May not get a chance to work on this tonight. Haven't been feeling too well
today or yesterday. :(
On 21 August 2017 at 18:38, Matt Sicker wrote:
> I won't be free until Wednesday night at the earliest. If Ralph wants to
> start the release before that, I'm alright with that.
>
> On 21 August 20
I won't be free until Wednesday night at the earliest. If Ralph wants to
start the release before that, I'm alright with that.
On 21 August 2017 at 17:43, Gary Gregory wrote:
> Sweet. I've been going through the back log and picking some low-hanging
> fruit as you may have noticed. Maybe others
Sweet. I've been going through the back log and picking some low-hanging
fruit as you may have noticed. Maybe others could do the same.
Gary
On Mon, Aug 21, 2017 at 4:31 PM, Ralph Goers
wrote:
> I plan on starting the 2.9 release any day…
>
> Ralph
>
> > On Aug 21, 2017, at 3:25 PM, Gary Gregor
I plan on starting the 2.9 release any day…
Ralph
> On Aug 21, 2017, at 3:25 PM, Gary Gregory wrote:
>
> On Thu, Jul 20, 2017 at 9:05 PM, Gary Gregory
> wrote:
>
>> On Thu, Jul 20, 2017 at 7:19 PM, Matt Sicker wrote:
>>
>>> I haven't been able to get to this so far this week. Been finishing
On Thu, Jul 20, 2017 at 9:05 PM, Gary Gregory
wrote:
> On Thu, Jul 20, 2017 at 7:19 PM, Matt Sicker wrote:
>
>> I haven't been able to get to this so far this week. Been finishing up a
>> project for work. I should hopefully have enough time to merge this
>> tomorrow though.
>>
>
> Thank you for
On Thu, Jul 20, 2017 at 7:19 PM, Matt Sicker wrote:
> I haven't been able to get to this so far this week. Been finishing up a
> project for work. I should hopefully have enough time to merge this
> tomorrow though.
>
Thank you for the update Matt.
Gary
>
> On 16 July 2017 at 14:36, Gary Greg
I haven't been able to get to this so far this week. Been finishing up a
project for work. I should hopefully have enough time to merge this
tomorrow though.
On 16 July 2017 at 14:36, Gary Gregory wrote:
> On Sun, Jul 16, 2017 at 12:29 PM, Matt Sicker wrote:
>
> > I don't think I'll have time t
On Sun, Jul 16, 2017 at 12:29 PM, Matt Sicker wrote:
> I don't think I'll have time to manage the merge conflicts today, though I
> can shoot for tomorrow.
>
That's great. I just wanted to check that it was still on your near term
to-do list.
Gary
>
> On 16 July 2017 at 14:14, Gary Gregory w
I don't think I'll have time to manage the merge conflicts today, though I
can shoot for tomorrow.
On 16 July 2017 at 14:14, Gary Gregory wrote:
> HI Matt,
>
> Do you still plan to do this over this weekend?
>
> Thank you,
> Gary
>
> On Sun, Jul 16, 2017 at 10:02 AM, Matt Sicker wrote:
>
> > I
HI Matt,
Do you still plan to do this over this weekend?
Thank you,
Gary
On Sun, Jul 16, 2017 at 10:02 AM, Matt Sicker wrote:
> I found the issues:
>
> https://issues.apache.org/jira/browse/LOG4J2-1431 (for the system
> properties normalization)
> https://issues.apache.org/jira/browse/LOG4J2-1
I found the issues:
https://issues.apache.org/jira/browse/LOG4J2-1431 (for the system
properties normalization)
https://issues.apache.org/jira/browse/LOG4J2-1809 (for the supporting API
addition to log4j-api)
On 14 July 2017 at 15:52, Gary Gregory wrote:
> On Fri, Jul 14, 2017 at 1:49 PM, Matt
On Fri, Jul 14, 2017 at 1:49 PM, Matt Sicker wrote:
> The old names are all translated to normalized names via some magical
> regular expressions from what I recall. I should have some time to work on
> Log4j stuff this weekend, so I'll try to get that merged as well.
>
Thank you sir.
Gary
>
On Fri, Jul 14, 2017 at 1:48 PM, Matt Sicker wrote:
> Said branch continues to support the alternate naming schemes as fallbacks,
> but it prioritizes the log4j2.* naming scheme.
>
Please. Please. Please. I do not need to track this kind of noise :-P
G
> On 14 July 2017 at 15:47, Matt Sicker
The old names are all translated to normalized names via some magical
regular expressions from what I recall. I should have some time to work on
Log4j stuff this weekend, so I'll try to get that merged as well.
On 14 July 2017 at 15:48, Gary Gregory wrote:
> Merge it! :-)
>
> Did you bother to k
Merge it! :-)
Did you bother to keep the old names for compat?
G
On Fri, Jul 14, 2017 at 1:47 PM, Matt Sicker wrote:
> I have an open branch that fixes all this. The only remaining work there is
> to clean up merge conflicts and update the documentation to use log4j2.*
> everywhere.
>
> On 14
Said branch continues to support the alternate naming schemes as fallbacks,
but it prioritizes the log4j2.* naming scheme.
On 14 July 2017 at 15:47, Matt Sicker wrote:
> I have an open branch that fixes all this. The only remaining work there
> is to clean up merge conflicts and update the docum
I have an open branch that fixes all this. The only remaining work there is
to clean up merge conflicts and update the documentation to use log4j2.*
everywhere.
On 14 July 2017 at 15:46, Gary Gregory wrote:
> Hi All,
>
> Our sys prop naming is driving me nuts!
>
> Sometimes it's "log4j.foo", som
Hi All,
Our sys prop naming is driving me nuts!
Sometimes it's "log4j.foo", sometimes it's "log4j*2*.bar", sometimes its
"bar". WTF!
Can we just PLEASE bite the bullet and make it all "log4j2." or _something_
We could keep the existing names for compat (TDB).
?
Gary
27 matches
Mail list logo
