[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1548:
-
Attachment: LOG4J2-1548-testcase-cleanFoldersRule.patch
[~garydgregory] I have added a sm
[
https://issues.apache.org/jira/browse/LOG4J2-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT updated LOG4J2-1320:
-
Attachment: LOG4J2-1320-testcase-cleanFoldersRule.patch
Hi [~garydgregory],
Attached pat
[
https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444854#comment-15444854
]
Gary Gregory commented on LOG4J2-1553:
--
(On my phone) the commits are supposed to be
[
https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444507#comment-15444507
]
Ralph Goers commented on LOG4J2-1553:
-
Yeah, I am not a big fan of issues like this t
[
https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444318#comment-15444318
]
Bill Okara commented on LOG4J2-1535:
actually the issue only happened if putting the
[
https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444297#comment-15444297
]
Remko Popma commented on LOG4J2-1553:
-
Don't get me wrong. I appreciate these are all
[
https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444277#comment-15444277
]
Remko Popma commented on LOG4J2-1553:
-
Why do you think so? Can you share your use ca
I don't think the close() method should be renamed to closeOutputStream(),
at least for
MemoryMappedFileManager,
RandomAccessFileManager, and
RollingRandomAccessFileManager.
The above three have a dummy OutputStream because they inherit from
OuputStreamManager, but closing this stream does not do
[
https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444161#comment-15444161
]
Gary Gregory commented on LOG4J2-1502:
--
I think the problem is that a 0x00 is writte
[
https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444157#comment-15444157
]
Gary Gregory commented on LOG4J2-1502:
--
Might have found something with
org.apache.
[
https://issues.apache.org/jira/browse/LOG4J2-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444157#comment-15444157
]
Gary Gregory edited comment on LOG4J2-1502 at 8/28/16 9:31 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15444097#comment-15444097
]
Gary Gregory commented on LOG4J2-1553:
--
Implemented in branch {{LOG4J2-1553}}.
> Ab
Gary Gregory created LOG4J2-1553:
Summary: AbstractManager should implement AutoCloseable
Key: LOG4J2-1553
URL: https://issues.apache.org/jira/browse/LOG4J2-1553
Project: Log4j 2
Issue Type:
On Sun, Aug 28, 2016 at 12:00 PM, Ralph Goers
wrote:
> The changes.xml already says 2.7. The versions in the poms don’t matter.
> I know I have told you this before, but no matter what you set them to the
> release plugin is going to change them to whatever version I set when I run
> the release
The changes.xml already says 2.7. The versions in the poms don’t matter. I
know I have told you this before, but no matter what you set them to the
release plugin is going to change them to whatever version I set when I run the
release build. So modifying the pom versions now is just a waste of
Gary Gregory created LOG4J2-1552:
Summary: Help Apache Camel project to upgrade from Log4j 1.x to 2.x
Key: LOG4J2-1552
URL: https://issues.apache.org/jira/browse/LOG4J2-1552
Project: Log4j 2
Ok, we do have quite the flurry of branch merging here... :-) I've got a
lot I am curious to review in more detail than the scanning I've done in
the past; we are definitively in 2.7 territory here... as opposed to 2.6.3
which is the current version in the repo.
Check?
Gary
On Aug 24, 2016 4:15
[
https://issues.apache.org/jira/browse/LOG4J2-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1542:
Fix Version/s: 2.7
> java.lang.ArrayIndexOutOfBoundsException in
> ParameterizedMessage.formatTo(P
[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443634#comment-15443634
]
Remko Popma edited comment on LOG4J2-1010 at 8/28/16 3:52 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443634#comment-15443634
]
Remko Popma commented on LOG4J2-1010:
-
[[email protected]] {{ContextDataInj
Hi,
Is there a specific version of Scala plugins I should use to get the new
Scala modules to build in Eclipse? Is it possible to have both the 2.10 and
2.11 Scala modules building in the same workspace with the same Eclipse
plugin?
Gary
--
E-Mail: [email protected] | [email protected]
J
[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443428#comment-15443428
]
Remko Popma commented on LOG4J2-1010:
-
Thanks for the tip. I find that links in the t
[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443390#comment-15443390
]
Remko Popma commented on LOG4J2-1010:
-
That would not solve the problem and would add
The method StatusConfiguration.initialize() is invoked from
ConfigurationBuilder.build() and the constructors of XmlConfiguration,
JsonConfiguration and CompositeConfiguration.
Would it make sense if this was instead done in one place, in
Configuration.initialize()? That would make the lifecycle o
[
https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443357#comment-15443357
]
Remko Popma commented on LOG4J2-1528:
-
I have looked at the branch. This is all new f
[
https://issues.apache.org/jira/browse/LOG4J2-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443344#comment-15443344
]
Mikael Ståldal commented on LOG4J2-1535:
What happen if you try to create a Kafka
[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443340#comment-15443340
]
Mikael Ståldal commented on LOG4J2-1010:
Maybe consider my proposal of moving the
+1 Good idea!
On Sun, Aug 28, 2016 at 7:12 PM, Mikael Ståldal
wrote:
> I think that some people find the project on GitHub, and they might not be
> aware about our JIRA. Should we mention this in the README.md that is
> visible on GitHub?
>
> On Aug 27, 2016 2:30 PM, "Mikael Ståldal"
> wrote:
>
I think that some people find the project on GitHub, and they might not be
aware about our JIRA. Should we mention this in the README.md that is
visible on GitHub?
On Aug 27, 2016 2:30 PM, "Mikael Ståldal" wrote:
> Does anyone keep track of incoming pull requests on GitHub? It seems like
> we ge
[
https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal resolved LOG4J2-1181.
Resolution: Fixed
Fix Version/s: 2.7
I think this is ready for release now. There ar
30 matches
Mail list logo
