Laurent, although my Java use-case was very simple (1 file, < 100 lines). I
still needed to log to stdout+file at the same time. Hence I needed a
logging framework (please correct me if I'm wrong). As Matt said, logging
is a "fundamental" library.

At the same time I do agree with Luarent. The internet already define
classpath at a gazillion places[1][2]. Let's not just restate what is
there. I suggest something very practical and only geared to log4j2.  What
about creating a repo like [3] and linking to it from the docs? Just make
it officially under the log4j2 organization and commit to keep it up to
date. What do the community think?

[1]:
https://docs.oracle.com/javase/tutorial/essential/environment/paths.html
[2]: https://en.wikipedia.org/wiki/Classpath_(Java)
[3]: https://github.com/Tarrasch/log4j2-minimal-examples

On Fri, Dec 2, 2016 at 1:43 PM, <l...@capsicohealth.com> wrote:

> Gotta explain what Jars are too! </sarcasm> Joking aside, Java is a very
> complex and deep platform. For casual developers, why not just use
> System.out.print? Do you really need a rich framework such as log4j for a
> casual java program? Just thinking about the simplest option for you here...
>
>
>
> Laurent Hasson
> Co-Founder & CTO, CapsicoHealth Inc.
> Sent from my BlackBerry Passport.
>
> Research has shown that capsaicin—the substance that gives hot red
> peppers (or chilies) their kick, and boosts our metabolism—keeps
> immature fat cells from developing into full-fledged ones. And a study
> presented in April found that a compound in some sweet peppers
> (called CH-19 Sweet), which resembles capsaicin, provides similar
> positive metabolic effects
>
>
>   Original Message
> From: Matt Sicker
> Sent: Friday, December 2, 2016 01:17
> To: Log4J Users List
> Reply To: Log4J Users List
> Subject: Re: Suggestion for docs improvement: What is a classpath?
>
> So you're saying you'd like the docs to include some basic introductory
> info on what a class path is, what system properties are, and how to
> configure them all? Sounds like a good idea considering log4j is such a
> fundamental library that I wouldn't expect all users to know that sort of
> thing by default.
>
> On 1 December 2016 at 21:08, Arash Rouhani Kalleh <
> aras...@vng.com.vn.invalid> wrote:
>
> > Hi Log4j community!
> >
> > After getting a constructive response from mr. Gary Gregory on Twitter on
> > one of my rage-tweets[1]. I decided to take him up on that and send some
> > feedback to this community.
> >
> > My bad experience came from spending maybe over an hour trying to just
> get
> > the framework to pick up my config file. So here I come with a practical
> > suggestion to remedy this: On this[2] docs page, under "Automatic
> > Configuration". You would change the first occurrence of "system
> property"
> > and "classpath" into a hyperlink pointing to more information *how to
> > set *those
> > values. The problem is that many casual programmers don't know (I
> didn't).
> > Would that make sense?
> >
> > Note that the mere definition of system property/classpath (the results I
> > would find when Googling the terms) are still of no use, because they
> lack
> > practical information on how to include the log4j2 configuration file
> > inside my jar and having it being read by log4j2.
> >
> > Lastly, thanks to everybody who've contributed to this well-documented,
> > well-designed, efficient logging framework. The experience is good once
> > you've got the framework to pick up your configuration file. And the more
> > users who don't get frustrated in the phase before that, the more users
> > that have energy left over to contribute back. :)
> >
> > Cheers,
> > Arash Rouhani
> >
> >
> > [1]: https://twitter.com/ArashRouhani/status/775969974397480960
> > [2]: http://logging.apache.org/log4j/2.x/manual/configuration.html
> >
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
>

Reply via email to