Menu

#3 "Javadoc returned 1" error

open
nobody
None
5
2006-04-28
2006-04-28
Anonymous
No

Installed all - default preferences except setting
javadoc path. Running "Project/Generate Javadoc"
generates javadocs without error but with some
warnings. "Generate a Class Diagram" returns "Javadoc
returned 1" error. Does this indicate that I need to
clean up all the javadoc warnings first? Or something
more sinister...

Thanks.
scottsplace98@yahoo.com

Discussion

  • Antti Hakala

    Antti Hakala - 2006-05-03

    Logged In: YES
    user_id=1293256

    Do you use jdk >= 1.5? Newest UMLGraph versions don't work
    with earlier versions of Java. What Eclipse version and
    operating system are you using?

     
  • Martin Petrovsky

    Logged In: YES
    user_id=1440343

    I have managed to reproduce this if I have a class that
    imports org.apache.commons.lang.enum.Enum; This is on a
    Java 1.4 project running under eclipse using Java 1.5 and
    using UMLGraph-2.10.

    If I however switch to using Java 1.4 to load eclipse and
    switch to using UMLGraph-2.10 then the problem goes away.

    It may be an incompatibility with javadoc in Java 1.5 and
    the reserved enum keyword?

     
  • Nobody/Anonymous

    Logged In: NO

    I've the same problem. (returned 1)
    eclipse.buildId=I20050627-1435
    java.version=1.4.2_08
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT
    Command-line arguments: -os win32 -ws win32 -arch x86

    (running ant)
    run-umlgraph-with-set-javadoc:
    [javadoc] Generating Javadoc
    [javadoc] Javadoc execution
    [javadoc] javadoc: error - Cannot find doclet class UmlGraph
    [javadoc] 1 error

    It seem it not found the UmlGraph class but i've the
    UmlGraph.jar class in the classpath

     
  • Antti Hakala

    Antti Hakala - 2006-07-23

    Logged In: YES
    user_id=1293256

    Yeah, if you use java 1.4.x, you need to use older UMLGraph
    (see UMLGraph homepage) and select the UMLGraph version in
    LightUML preference pages. The latter because the doclet
    name was changed at some stage.

     
  • Sami Nieminen

    Sami Nieminen - 2006-07-24

    Logged In: YES
    user_id=1560801

    This same error message also occurs in case the older
    version of UMLGraph is in use and the user enables
    attributes that are not supported by that version (e.g.
    -inferdep). It would be good if selection of those
    non-supported attributes was disabled when the older
    UMLGraph version is selected.

     
  • Carsten Beck

    Carsten Beck - 2007-10-08

    Logged In: YES
    user_id=921612
    Originator: NO

    hello,

    i seem to have encountered the same problem. i've already heeded the advice from this thread regarding lightuml preferences in eclipse.

    my installation:
    win xp sp2
    eclipse: 3.3.1 M20070921-1145 using jre 1.5.0_13
    graphviz: 2.14.1
    lightuml: 1.2.7
    umlgraph: 4.9

    the error is triggered by the following lines of the build.xml file:

    - <antcall target="run-umlgraph-with-set-javadoc" />
    - <javadoc
    executable="${javadoc-executable-path}"
    docletpath="${umlgraph-jar-path}"
    access="${javadoc-access-level}"
    useexternalfile="yes"
    additionalparam="${umlgraph-extra-param} "
    failonerror="true">

    an excerpt of the eclipse error log is enclosed at the end of this message.
    has anyone run into this problem in a similar environment ?

    best regards and thanks in advance,

    carsten

    ----------- log excerpt - BEGIN ------------------
    !ENTRY org.lightuml.core 4 0 2007-10-08 17:36:44.468
    !MESSAGE E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:112: The following error occurred while executing this line:
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    !STACK 1
    org.eclipse.core.runtime.CoreException: E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:112: The following error occurred while executing this line:
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:451)
    [...]
    --- Nested Exception ---
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java:2077)
    [...]
    !SUBENTRY 1 org.eclipse.ant.core 4 1 2007-10-08 17:36:44.468
    !MESSAGE E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:112: The following error occurred while executing this line:
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    !STACK 0
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:112: The following error occurred while executing this line:
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
    [...]
    --- Nested Exception ---
    E:\appdata\eclipse\workspace\.metadata\.plugins\org.lightuml.core\build.xml:70: Javadoc returned 1
    at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java:2077)
    [...]
    ----------- log excerpt - END ------------------

     
  • Carsten Beck

    Carsten Beck - 2007-10-08

    Logged In: YES
    user_id=921612
    Originator: NO

    hello,

    regarding my previous post:
    i erroneously used umlgraph 4.9 together with j2se 5; however, the situation does not change if i revert to umlgraph 4.8.

    best regards,

    carsten

     
  • Antti Hakala

    Antti Hakala - 2007-11-03

    Logged In: YES
    user_id=1293256
    Originator: NO

    Ok, I tried LightUML 1.2.7 with Eclipse 3.3.0, UMLGraph-4.9, and Java 1.6.0_03 (on Linux).

    The problem seems to be when ant uses external file for javadoc options, javadoc complains "Illegal package name". So it seems there's some incompatibility between ant and javadoc. You can go around this by disabling the useexternalfile-option for javadoc (set useexternalfile to 'no' in workspace/.metadata/.plugins/org.lightuml.core/build.xml), but i think big projects with lots of source files need to use external file.

    I simply won't go deeper into the source of this problem because I think the whole combo of ant + javadoc + (any doclet), or actually just javadoc with anything, is a bad one.

    If somebody wants to make a bug fix, let me know. Cheers.

     
  • Thomas Kappler

    Thomas Kappler - 2007-11-28

    Logged In: YES
    user_id=1947390
    Originator: NO

    Hi, I can confirm that the problem is the useexternalfile option. Setting it to "no" lets LightUML run flawlessly. That's on Linux, Java 5, UmlGraph 4.8, LightUML 1.2.7, Eclipse 3.3.

     
  • popalka

    popalka - 2008-02-27

    Logged In: YES
    user_id=1865419
    Originator: NO

    Hi, I cannot solve problem simply by set useexternalfile="no" in build.xml.
    My enviroment Windows XP SP2, LightUML 1.2.7 with Eclipse 3.3.0, UMLGraph-5.0, Java
    1.6.0_03.

    If I set javadoc executable path in preferences of LightUML I get error in line 70 of build.xml
    If I set no javadoc executable path I get error in line 50 of build.xml

    I try Java 1.5.0_08. Try add UmlGraph.jar to classpathes. TRy to set useexternalfile="no" in 2 places of build.xml.
    I try about 10 combination of java, option useexternalfile, javadoc executable path.
    It not help me. Can anybody help?

     
  • popalka

    popalka - 2008-02-27

    Logged In: YES
    user_id=1865419
    Originator: NO

    heh, i fix my previous problem by using UMLGraph-4.8
    (info from official site of UMLGraph: Version 5.0 2007-11-29
    All code now lives under org.umlgraph. This change requires corresponding modifications to the UMLGraph callers. )

     
  • Muzietto

    Muzietto - 2008-09-01

    Logged In: YES
    user_id=1591053
    Originator: NO

    Excuse me, Popalka

    Still got into the same problem, using UMLGraph 5.1

    I have changed the doclet-name in the following places:
    - 1 time inside the file graph.ini
    - 4 times in the build.xml file at the instructions beginning with <condition property="umlgraph-output-param-name" (I did this after the first change didn't help)

    but the "javadoc returns 1" message remains. Also tried the externalFiles=no tip, but no relief.

    Could you please post here an example of your following files?
    - graph.ini
    - build.xml
    I could try to go from there.

    Is there a way to have a verbose output, so that I can see what exactly is going wrong? I tried to put verbose="yes" in the <antcall> and in the <javadoc> tags with no avail.

    Thanks in advance,
    Marco Faustinelli - Italy (marco_faustinelli@yahoo.com)

     
  • MartinL

    MartinL - 2009-01-28

    I figured the following with UMLGraph 5.2: the package name did indeed change.

    So I did the following:
    - Modified the graph.ini file to replace the value of 'umlgraph-doclet-name'

    umlgraph-doclet-name=org.umlgraph.doclet.UmlGraph

    - Modified the build.xml (in C:\Documents and Settings\&lt;username>\workspace\.metadata\.plugins\org.lightuml.core)

    useexternalfile="no" in two locations on the javadoc tasks as it seems Ant creates a malformed argument file for javadoc

    added to 'java-to-dot' target the following excerpt which defines to missing variables due to changing the doclet name:

    <condition property="umlgraph-output-param-name" value="-d">
    <equals arg1="${umlgraph-doclet-name}" arg2="org.umlgraph.doclet.UmlGraph"/>
    </condition>
    <condition property="umlgraph-output-param-value" value="${statelocation}/graph">
    <equals arg1="${umlgraph-doclet-name}" arg2="org.umlgraph.doclet.UmlGraph"/>
    </condition>

     
  • fcasarian

    fcasarian - 2010-05-16

    martin2leduc's modifications worked for me, thanks to him !

    Just a precision, take care when adding the excerpt to 'java-to-dot' : add it before the existing informations contained by the 'java-to-dot' element, not after.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.