Sorry. Your message could not be delivered to:
internet,PackerCollegiate (The name was not found at the remote site.
Check that the name has been entered correctly.)
I agree with you completely. In fact, the items you have specifically
identified are where I would start. Are there more?
Ralph
On Apr 17, 2014, at 3:21 PM, Bruce Brouwer wrote:
> This discussion about having modules or not having modules keeps coming up
> and I see different opinions here
You can also take a page out of JUnit's playbook. They release an
"experimental" jar in each production release so you test out unfinished
features before they become officially supported.
On Thu, Apr 17, 2014 at 4:41 PM, Gary Gregory wrote:
> On Thu, Apr 17, 2014 at 4:22 PM, Ralph Goers
> wrot
Sorry. Your message could not be delivered to:
internet,PackerCollegiate (The name was not found at the remote site.
Check that the name has been entered correctly.)
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973527#comment-13973527
]
Ralph Goers commented on LOG4J2-607:
With regard to the unit test, I suspect the bug i
This discussion about having modules or not having modules keeps coming up
and I see different opinions here on the log4j team. Generally, the
argument of "please, no more modules" has won. I wanted to present my
perspective to see if I can sway anyone's opinion.
There are plenty of reasons why pr
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973501#comment-13973501
]
Sebastian Audet commented on LOG4J2-607:
Is the mentioned fix in RC1 yet? Or will
On Thu, Apr 17, 2014 at 4:22 PM, Ralph Goers wrote:
> 1. I prefer trunk to be the stable branch. In addition to the 2.0 tag I
> would also cut a branch when 2.0 is finally released.
>
+1, ideally we can cut releases at any time out of trunk for log4j.
Experimentation can be done in branches.
Ga
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973358#comment-13973358
]
Ralph Goers edited comment on LOG4J2-607 at 4/17/14 9:16 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973358#comment-13973358
]
Ralph Goers edited comment on LOG4J2-607 at 4/17/14 8:32 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973358#comment-13973358
]
Ralph Goers commented on LOG4J2-607:
The error with not having the properties at the t
1. I prefer trunk to be the stable branch. In addition to the 2.0 tag I would
also cut a branch when 2.0 is finally released.
2. I could swear we have always generated the OSGi MANIFEST.MF and people said
it wasn’t sufficient, but if they aren’t there then I guess I am wrong.
3. I would like t
Sorry. Your message could not be delivered to:
internet,PackerCollegiate (The name was not found at the remote site.
Check that the name has been entered correctly.)
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973287#comment-13973287
]
Matt Sicker commented on LOG4J2-607:
Looks like this might be a problem related to not
Sorry. Your message could not be delivered to:
internet,PackerCollegiate (The name was not found at the remote site.
Check that the name has been entered correctly.)
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-607:
--
Assignee: Matt Sicker
> log4j2 json files do not support property substitutions
> -
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973269#comment-13973269
]
Matt Sicker edited comment on LOG4J2-607 at 4/17/14 6:47 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973269#comment-13973269
]
Matt Sicker commented on LOG4J2-607:
If you run the CustomConfigurationTest, you'll se
Done. Deleted the two modules after branching to branches/experimental.
On 17 April 2014 12:33, Matt Sicker wrote:
> Thanks, Ralph. I'll move the experimental code to a feature branch.
>
>
> On 17 April 2014 12:27, Paul Benedict wrote:
>
>> If you want to retroactively create a branch, and you
Thanks, Ralph. I'll move the experimental code to a feature branch.
On 17 April 2014 12:27, Paul Benedict wrote:
> If you want to retroactively create a branch, and you're doing Eclipse,
> simply show the project's SVN history; then select create a branch at the
> revision you want to split fro
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973243#comment-13973243
]
Matt Sicker commented on LOG4J2-607:
I tried translating the file to XML and it didn't
If you want to retroactively create a branch, and you're doing Eclipse,
simply show the project's SVN history; then select create a branch at the
revision you want to split from.
On Thu, Apr 17, 2014 at 1:16 PM, Ralph Goers wrote:
> Google “svn move”.
>
> Ralph
>
>
> On Apr 17, 2014, at 10:33 AM
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-607:
---
Environment: Windows 7, JVM 7, Tomcat 7. Also tested using Mac OS X
and JVM 8 (Tomcat 7). (was
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973232#comment-13973232
]
Matt Sicker commented on LOG4J2-607:
Confirmed this issue using the provided log4j2.js
Google “svn move”.
Ralph
On Apr 17, 2014, at 10:33 AM, Matt Sicker wrote:
> I know how to create one, but not retroactively.
>
>
> On 17 April 2014 10:11, Ralph Goers wrote:
> Matt,
>
> Creating a branch in subversion is trivial. A quick google would give you the
> answer to that.
>
>
I've got a few topics to mention.
1. Should we consider making a 2.0 release branch so that trunk can
continue to be the active development branch? That way we can work on new
things while just ironing out the remaining issues for 2.0 GA in the 2.0
branch. Unless you guys prefer a different branch
I know how to create one, but not retroactively.
On 17 April 2014 10:11, Ralph Goers wrote:
> Matt,
>
> Creating a branch in subversion is trivial. A quick google would give you
> the answer to that.
>
> Everyone - Do we already have a sandbox?
>
> Ralph
>
> On Apr 17, 2014, at 6:29 AM, Matt Si
Matt,
Creating a branch in subversion is trivial. A quick google would give you the
answer to that.
Everyone - Do we already have a sandbox?
Ralph
On Apr 17, 2014, at 6:29 AM, Matt Sicker wrote:
> I'm not very good at subversion. I just put it in the trunk. If someone could
> move it to a
[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Audet updated LOG4J2-607:
---
Attachment: log4j2.json
Updated with an example failing JSON file - this works except the fil
Can't both log4j and log4j2 already do this?
In your config, specify fileName="exception.current" and
filePattern="exception.%d{MMdd}". See the example config for
RollingAppender
http://logging.apache.org/log4j/2.x/manual/appenders.html#RollingFileAppender
Regards,
Remko
Sent from my iPh
We could, but to be honest I think it's an extremely rare scenario that the
buffer has so many events that it takes 10 secs to write them all to disk.
Remko
Sent from my iPhone
> On 2014/04/17, at 21:11, Gary Gregory wrote:
>
> >Thread.sleep(HALF_A_SECOND);
>
> Shouldn't this be configurabl
I'm not very good at subversion. I just put it in the trunk. If someone
could move it to a branch, that would be great. Same goes for the
experimental log4j-camel module I started yesterday.
On 17 April 2014 06:49, Gary Gregory wrote:
> Now I am confused. I thought we decided to keep this in a
Now I am confused. I thought we decided to keep this in a branch, I could
be wrong since there have been many back and forths. As of now, this means
it will be released in 2.0. If so, why is it not in the core or api module?
Gary
On Mon, Apr 14, 2014 at 11:45 PM, wrote:
> Author: mattsicker
>
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Brouwer updated LOG4J2-547:
-
Attachment: log4j2-547-builders.patch
> Update LoggerStream API
> ---
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972262#comment-13972262
]
Bruce Brouwer edited comment on LOG4J2-547 at 4/17/14 12:13 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Brouwer updated LOG4J2-547:
-
Attachment: (was: log4j2-547-builders-and-more.patch)
> Update LoggerStream API
> ---
>Thread.sleep(HALF_A_SECOND);
Shouldn't this be configurable?
Gary
On Tue, Apr 15, 2014 at 7:43 PM, Remko Popma wrote:
> The justification is in the comment: we need to give the async logging
> thread time to drain the buffer. Scenario where this is needed: app just
> had a burst of events &
Hi All
Consider following scenario
1) Application is writing to exception.current log file which has time
based rolling policy.
2) Once the rolling interval passed, exception.current should be renamed to
exception.04042014 and new exception.current file should be started.
Is there any configurat
38 matches
Mail list logo
