PluginManager.addPackage(“com.myorg.mypackage”) works with trunk ! But for
me it is almost the same as setting the system property.
I would love that it automatically find my ConfigurationFactory. Is it a
bug?
Clément
On Fri, Aug 1, 2014 at 11:02 AM, Remko Popma wrote:
> The packages attribute
We're using a Servlet 2.5 container and configuration. I added the
Log4jContextSelector environment variable to the container startup as well
as loading all the Log4j 2.0 jars with the container. I added the following
items to my web.xml:
isLog4jContextSelectorNamed
true
log4j
The packages attribute in configuration (and the corresponding
PluginManager.addPackage method) does not work in 2.0.
This has been fixed in trunk and the fix will be in the upcoming 2.0.1
release.
Can you try with trunk?
On Sat, Aug 2, 2014 at 2:05 AM, Clément Guillaume
wrote:
> The fact is t
The fact is that the method getSupportedTypes() is never called ! (It's
return a custom extension: ".myorg")
I'm using 2.0. And even a call to
PluginManager.addPackage(“com.myorg.mypackage”)
doesn't works.
Clément
On Thu, Jul 31, 2014 at 10:31 PM, Ralph Goers
wrote:
> It also occurs to me that
Ok. Take a look at the system properties section of the Configuration manual
page. There seem to be two settings. I'm not sure which to use:
Log4jDefaultStatusLevel or log4j2.StatusLogger.level.
Sent from my iPhone
> On 2014/08/01, at 16:15, Marco Cosentino wrote:
>
> Hi Remko,
> thanks for
Hi Remko,
thanks for the reply.
I'd still like something which can be enabled through system preoperties
and logs at very early stages, for example, where the config is read from.
Marco.
On 08/01/2014 12:04 AM, Remko Popma wrote:
All you need to do is set status="trace" in your log4j2.xml con
