Any interest in a fat jar?

Most projects where I use log4j2, I include all the following dependencies thanks to framework logging divergence: log4j-api log4j-core log4j-jcl log4j-jul log4j-slf4j-impl log4j-1.2-api Shading these together would be super-convenient. Would anyone else be interested in such a thing? I usually

Re: Any interest in a fat jar?

I would LOVE that. I've stopped and started this a couple of times but always got side tracked with other tasks and shifting needs for what *all* means because it does not means "all" jars since that would cause a loop. The issue is what to include and what to exclude... For example, why not

Re: Any interest in a fat jar?

The whole point here is to provide a jar... Gary On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict wrote: > You can also achieve the same thing by creating a "fat POM" that lists all > the dependencies (or the ones you're interested in). My point is you don't > have to

Re: Any interest in a fat jar?

Ralph, this doesn't affect OSGi. It's just specifying a single dependency for each project rather than specifying several. Also, using log4j-bom does reduce the amount of XML required to use log4j, but it doesn't help this use-case. On 10 December 2015 at 13:18, Gary Gregory

Re: Any interest in a fat jar?

When I use log4j, there is a typical setup I never deviate from. I commonly need an API, a default implementation, and perhaps a bridge for log4j1 compatbility. I don't care about how many jars I have as long as it's easy to configure. If I can get one POM to provide X jars, that's the solution I

[jira] [Updated] (LOG4J2-1050) Add a Log4jLookup class to help write log files relative to log4j2.xml

[ https://issues.apache.org/jira/browse/LOG4J2-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1050: - Fix Version/s: (was: 2.5) 2.5.1 > Add a Log4jLookup class to help write

[jira] [Updated] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

[ https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-849: Fix Version/s: (was: 2.5) 2.5.1 > [Perf] Add performance tests to compare

[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly with Logj2 2.3 version jars

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1086: - Fix Version/s: (was: 2.5) 2.5.1 > SizeBasedTriggeringPolicy is not

[jira] [Updated] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1013: - Fix Version/s: (was: 2.5) 2.5.1 > Log4j2 Main Arguments Lookup by name

[jira] [Updated] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1080: - Fix Version/s: (was: 2.5) 2.5.1 > Drop events when the RingBuffer is full

[jira] [Updated] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-850: Fix Version/s: (was: 2.5) 2.5.1 > [Perf] Add performance tests for

[jira] [Updated] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1011: - Fix Version/s: (was: 2.5) 2.5.1 > Dependencies for layouts should be

Re: Any interest in a fat jar?

Also, we use Ant in some of our products, I'm not going to write a POM to be used from Ant... Gary On Thu, Dec 10, 2015 at 11:17 AM, Gary Gregory wrote: > The whole point here is to provide a jar... > > Gary > > On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict

[jira] [Updated] (LOG4J2-915) Wrong timestamp of filename when SizeBasedTriggering and TimeBasedTrigger used simultaniously with RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-915: Fix Version/s: (was: 2.5) 2.5.1 > Wrong timestamp of filename when

[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy

[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1198: - Fix Version/s: (was: 2.5) 2.5.1 > Add support for custom rollover

[jira] [Closed] (LOG4J2-1219) Update SLF4J from 1.7.12 to 1.7.13

[ https://issues.apache.org/jira/browse/LOG4J2-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1219. Resolution: Fixed Fix Version/s: 2.5.1 In Git master. > Update SLF4J from 1.7.12 to 1.7.13

Re: Any interest in a fat jar?

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, at 12:55 PM, Matt Sicker wrote: > > Ralph, this doesn't affect OSGi. It's just specifying a single dependency for > each

[jira] [Created] (LOG4J2-1219) Update SLF4J from 1.7.12 to 1.7.13

Gary Gregory created LOG4J2-1219: Summary: Update SLF4J from 1.7.12 to 1.7.13 Key: LOG4J2-1219 URL: https://issues.apache.org/jira/browse/LOG4J2-1219 Project: Log4j 2 Issue Type: Task

Re: Any interest in a fat jar?

My understanding is that most of the people who combine jars like this also include the classes from their application. For that reason I don’t think it would be helpful. Beyond that, I am not sure combining them makes it “super-convenient”. The only place this might be helpful is in OSGi, and

[jira] [Created] (LOG4J2-1218) How to remove the IP Address that is getting logged in the log messages that are printed using log4j 2.2.

Kiran Kumar Vadla created LOG4J2-1218: - Summary: How to remove the IP Address that is getting logged in the log messages that are printed using log4j 2.2. Key: LOG4J2-1218 URL:

[jira] [Commented] (LOG4J2-1218) How to remove the IP Address that is getting logged in the log messages that are printed using log4j 2.2.

[ https://issues.apache.org/jira/browse/LOG4J2-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15050924#comment-15050924 ] Kiran Kumar Vadla commented on LOG4J2-1218: --- Sample log message that I am logging is as

Re: Any interest in a fat jar?

To the point of conveniences, the convenience is GREAT when I use cxf-bundle, hamcrest-all, activemq-all, jetty-all, mockito-all, and so on, instead of being forced to list out 50 or who-knows-how-many modules. For our big app server, I just use bundles and be done with it unless a specific

[jira] [Commented] (LOG4J2-1218) How to remove the IP Address that is getting logged in the log messages that are printed using log4j 2.2.

[ https://issues.apache.org/jira/browse/LOG4J2-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051069#comment-15051069 ] Remko Popma commented on LOG4J2-1218: - One more thing: please upgrade to version 2.5. > How to

[jira] [Commented] (LOG4J2-1218) How to remove the IP Address that is getting logged in the log messages that are printed using log4j 2.2.

[ https://issues.apache.org/jira/browse/LOG4J2-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051067#comment-15051067 ] Remko Popma commented on LOG4J2-1218: - I don't know your log4j2.xml configuration, but my guess is