Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325354

Summary:	javadoc fails to generate correct documentation in hudson builds
Product:	Community	Reporter:	Steve Powell <zteve.powell>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	glyn.normington
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Steve Powell

2010-09-15 10:14:15 EDT

javadoc with -link options sometimes requires to access package-lists from external URLs.  On the slave machines these references always result in a warning -- and a sizeable delay (about five mins for each warning) -- and then runs to completion -- BUT the output generated then lacks links to external packages (e.g. to http://java.sun.com/javase/6/docs/api packages).

Here is an example of the failure, taken from virgo.osgi-test-stubs.snapshot (build #36) with -verbose option on ant:

----8<------------
[javadoc.links] Generating Javadoc
[javadoc.links] Executing '/opt/public/common/sun-jdk1.6.0_21_x64/bin/javadoc' with arguments:
[javadoc.links] '@/tmp/javadocOptions2867206154035552073'
[javadoc.links] '-J-Xmx128M'
[javadoc.links] '@/tmp/javadoc1508323835858264056'
[javadoc.links] 
[javadoc.links] The ' characters around the executable and arguments are
[javadoc.links] not part of the command.
[javadoc.links] Javadoc execution
[javadoc.links] Loading source files for package org.eclipse.virgo.teststubs.osgi.framework...
[javadoc.links] Loading source files for package org.eclipse.virgo.teststubs.osgi.service.cm...
[javadoc.links] Loading source files for package org.eclipse.virgo.teststubs.osgi.service.event...
[javadoc.links] Loading source files for package org.eclipse.virgo.teststubs.osgi.support...
[javadoc.links] Constructing Javadoc information...
(*)[javadoc.links] javadoc: warning - Error fetching URL: http://java.sun.com/javase/6/docs/api/package-list
(*)[javadoc.links] javadoc: warning - Error fetching URL: http://www.osgi.org/javadoc/r4v41/package-list
(*)[javadoc.links] javadoc: warning - Error fetching URL: http://junit.org/junit/javadoc/4.5/package-list
[javadoc.links] Standard Doclet version 1.6.0_21
[javadoc.links] Building tree for all the packages and classes...
------------------

There are large pauses at lines marked (*) and the generated javadoc lacks links to the packages in these lists.

Comment 1 Steve Powell

2010-10-14 06:25:27 EDT

This problem still exists; even after 'solving' the proxy ivy resolution issues on the virgo jobs.  It is possibly a proxy setting, but may simply be that the javadoc features don't expect to be denied read-only access to public information java sites.

I'd be grateful for some advice from anyone who understands proxies and javadoc generation to help out here.

Comment 2 Steve Powell

2011-01-19 10:13:45 EST

This is still a problem, causing incorrect javadoc generation on any hudson build.

It appears to be an issue which could be alleviated by the proxies allowing access to the java language public sites used by javadoc.

Comment 3 Eclipse Webmaster

2011-01-24 15:02:20 EST

The proxy isn't 'blocking' any sites(that I'm aware of).  I can access the urls you've given via a wget in my test build.

Can you help craft a 'simple' javadoc job so we can establish if it's the javadoc process or hudson that's failing?

-M.

Comment 4 Steve Powell

2011-01-25 04:51:27 EST

(In reply to comment #3)

I can't create a job.

You create me a job and I'll set one up for you.  It'll be a cut-down osgi-test-stubs job with much fewer ant targets.

Comment 5 Eclipse Genie

2014-10-14 17:39:52 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Eclipse Webmaster

2014-10-15 16:06:55 EDT

I'm going to close this as 'worksforme'.

-M.