[
https://issues.apache.org/jira/browse/LOG4J2-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133112#comment-14133112
]
Hassan Kalaldeh commented on LOG4J2-820:
OK I think I got it, I just saw your comm
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133101#comment-14133101
]
Remko Popma edited comment on LOG4J2-819 at 9/14/14 6:14 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133102#comment-14133102
]
Hassan Kalaldeh commented on LOG4J2-820:
I understand your point for the filePatte
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133101#comment-14133101
]
Remko Popma commented on LOG4J2-819:
Clock latency and granularity varies wildly acros
[
https://issues.apache.org/jira/browse/LOG4J2-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-825.
Resolution: Implemented
Fix Version/s: 2.1
Implemented in latest master. Will close after som
Sounds good to me.
On 13 September 2014 23:53, Gary Gregory wrote:
> Which ever way we go on this, let's get 2.1 out the door first. We have
> some nice new functionality for 2.1 already (JUL, IO streams). Once we fix
> our clock threading issue, I say we clean thing up and prepare 2.1.
>
> Gary
Which ever way we go on this, let's get 2.1 out the door first. We have
some nice new functionality for 2.1 already (JUL, IO streams). Once we fix
our clock threading issue, I say we clean thing up and prepare 2.1.
Gary
On Sat, Sep 13, 2014 at 4:45 PM, Matt Sicker wrote:
> They're the most flex
If you have time to check this for 2.1 that would be nice.
Gary
On Thu, Sep 11, 2014 at 3:03 PM, Matt Sicker wrote:
> Whoops, sort of forgot. It would be safe to upgrade EclipseLink. I'm
> assuming Mongo would work, but I wouldn't do that blindly. I don't know
> enough about lightcouch to know
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133078#comment-14133078
]
Gary Gregory edited comment on LOG4J2-819 at 9/14/14 4:50 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133078#comment-14133078
]
Gary Gregory edited comment on LOG4J2-819 at 9/14/14 4:47 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133078#comment-14133078
]
Gary Gregory commented on LOG4J2-819:
-
To answer my own question it looks like {{nanoT
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133074#comment-14133074
]
Gary Gregory commented on LOG4J2-819:
-
This might be a silly comment but why is there
We might not be that far apart, at my work, we care very much about IBM,
AIX, the i/Series and z/Series. I just do not want to linger on an old
platform. We just need to strike a balance. Now that Java 8 is out, I see a
much stronger desire from developers to use it than I did when Java 7 came
out.
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133068#comment-14133068
]
Remko Popma edited comment on LOG4J2-819 at 9/14/14 3:49 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133068#comment-14133068
]
Remko Popma commented on LOG4J2-819:
Yes, you are both correct.
Gary's suggestion to
Oops. Sorry. The End of Service date for Java 6 on everything but z/OS (IBM
mainframes) is September 2017. That would include AIX. Java 7 EOS on AIX is
Sept 2019, which lines up with Oracle’s end of Premium support for Java 7.
I agree with keeping it simple. We will provide support until Oracle
I think you are going to need something more concrete to convince me that
emulating the OSGi Lifecycle is necessary.
Ralph
On Sep 13, 2014, at 7:07 PM, Matt Sicker wrote:
> Having at least more than one boolean state will help with concurrency issues
> when starting/stopping a thing. Using th
I really don’t think there are that many features where we would need JDK
specific implementations of something.
The problem is, your definition of “dead” and mine are different. I know very
well that there are many users still on JDK 6. Also, IBM [1] still has not
announced an end of service
Having at least more than one boolean state will help with concurrency
issues when starting/stopping a thing. Using the OSGi life cycle means that
all platforms can have sufficient life cycle support for things that need
to be managed as such. Spring may have only those three methods as Ralph
point
I think we should keep it simple. If some version of Java is dead, past
public update EOLs, then it's OK by me to switch _master development_ to a
supported Java version. To me, this means that all master development
should be on Java 7 now.
Perso, I do not want to support multiple Java versions i
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133051#comment-14133051
]
Gary Gregory commented on LOG4J2-819:
-
It seems clear that no final statics = no probl
On 13 September 2014 19:03, Ralph Goers wrote:
> For example, we could plan to upgrade our minimum version whenever Premier
> support ends (Java 6 until Dec 2015, Java 7 until July 2019, etc).
>
Good idea.
> I also wouldn’t want to jump from version 2.x to 3.x just because we
> changed the mini
Well... this is an interesting topic.
At work and here at Log4j, and other personal projects I've introduced life
cycle classes of different types.
I've specifically not reused other frameworks for a simple reason, I was
not going to pretend to co-exist and jump through hoops to follow the
proper
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133045#comment-14133045
]
Ralph Goers commented on LOG4J2-819:
OK. But if we remove the static variables in thos
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133042#comment-14133042
]
Remko Popma commented on LOG4J2-819:
Tomcat loads those two classes because ClockFacto
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133041#comment-14133041
]
Ralph Goers commented on LOG4J2-819:
I admit I don't completely understand why Tomcat
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133039#comment-14133039
]
Remko Popma commented on LOG4J2-819:
Ralph, since LOG4J2-628 the Log4JLogEvent Clock i
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133036#comment-14133036
]
Remko Popma commented on LOG4J2-819:
Gary, I named the class ~Factory to convey the in
Log4j 1.x stuck with JDK 1.2 for many years for a reason.
Although public support for Java 6 ended in 2013, Oracle’s site [1] says
Premier support is available until Dec 2015 and extended support is available
until Dec 2018. Java 7’s extended support runs through 2022. So just because
the “fr
Matt Sicker created LOG4J2-825:
--
Summary: Add basic validation annotations for plugin builders
Key: LOG4J2-825
URL: https://issues.apache.org/jira/browse/LOG4J2-825
Project: Log4j 2
Issue Type:
[
https://issues.apache.org/jira/browse/LOG4J2-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-653:
---
Component/s: (was: Core)
Plugins
> Add plugin builder classes as alternative to f
Are you planning on implementing something for each of those phases? Spring’s
Lifecycle contains start(), stop(), and isRunning(). JSF and Swing and I am
sure many other things also have life cycles. We should implement the states
we need because we need them, not to match some other technolog
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133025#comment-14133025
]
Ralph Goers commented on LOG4J2-819:
I think you worry too much about names ;-) I don
So would we like to do this for something like version 2.2, 2.3, or make a
3.0 version? I'm not really sure on how other projects tend to handle these
sorts of compatibility changes.
On 13 September 2014 16:16, Gary Gregory wrote:
> FYI
>
> Original message
> From: Stephen Conn
FYI
Original message From: Stephen Connolly
Date:09/13/2014 07:56
(GMT-05:00) To: Maven Developers List
Subject: Java 7 EOS now set for April 2015
http://mail.openjdk.java.net/pipermail/jdk7u-dev/2014-April/008910.html
Wondering if we should start thinking about upping to
Going back to this programmatic configuration topic, I agree with Ralph's
idea of using Configuration/Node. Thus, a programmatic API would likely
work via that idea so as not to cause problems with this sort of annotation.
On 9 July 2014 14:34, Ralph Goers wrote:
> Not necessarily Groovy specifi
They're the most flexible. Quick overview of the life cycle in OSGi:
installed -> resolved -> (starting) -> active -> (stopping) resolved ->
uninstalled
Installed is the initial state. Resolved is when all its dependencies have
been fulfilled. During the starting state, if there is an error, then
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132934#comment-14132934
]
Gary Gregory commented on LOG4J2-819:
-
It also now feels that {{ClockFactory}} class i
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132795#comment-14132795
]
Ralph Goers commented on LOG4J2-819:
I think the Clock instance needs to be stored in
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132736#comment-14132736
]
Gary Gregory commented on LOG4J2-819:
-
It seems to be we can solve this in several way
[
https://issues.apache.org/jira/browse/LOG4J2-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132571#comment-14132571
]
Remko Popma edited comment on LOG4J2-819 at 9/13/14 8:09 AM:
-
41 matches
Mail list logo
