facebook

How to shut off *lots* of debug output from xdoclet [Closed]

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #198718 Reply

    I’m getting *lots* of output from ejbdoclet all of a sudden and can’t find out how I turned it on or (more importantly 🙂 how to turn it off. 🙂

    I don’t see any settings in the generated ant file that would obviously cause this behaviour and it wasn’t generating them at one point either.

    I feel silly reporting this but its really getting in the way of me solving real xdoclet problems. Any ideas what I did or what is causing this?

    Thanks!

    Mike Dickson

    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:82)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – resourceKey=SKIP_NO_XDOCLET_XML
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:83)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – #arguments=1
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:89)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – arg #0=C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_2.6.2\data\libraryset\1.3\jts.jar
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:91)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getBundle] – bundleKey=xdoclet.loader.LoaderMessagesMessages
    [ejbdoclet] at xdoclet.util.Translator.getBundle(Translator.java:138)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – resource=Skipping {0} (no META-INF/xdoclet.xml in here).
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:100)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – return message: Skipping C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_2.6.2\data\libraryset\1.3\jts.jar (no META-INF/xdoclet.xml in here).
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:104)
    [ejbdoclet] DEBUG [xdoclet.loader.ModuleFinder.findModules] – Skipping C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_2.6.2\data\libraryset\1.3\jts.jar (no META-INF/xdoclet.xml in here).
    [ejbdoclet] at xdoclet.loader.ModuleFinder.findModules(ModuleFinder.java:149)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – bundleKey=xdoclet.loader.LoaderMessagesMessages
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:82)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – resourceKey=SKIP_NO_XDOCLET_XML
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:83)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – #arguments=1
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:89)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – arg #0=C:\Program Files\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_2.6.2\data\libraryset\1.3\mail.jar
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:91)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getBundle] – bundleKey=xdoclet.loader.LoaderMessagesMessages
    [ejbdoclet] at xdoclet.util.Translator.getBundle(Translator.java:138)
    [ejbdoclet] DEBUG [xdoclet.util.Translator.getString] – resource=Skipping {0} (no META-INF/xdoclet.xml in here).
    [ejbdoclet] at xdoclet.util.Translator.getString(Translator.java:100)

    #198721 Reply

    I have a log4j properties file in the root of my source tree that the xdoclet runtime was picking up and using!

    Mike

    #198733 Reply

    Scott Anderson
    Participant

    Mike,

    Glad you figured this one out, because it’s an odd one. I’ve often been asked how to make XDoclet generate more debug information so it seems you’ve found the key. Could you post steps you undertook to get this level of output? I know it would really help others that have struggled with this issue, but from the other side. 🙂

    –Scott
    MyEclipse Support

    #198737 Reply

    I placed a log4j.properties file in the root of my source directory. The goal was to get this into the built deployment as a resource but Xdoclet saw it and used the settings when running…

    Hope this helps

    Here’s the log4j.properties file:

    log4j.rootLogger=DEBUG, stdout

    log4j.appender.stdout=org.apache.log4j.ConsoleAppender
    log4j.appender.stdout.layout=org.apache.log4j.PatternLayout

    # Pattern to output the caller’s file name and line number.
    log4j.appender.stdout.layout.ConversionPattern=%5p [%c] – %m%n at %l%n

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: How to shut off *lots* of debug output from xdoclet [Closed]

You must be logged in to post in the forum log in