Comments on Eclipse plugin: Log4E
add comment plugin-details
pages: 1 2 3 Next>
Rob Miller on Jul 27, 2010 12:03 AM
I liked your site.
Log4E on Apr 12, 2007 7:08 PM
The plugin Log4E is not needed by your plugin at runtime.
Therefore I suggest that you include the library log4j.jar
(http://logging.apache.org/log4j/docs/download.html) in your own project without any dependencies to Log4E (except you really need that).
dingfelder on Apr 12, 2007 1:49 AM
I downloaded log4e fromhttp://log4e.jayefem.de/update
(autoinstalled from eclipse)
It seems to work from a normal java class, but for a plugin on the import:
import org.apache.log4j.Logger;
and every subsequent logger call I am getting the following error message:
Access restriction: The type Logger is not accessible due to restriction on required library C:
\eclipse\plugins\de.jayefem.log4e_1.2.12\lib\log4j-1.2.12.jar
I am using 3.2 eclipse.
I defined de.jayefem.log4e as a required plugin for my plugin.
Do you have any suggestions?
Log4E on Oct 27, 2006 12:23 PM
The Log4E site is down at the moment. In the meantime the plugins are temporary available at:
Eclipse 3:
http://wildepfade.de/log4e/de.jayefem.log4e_free_1.2.11.zip
http://wildepfade.de/log4e/de.jayefem.log4e_pro_1.2.11.zip
Eclipse 2:
http://wildepfade.de/log4e/de.jayefem.log4e_0.6.6.zip
WSAD 5:
http://wildepfade.de/log4e/de.jayefem.log4e_0.5.5.zip
Log4E on Feb 3, 2005 12:52 PM
The Log4E site will be down at Feb 3rd, 2005 at 9 p.m. UTC for some hours (maybe days - hopefully not). In the meantime the plugins are _temporary_ available at:
Eclipse 3:
http://wildepfade.de/log4e/de.jayefem.log4e_0.7.7.zip
Eclipse 2:
http://wildepfade.de/log4e/de.jayefem.log4e_0.6.6.zip
WSAD 5:
http://wildepfade.de/log4e/de.jayefem.log4e_0.5.5.zip
BTW: if you're interested in arts you may have a look at the site http://wildepfade.de itself where you can find wonderful paintings from my mom :-)
Log4E on Nov 13, 2004 3:34 PM
As there where several enquiries with the same issue I disabled the "action definitionId" in the plugin.xml. The Log4E entry in the main menu "Edit" disappears due to that, but I think that it isn't a big loss.
I never could reproduce that problem, so I hope it is fixed now.
Besides only minor changes in the new version. No big deal.
-Jan
ekkehard on Nov 13, 2004 9:24 AM
errors with 3.1M3
there are many errors in the error log,
per ex.:
The command 'de.jayefem.log4e.DeclareCommand' is not defined, but is being asked if it is active. Are you using an actionDefinitionId without defining a command?
...
The command 'de.jayefem.log4e.AddPositionCommand' is not defined, but is being asked if it is active. Are you using an actionDefinitionId without defining a command?
.....
regards
ekkehard
michael on Oct 19, 2004 10:57 AM
Hi Jan,
imo, this seems to be the easiest solution:
a new variable ${leadin} is introduced, which can be specified on the config-page for "Method Start/Exit", too
(in addition to ${message}).
The template for level statements is changed from e.g.
debug("${enclosing_method}${delimiter}${message}${delimiter}${return_value}")
to
debug("${leadin}${enclosing_method}${delimiter}${message}${delimiter}${return_value}")
... and that's it...
br
Michael
Log4E on Oct 14, 2004 2:48 PM
Hi Micheal,
OK, I see the point. I don't have a solution yet. Maybe a new template variable, but that could be very confusing for the user. I will think about it but I don't think that it will be a new feature in the near future.
If you've got a good idea solving that problem, please mail me or post it in this forum.
Thanks,
Jan.
michael on Oct 14, 2004 6:33 AM
I think I have to clarify my previous comment:
e.g. System.out.println("reached here");
would be converted to a log statement printing out:
reached here func()
michael
pages: 1 2 3 Next>
