[
https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054094#comment-15054094
]
Sampath Kumar commented on LOG4J2-1080:
---
I am seeing one more issue with log4j, in
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054090#comment-15054090
]
Sampath Kumar edited comment on LOG4J2-1221 at 12/12/15 6:45 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054090#comment-15054090
]
Sampath Kumar commented on LOG4J2-1221:
---
Nope this is not resolved dropping the eve
I thought Mikael's intention was to make the scala module part of the next
release, while somehow marking it as experimental so that we can still make
changes to the API depending on user feedback.
I don't mind either way, but is there any way to release only the scala module?
Remko
Sent fro
If it builds by default it will be part of the next release, which I am not
certain is assured yet. I think that is why he wants to release it separately.
Ralph
> On Dec 11, 2015, at 8:21 PM, Remko Popma wrote:
>
> I'm assuming that Mikael has verified some use cases on the dev branch, so it
I'm assuming that Mikael has verified some use cases on the dev branch, so it
should be okay to build this module by default. No need for setting up a
separate profile AFAIC.
Sent from my iPhone
> On 2015/12/12, at 9:43, Ralph Goers wrote:
>
> That seems like a bit of a pain. It would be bet
That seems like a bit of a pain. It would be better to specify the classifier
as experimental but you can’t do that in the pom as I recall. I think you have
to specify the project as of type pom and then use the maven helper plugin to
attach it as an artifact with a classifier.
OTOH, the artifa
Should the package name include ".experimental." ?
Gary
On Fri, Dec 11, 2015 at 3:52 PM, Ralph Goers
wrote:
> That is true. In fact, we could add an “experimental" profile to the
> parent pom that has the experimental modules in it. They wouldn’t have to
> build by default.
>
> Ralph
>
> On De
That is true. In fact, we could add an “experimental" profile to the parent
pom that has the experimental modules in it. They wouldn’t have to build by
default.
Ralph
> On Dec 11, 2015, at 2:49 PM, Remko Popma wrote:
>
> Why not just put it on master and _document_ it as "experimental, feedb
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053771#comment-15053771
]
Remko Popma commented on LOG4J2-1221:
-
I am thinking to treat this as a special case
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053702#comment-15053702
]
Remko Popma commented on LOG4J2-1221:
-
[~sakumar], can you provide your full log4j2.x
Why not just put it on master and _document_ it as "experimental, feedback
requested".
That way we simply use our existing release process and instead of 2.5.1, our
next release would be 2.6.
Sent from my iPhone
> On 2015/12/12, at 3:05, Ralph Goers wrote:
>
> With SVN we had a separate br
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053174#comment-15053174
]
Sampath Kumar commented on LOG4J2-1221:
---
I agree that this is a issue with LMAX dis
With SVN we had a separate branch for experimental stuff. In fact, that is
where Log4j 2 originated. I am not sure how to do the same thing with git. If
you have an account at github you could put the project there. But we really
can’t publish anything officially from there.
If you have a pr
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053116#comment-15053116
]
Ralph Goers commented on LOG4J2-1221:
-
Looking at the issue you raised with the disru
This would be in addition. Not everyone needs all the bridges or additional
framework support.
On 11 December 2015 at 11:08, Gary Gregory wrote:
> In my mind, any kind of fat jar would be a new module. Matt?
>
> Gary
>
> On Fri, Dec 11, 2015 at 9:00 AM, Mikael Ståldal > wrote:
>
>> I certainly
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampath Kumar updated LOG4J2-1221:
--
Comment: was deleted
(was: I am OK to move 2.5 but problem is I am not sure how LMAX disruptor
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampath Kumar updated LOG4J2-1221:
--
Comment: was deleted
(was: I am OK to move 2.5 but problem is I am not sure how LMAX disruptor
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053046#comment-15053046
]
Sampath Kumar commented on LOG4J2-1221:
---
I am OK to move 2.5 but problem is I am no
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053045#comment-15053045
]
Sampath Kumar commented on LOG4J2-1221:
---
I am OK to move 2.5 but problem is I am no
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053047#comment-15053047
]
Sampath Kumar commented on LOG4J2-1221:
---
I am OK to move 2.5 but problem is I am no
I do not really know that it means to do RM stuff for Log4j.
I think it would be enough to release the Scala modules, and let them
depend on Log4j API 2.5, if that is possible.
On Fri, Dec 11, 2015 at 6:09 PM, Gary Gregory
wrote:
> Seems fine with me. Label it 2.6-beta1? Mikael, are you feeling
Seems fine with me. Label it 2.6-beta1? Mikael, are you feeling up to
trying your hand at RM duties?
Should we release just these Scala modules as 2.6-beta1 or the whole suite?
Gary
On Fri, Dec 11, 2015 at 9:07 AM, Mikael Ståldal
wrote:
> So can we release some Scala API preview now when 2.5 i
In my mind, any kind of fat jar would be a new module. Matt?
Gary
On Fri, Dec 11, 2015 at 9:00 AM, Mikael Ståldal
wrote:
> I certainly hope that this will not replace the different modules we have
> today.
>
> On Thu, Dec 10, 2015 at 10:36 PM, Ralph Goers
> wrote:
>
>> I understand what this d
So can we release some Scala API preview now when 2.5 is out?
On Mon, Dec 7, 2015 at 3:58 AM, Gary Gregory wrote:
> On Dec 5, 2015 6:05 AM, "Ralph Goers" wrote:
> >
> > It would make more sense to me to release the scala beta as a single
> separate module. Then integrate it once you are sure.
>
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053030#comment-15053030
]
Gary Gregory commented on LOG4J2-1221:
--
I am telling you about our version 2.5 becau
I certainly hope that this will not replace the different modules we have
today.
On Thu, Dec 10, 2015 at 10:36 PM, Ralph Goers
wrote:
> I understand what this does in the non-OSGi case and I’m not in favor of
> it and haven’t been each time it has been brought up.
>
> Ralph
>
> On Dec 10, 2015,
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053014#comment-15053014
]
Sampath Kumar commented on LOG4J2-1221:
---
Can you tell me what is changes done to re
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053006#comment-15053006
]
Gary Gregory commented on LOG4J2-1221:
--
Can you test with our latest version 2.5?
>
[
https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1220:
-
Description:
I am adding session id in the thread context of log4j2. As per the document
thread
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampath Kumar updated LOG4J2-1221:
--
Priority: Major (was: Critical)
> Dead lock observed in BlockingWaitStrategy in Log 4J
> -
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampath Kumar updated LOG4J2-1221:
--
Priority: Critical (was: Major)
> Dead lock observed in BlockingWaitStrategy in Log 4J
> -
[
https://issues.apache.org/jira/browse/LOG4J2-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sampath Kumar updated LOG4J2-1221:
--
Priority: Critical (was: Major)
> Dead lock observed in BlockingWaitStrategy in Log 4J
> -
Sampath Kumar created LOG4J2-1221:
-
Summary: Dead lock observed in BlockingWaitStrategy in Log 4J
Key: LOG4J2-1221
URL: https://issues.apache.org/jira/browse/LOG4J2-1221
Project: Log4j 2
Issu
[
https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052783#comment-15052783
]
Ralph Goers edited comment on LOG4J2-1220 at 12/11/15 1:52 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052783#comment-15052783
]
Ralph Goers edited comment on LOG4J2-1220 at 12/11/15 1:52 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052783#comment-15052783
]
Ralph Goers commented on LOG4J2-1220:
-
If I had to guess I would suppose that the ses
[
https://issues.apache.org/jira/browse/LOG4J2-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Kumar Vadla closed LOG4J2-1218.
-
Resolution: Fixed
Thanks a lot Remko. Removing it from the pattern helped.
> How to rem
sivan created LOG4J2-1220:
-
Summary: Thread context value is different for same thread.
Key: LOG4J2-1220
URL: https://issues.apache.org/jira/browse/LOG4J2-1220
Project: Log4j 2
Issue Type: Bug
39 matches
Mail list logo
