You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2015/12/10 19:13:33 UTC

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 see this sort of thing in testing
frameworks (like mockito-all, hamcrest-all, etc.), but calling this
log4j-all would be incorrect.

-- 
Matt Sicker <bo...@gmail.com>

Re: Any interest in a fat jar?

Posted by Gary Gregory <ga...@gmail.com>.
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 include nosql and io-streams?

For me, today, my "all" is to provide customers Log4j2 with *all*
appenders, so that they can go to town on configuring events to go anywhere
Log4j supports.

Integration with other frameworks is a second concern that I do not want in
*all*, today.

Other projects use "bundle" instead of "all" (like Apache CXF). I'll call
it "bundle" from now now since it is not really "all".

Let's review all of our modules, I mark with * what I see as minimal in
"bundle":

log4j-1.2-api
log4j-api *
log4j-bom
log4j-core *
log4j-distribution
log4j-flume-ng *
log4j-iostreams *
log4j-jcl
log4j-jmx-gui *
log4j-jul
log4j-liquibase *
log4j-nosql *
log4j-perf
log4j-samples
log4j-slf4j-impl
log4j-taglib *
log4j-to-slf4j
log4j-web

I'm not quite sure what "bom" does.

I would NOT want log4j-1.2-api in bundle because I do not want to hijack
the 1.2 API calls since I have code that provides custom 1.2 Appenders.

Would including log4j-web cause problems for folks in a container?

Would including any of the other logging modules cause issues like the one
I have with 1.2 APIs?

Gary


On Thu, Dec 10, 2015 at 10:13 AM, Matt Sicker <bo...@gmail.com> wrote:

> 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 see this sort of thing in testing
> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
> log4j-all would be incorrect.
>
> --
> Matt Sicker <bo...@gmail.com>
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Any interest in a fat jar?

Posted by Matt Sicker <bo...@gmail.com>.
This would be in addition. Not everyone needs all the bridges or additional
framework support.

On 11 December 2015 at 11:08, Gary Gregory <ga...@gmail.com> 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 <mikael.staldal@magine.com
> > 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 <ralph.goers@dslextreme.com
>> > 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, at 12:55 PM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> 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 <ga...@gmail.com>
>>> wrote:
>>>
>>>> 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 <ga...@gmail.com>
>>>> wrote:
>>>>
>>>>> The whole point here is to provide a jar...
>>>>>
>>>>> Gary
>>>>>
>>>>> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
>>>>> 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 build another jar; you can achieve this by building
>>>>>> another POM.
>>>>>>
>>>>>> Cheers,
>>>>>> Paul
>>>>>>
>>>>>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <
>>>>>> garydgregory@gmail.com> wrote:
>>>>>>
>>>>>>> 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 dependency problem arises.
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>>>>>> ralph.goers@dslextreme.com> wrote:
>>>>>>>
>>>>>>>> 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
>>>>>>>> even then I am not sure as I don’t really know enough about OSGi. Also, we
>>>>>>>> need to look at the new module system in Java 9.
>>>>>>>>
>>>>>>>> Ralph
>>>>>>>>
>>>>>>>>
>>>>>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> 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 see this sort of thing in testing
>>>>>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>>>>>> log4j-all would be incorrect.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>>>> Java Persistence with Hibernate, Second Edition
>>>>>>> <http://www.manning.com/bauer3/>
>>>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>>>>> Blog: http://garygregory.wordpress.com
>>>>>>> Home: http://garygregory.com/
>>>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>> Java Persistence with Hibernate, Second Edition
>>>>> <http://www.manning.com/bauer3/>
>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>> Java Persistence with Hibernate, Second Edition
>>>> <http://www.manning.com/bauer3/>
>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
>>>>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.staldal@magine.com
>> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com
>>
>> Privileged and/or Confidential Information may be contained in this
>> message. If you are not the addressee indicated in this message
>> (or responsible for delivery of the message to such a person), you may
>> not copy or deliver this message to anyone. In such case,
>> you should destroy this message and kindly notify the sender by reply
>> email.
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker <bo...@gmail.com>

Re: Any interest in a fat jar?

Posted by Gary Gregory <ga...@gmail.com>.
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 <mi...@magine.com>
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 <ra...@dslextreme.com>
> 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, at 12:55 PM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> 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 <ga...@gmail.com>
>> wrote:
>>
>>> 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 <ga...@gmail.com>
>>> wrote:
>>>
>>>> The whole point here is to provide a jar...
>>>>
>>>> Gary
>>>>
>>>> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
>>>> 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 build another jar; you can achieve this by building another
>>>>> POM.
>>>>>
>>>>> Cheers,
>>>>> Paul
>>>>>
>>>>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <garydgregory@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> 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 dependency problem arises.
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>>>>> ralph.goers@dslextreme.com> wrote:
>>>>>>
>>>>>>> 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
>>>>>>> even then I am not sure as I don’t really know enough about OSGi. Also, we
>>>>>>> need to look at the new module system in Java 9.
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>>
>>>>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>>
>>>>>>> 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 see this sort of thing in testing
>>>>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>>>>> log4j-all would be incorrect.
>>>>>>>
>>>>>>> --
>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>>> Java Persistence with Hibernate, Second Edition
>>>>>> <http://www.manning.com/bauer3/>
>>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>>>> Blog: http://garygregory.wordpress.com
>>>>>> Home: http://garygregory.com/
>>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>> Java Persistence with Hibernate, Second Edition
>>>> <http://www.manning.com/bauer3/>
>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
>>>>
>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>
>
> --
> [image: MagineTV]
>
> *Mikael Ståldal*
> Senior software developer
>
> *Magine TV*
> mikael.staldal@magine.com
> Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com
>
> Privileged and/or Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply
> email.
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Any interest in a fat jar?

Posted by Mikael Ståldal <mi...@magine.com>.
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 <ra...@dslextreme.com>
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, at 12:55 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> 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 <ga...@gmail.com> wrote:
>
>> 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 <ga...@gmail.com>
>> wrote:
>>
>>> The whole point here is to provide a jar...
>>>
>>> Gary
>>>
>>> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
>>> 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 build another jar; you can achieve this by building another
>>>> POM.
>>>>
>>>> Cheers,
>>>> Paul
>>>>
>>>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
>>>> wrote:
>>>>
>>>>> 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 dependency problem arises.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>>>> ralph.goers@dslextreme.com> wrote:
>>>>>
>>>>>> 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
>>>>>> even then I am not sure as I don’t really know enough about OSGi. Also, we
>>>>>> need to look at the new module system in Java 9.
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>>
>>>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>
>>>>>> 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 see this sort of thing in testing
>>>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>>>> log4j-all would be incorrect.
>>>>>>
>>>>>> --
>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>> Java Persistence with Hibernate, Second Edition
>>>>> <http://www.manning.com/bauer3/>
>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
>


-- 
[image: MagineTV]

*Mikael Ståldal*
Senior software developer

*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3  | 114 46 Stockholm, Sweden  |   www.magine.com

Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.

Re: Any interest in a fat jar?

Posted by Ralph Goers <ra...@dslextreme.com>.
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 <bo...@gmail.com> wrote:
> 
> 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 <garydgregory@gmail.com <ma...@gmail.com>> wrote:
> 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 <garydgregory@gmail.com <ma...@gmail.com>> wrote:
> The whole point here is to provide a jar... 
> 
> Gary
> 
> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pbenedict@apache.org <ma...@apache.org>> 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 build another jar; you can achieve this by building another POM.
> 
> Cheers,
> Paul
> 
> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <garydgregory@gmail.com <ma...@gmail.com>> wrote:
> 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 dependency problem arises.
> 
> Gary
> 
> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <ralph.goers@dslextreme.com <ma...@dslextreme.com>> wrote:
> 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 even then I am not sure as I don’t really know enough about OSGi. Also, we need to look at the new module system in Java 9.
> 
> Ralph
> 
> 
>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <boards@gmail.com <ma...@gmail.com>> wrote:
>> 
>> 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 see this sort of thing in testing frameworks (like mockito-all, hamcrest-all, etc.), but calling this log4j-all would be incorrect.
>> 
>> -- 
>> Matt Sicker <boards@gmail.com <ma...@gmail.com>>
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com <ma...@gmail.com> | ggregory@apache.org  <ma...@apache.org>
> Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com <ma...@gmail.com> | ggregory@apache.org  <ma...@apache.org>
> Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com <ma...@gmail.com> | ggregory@apache.org  <ma...@apache.org>
> Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> -- 
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>


Re: Any interest in a fat jar?

Posted by Paul Benedict <pb...@apache.org>.
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
want. I don't want to include more bytes than necessary (i.e., a big jar of
things I may not use).

Cheers,
Paul

On Thu, Dec 10, 2015 at 1:55 PM, Matt Sicker <bo...@gmail.com> wrote:

> 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 <ga...@gmail.com> wrote:
>
>> 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 <ga...@gmail.com>
>> wrote:
>>
>>> The whole point here is to provide a jar...
>>>
>>> Gary
>>>
>>> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
>>> 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 build another jar; you can achieve this by building another
>>>> POM.
>>>>
>>>> Cheers,
>>>> Paul
>>>>
>>>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
>>>> wrote:
>>>>
>>>>> 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 dependency problem arises.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>>>> ralph.goers@dslextreme.com> wrote:
>>>>>
>>>>>> 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
>>>>>> even then I am not sure as I don’t really know enough about OSGi. Also, we
>>>>>> need to look at the new module system in Java 9.
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>>
>>>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>
>>>>>> 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 see this sort of thing in testing
>>>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>>>> log4j-all would be incorrect.
>>>>>>
>>>>>> --
>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>>> Java Persistence with Hibernate, Second Edition
>>>>> <http://www.manning.com/bauer3/>
>>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>>> Blog: http://garygregory.wordpress.com
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>

Re: Any interest in a fat jar?

Posted by Matt Sicker <bo...@gmail.com>.
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 <ga...@gmail.com> wrote:

> 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 <ga...@gmail.com>
> wrote:
>
>> The whole point here is to provide a jar...
>>
>> Gary
>>
>> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
>> 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 build another jar; you can achieve this by building another
>>> POM.
>>>
>>> Cheers,
>>> Paul
>>>
>>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
>>> wrote:
>>>
>>>> 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 dependency problem arises.
>>>>
>>>> Gary
>>>>
>>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>>> ralph.goers@dslextreme.com> wrote:
>>>>
>>>>> 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 even then I am not
>>>>> sure as I don’t really know enough about OSGi. Also, we need to look at the
>>>>> new module system in Java 9.
>>>>>
>>>>> Ralph
>>>>>
>>>>>
>>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>
>>>>> 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 see this sort of thing in testing
>>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>>> log4j-all would be incorrect.
>>>>>
>>>>> --
>>>>> Matt Sicker <bo...@gmail.com>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>>> Java Persistence with Hibernate, Second Edition
>>>> <http://www.manning.com/bauer3/>
>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
>>>>
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker <bo...@gmail.com>

Re: Any interest in a fat jar?

Posted by Gary Gregory <ga...@gmail.com>.
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 <ga...@gmail.com>
wrote:

> The whole point here is to provide a jar...
>
> Gary
>
> On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
> 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 build another jar; you can achieve this by building another
>> POM.
>>
>> Cheers,
>> Paul
>>
>> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>
>>> 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 dependency problem arises.
>>>
>>> Gary
>>>
>>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <
>>> ralph.goers@dslextreme.com> wrote:
>>>
>>>> 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 even then I am not
>>>> sure as I don’t really know enough about OSGi. Also, we need to look at the
>>>> new module system in Java 9.
>>>>
>>>> Ralph
>>>>
>>>>
>>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> 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 see this sort of thing in testing
>>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>>> log4j-all would be incorrect.
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>>> Java Persistence with Hibernate, Second Edition
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>>
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Any interest in a fat jar?

Posted by Gary Gregory <ga...@gmail.com>.
The whole point here is to provide a jar...

Gary

On Thu, Dec 10, 2015 at 10:40 AM, Paul Benedict <pb...@apache.org>
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 build another jar; you can achieve this by building another POM.
>
> Cheers,
> Paul
>
> On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
> wrote:
>
>> 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 dependency problem arises.
>>
>> Gary
>>
>> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <ralph.goers@dslextreme.com
>> > wrote:
>>
>>> 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 even then I am not
>>> sure as I don’t really know enough about OSGi. Also, we need to look at the
>>> new module system in Java 9.
>>>
>>> Ralph
>>>
>>>
>>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> 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 see this sort of thing in testing
>>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>>> log4j-all would be incorrect.
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> Java Persistence with Hibernate, Second Edition
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Any interest in a fat jar?

Posted by Paul Benedict <pb...@apache.org>.
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 build another jar; you can achieve this by building another POM.

Cheers,
Paul

On Thu, Dec 10, 2015 at 12:38 PM, Gary Gregory <ga...@gmail.com>
wrote:

> 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 dependency problem arises.
>
> Gary
>
> On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> 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 even then I am not
>> sure as I don’t really know enough about OSGi. Also, we need to look at the
>> new module system in Java 9.
>>
>> Ralph
>>
>>
>> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> 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 see this sort of thing in testing
>> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
>> log4j-all would be incorrect.
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

Re: Any interest in a fat jar?

Posted by Gary Gregory <ga...@gmail.com>.
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 dependency problem arises.

Gary

On Thu, Dec 10, 2015 at 10:28 AM, Ralph Goers <ra...@dslextreme.com>
wrote:

> 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 even then I am not sure as
> I don’t really know enough about OSGi. Also, we need to look at the new
> module system in Java 9.
>
> Ralph
>
>
> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> 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 see this sort of thing in testing
> frameworks (like mockito-all, hamcrest-all, etc.), but calling this
> log4j-all would be incorrect.
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Any interest in a fat jar?

Posted by Ralph Goers <ra...@dslextreme.com>.
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 even then I am not sure as I don’t really know enough about OSGi. Also, we need to look at the new module system in Java 9.

Ralph


> On Dec 10, 2015, at 11:13 AM, Matt Sicker <bo...@gmail.com> wrote:
> 
> 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 see this sort of thing in testing frameworks (like mockito-all, hamcrest-all, etc.), but calling this log4j-all would be incorrect.
> 
> -- 
> Matt Sicker <boards@gmail.com <ma...@gmail.com>>