Please do not send emails to individuals but please keep your mail on the Log4j
mailing lists.
In case you are not aware most open source software projects are developed by
people who are volunteering their time to do so. Some committers at the ASF are
lucky in that their employers do pay them
> On May 21, 2017, at 7:32 PM, Remko Popma wrote:
>
>
>> On May 22, 2017, at 8:57, Ralph Goers wrote:
>>
>> When you run the release plugin the artifact is deployed when the module
>> gets to the deploy phase. Thus any shading would take place too late to do
>> any good.
>
> I think there'
[
https://issues.apache.org/jira/browse/LOG4J2-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019107#comment-16019107
]
Gary Gregory commented on LOG4J2-1911:
--
Thank you for the report.
Can you please p
On May 21, 2017 7:32 PM, "Remko Popma" wrote:
> On May 22, 2017, at 8:57, Ralph Goers wrote:
>
> When you run the release plugin the artifact is deployed when the module
gets to the deploy phase. Thus any shading would take place too late to do
any good.
I think there's a misunderstanding: the
> On May 22, 2017, at 8:57, Ralph Goers wrote:
>
> When you run the release plugin the artifact is deployed when the module gets
> to the deploy phase. Thus any shading would take place too late to do any
> good.
I think there's a misunderstanding: the shade plugin is bound to the package
ph
When you run the release plugin the artifact is deployed when the module gets
to the deploy phase. Thus any shading would take place too late to do any good.
It could be done if we renamed log4j-api to something else and then disable the
deploy in the module. Then the new log4j-api could create
> On May 22, 2017, at 5:30, Ralph Goers wrote:
>
> I’m not sure how to make it be any better than this. Although the Java 9
> classes could be removed we would just have to put them back in a couple of
> months when Java 9 is released. Putting them in a separate module is not a
> great option
If you see an interesting post on the Jigsaw ML, feel free to post a link
to it here.
Gary
On May 21, 2017 1:45 PM, "Ralph Goers" wrote:
> I’ve been following the jigsaw mailing list. The consensus on the advice
> I’ve been getting leads me to believe that log4j-api will be able to be a
> “real
I like it, let's see what happens with the next module ballot and not sink
too much time into this. I was initially ticked off that my IDE set up go
messed up, but I got over it ;-). I wonder if Oracle would ram it down Java
9's throat anyway...
Gary
On May 21, 2017 1:45 PM, "Ralph Goers" wrote:
In Eclipse Oxygen with the Java 9 beta support addon, I setup the log4j-api
project with Java 9 and Java 7 as the target and it works. I have not
checked with the latest Java9 folder though.
We are on the bleeding edge for sure here.
The only part that is not great is that we require Java 9 to be
I’ve been following the jigsaw mailing list. The consensus on the advice I’ve
been getting leads me to believe that log4j-api will be able to be a “real”
module but that log4j core will be an automatic module with just the manifest
header that declares the name of the module. There is some clean
Unsuscribe
El 21 may. 2017 4:29 AM, "Ralph Goers"
escribió:
> I’ve modified the build to put the Java 9 classes of the API into a
> separate source directory. Can you see if that helps things in Eclipse?
>
> Ralph
>
I’m not sure how to make it be any better than this. Although the Java 9
classes could be removed we would just have to put them back in a couple of
months when Java 9 is released. Putting them in a separate module is not a
great option as that will require an additional jar to run in Java 9.
R
Since src/main/java9 isn’t normally considered a source directory you should be
able to work with Java 7 as well. It will just ignore the Java 9 files.
Ralph
> On May 21, 2017, at 5:50 AM, Gary Gregory wrote:
>
> I set the JRE for that project to Java 9. I do not think you can set the
> JRE pe
Same with IntelliJ IDEA. You can set JRE per module (such as log4j-api,
log4j-core), but not per source folder.
So this is not enough to fix it. But it is better than nothing, so
please keep it. And do the same for tests if/when we add any tests for
the code in src/main/java9.
I am now able
We need to fix this very soon. It is not acceptable to have the project
master branch in a state which breaks both of the two most popular Java
IDEs.
In IntelliJ I now get stuck at com.sun.tools.jconsole.JConsolePlugin not
found in log4j-jmx-gui.
If we cannot fix this in a timely manner, I s
[
https://issues.apache.org/jira/browse/LOG4J2-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-1918.
---
Resolution: Duplicate
> Issues with log4j2 socket appender - Logs are lost when target application
>
[
https://issues.apache.org/jira/browse/LOG4J2-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers updated LOG4J2-1918:
Description:
We are facing intermittent lost of logs while sending logs to log target using
log4j2
[
https://issues.apache.org/jira/browse/LOG4J2-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-1917.
---
> Log4j api should use Java's ServiceLoader to locate implememtations
> -
I set the JRE for that project to Java 9. I do not think you can set the
JRE per source folder, only per project.
Gary
On May 21, 2017 1:29 AM, "Ralph Goers" wrote:
I’ve modified the build to put the Java 9 classes of the API into a
separate source directory. Can you see if that helps things in
[
https://issues.apache.org/jira/browse/LOG4J2-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1917.
-
Resolution: Fixed
Changes applied.
> Log4j api should use Java's ServiceLoader to locate impleme
I’ve modified the build to put the Java 9 classes of the API into a separate
source directory. Can you see if that helps things in Eclipse?
Ralph
[
https://issues.apache.org/jira/browse/LOG4J2-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018753#comment-16018753
]
ASF subversion and git services commented on LOG4J2-1917:
-
Commit
Girish created LOG4J2-1918:
--
Summary: Issues with log4j2 socket appender - Logs are lost when
target application closes the tcp connection after idle time
Key: LOG4J2-1918
URL: https://issues.apache.org/jira/browse/LOG4J
[
https://issues.apache.org/jira/browse/LOG4NET-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018712#comment-16018712
]
Dominik Psenner commented on LOG4NET-565:
-
Would you please refactor your changes
To me the gitflow concept boils down to a way of tydying up the historical
mess that piles up over the years. The branch
feature/RollingFileAppender-NG dates actually back to 2012. I'd be happy
already if we had a naming convention for the different branch types. From
the branch name alone it is at
26 matches
Mail list logo
