https://issues.apache.org/bugzilla/show_bug.cgi?id=46649

           Summary: Javadoc task does nothing when given 3+ nested link
                    elements
           Product: Ant
           Version: 1.7.0
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
        AssignedTo: [email protected]
        ReportedBy: [email protected]


When using the <javadoc> task in a target, I can get it to link to external
Javadoc API by providing a nested <link> element, even two, and it works fine.
The moment a third <link> element is added, the only output I get is:

             docs:
              [javadoc] Generating Javadoc
              [javadoc] Javadoc execution

             BUILD SUCCESSFUL
             Total time: 0 seconds

No packages are loaded or parsed, and no output is generated. It doesn't seem
to matter what URL's are, or what order they're in. For reference, here are
several that I've been using:

            <link href="http://java.sun.com/j2se/1.5.0/docs/api/"/>
            <link href="http://java.sun.com/javaee/5/docs/api/"/>
            <link href="http://bouncycastle.org/docs/docs1.5/"/>
            <link href="http://bouncycastle.org/docs/mdocs1.5/"/>
            <link href="http://junit.org/junit/javadoc/4.5/"/>

It wouldn't seem to be a timeout issue, since when I'm on a slow connection,
the javadoc tasks hangs until it can download the "package-list" file from each
URL.

I've tried increasing the memory with the 'maxmemory' attribute, to no avail.
My next step is to try using offline saved files for each link. Perhaps that
will work, but even if it does, that's a serious PITA workaround for something
that should just work, especially since each file has to be named
"package-list" and be in a different directory.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to