I missed that. Added to my pom - should running mvn package be enough to generate the file?
It looks like it doesn't. I see this warning: WARNING: this tool is superseded by the annotation processor included in log4j-core. And in the file system I have an empty directory: \target\generated-sources\annotations Best Regards, Yair Ogen -----Original Message----- From: Remko Popma [mailto:[email protected]] Sent: Thursday, July 17, 2014 16:30 To: Log4J Users List Subject: Re: Converter Plugin not loaded On Thu, Jul 17, 2014 at 10:24 PM, Yair Ogen (yaogen) <[email protected]> wrote: > In my case it find the *.dat file from core jar. Not clear how can we > add more custom plugins. > Do you build with maven? The Plugin Preloading section <http://logging.apache.org/log4j/2.x/manual/plugins.html#Plugin_Preloading> on the Plugins page gives a sample snippet to add to your pom.xml to make Maven generate the *.dat file for your plugins. > The same applies to my configuration plugin. I had to also use a > ContextFactory and call start(new MyNewConfiguration()) manually for > the custom configuration to work. > > Something in the plugin mechanism is not extension friendly. > > Best Regards, > > Yair Ogen > > -----Original Message----- > From: Jaime Sastre [mailto:[email protected]] > Sent: Thursday, July 17, 2014 16:20 > To: Log4J Users List > Subject: RE: Converter Plugin not loaded > > I will try to do it bw today and tomorrow. > From what I see in code in pluginmanager: > > private static PluginRegistry<PluginType<?>> decode(final > ResourceLoader loader) { > final Enumeration<URL> resources; > try { > resources = > loader.getResources(PluginProcessor.PLUGIN_CACHE_FILE); > if (resources == null) { > return null; > } > } catch (final IOException ioe) { > LOGGER.warn("Unable to preload plugins", ioe); > return null; > } > final PluginRegistry<PluginType<?>> map = new > PluginRegistry<PluginType<?>>(); > while (resources.hasMoreElements()) { > > It cannot load PluginProcessor.PLUGIN_CACHE_FILE > resources.hasMoreElements() == false > > Probably a classloading issue since PluginProcessor.PLUGIN_CACHE_FILE > exists on the jar file > > > -----Mensaje original----- > De: Remko Popma [mailto:[email protected]] Enviado el: jueves, 17 > de julio de 2014 15:03 > Para: Log4J Users List > Asunto: Re: Converter Plugin not loaded > > Would it be possible to provide a small sample project that > demonstrates the problem? > You may want to create a Jira ticket to attach files to (the mailing > list software does not like attachments). > > Remko > > > On Thu, Jul 17, 2014 at 10:00 PM, Yair Ogen (yaogen) > <[email protected]> > wrote: > > > Just recently joined the mailing list - can you please share? > > > > Yair > > > > -----Original Message----- > > From: Jaime Sastre [mailto:[email protected]] > > Sent: Thursday, July 17, 2014 15:59 > > To: Log4J Users List > > Subject: RE: Converter Plugin not loaded > > > > I think it is related to my issue (previous email) > > > > -----Mensaje original----- > > De: Yair Ogen (yaogen) [mailto:[email protected]] Enviado el: jueves, > > 17 de julio de 2014 14:43 > > Para: [email protected] > > Asunto: Converter Plugin not loaded > > > > I am trying to extend log4j2. > > > > I created my own configuration factory that is loaded just fine. In > > there I give it a default pattern with some new converters. > > > > I created a converter with the needed annotations. However, seems > > that the plugin manager is not picking these up. Only plugins that > > exists in "" are actually loaded. > > > > What am I missing? > > > > Yair > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
