Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157685 - classpathref attribute in javadoc target fails
Summary: classpathref attribute in javadoc target fails
Alias: None
Product: Fedora
Classification: Fedora
Component: classpathx-mail
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Vadim Nasardinov
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-13 18:43 UTC by Thomas Fitzsimmons
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-11-11 16:25:56 UTC

Attachments (Terms of Use)

Description Thomas Fitzsimmons 2005-05-13 18:43:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Firefox/1.0.2 Fedora/1.0.2-3

Description of problem:
In classpathx-mail we have workaround patches for build.xml:

--- ../mail-20050512.orig/build.xml	2005-05-12 14:26:00.000000000 -0400
+++ build.xml	2005-05-12 14:29:01.000000000 -0400
@@ -208,8 +211,7 @@
   <target name='javadoc' depends='init' description='Build the JavaDoc API documentation'>
     <mkdir dir='${doc}'/>
     <javadoc destdir='${doc}' use='true' author='true'
-      windowtitle='GNU JavaMail API documentation'
-      classpathref='nntp.classpath'>
+      windowtitle='GNU JavaMail API documentation'>
       <doctitle><![CDATA[<h3>GNU JavaMail</h3>]]></doctitle>
       <bottom><![CDATA[&copy;]]> Copyright 2003, 2004
             The Free Software Foundation, All rights reserved</bottom>

When I remove these patches, the ant build fails with:

/home/fitzsim/rpmbuild/BUILD/mail-20050512/inetlib-20050512/build.xml:159: Reference provider.classpath not found.
   at (/usr/lib/
   at, (/usr/lib/
   at, (/usr/lib/
   at (/usr/lib/
   at, boolean) (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/
   at[], java.util.Properties, java.lang.ClassLoader) (/usr/lib/
   at[]) (/usr/lib/
   at[]) (/usr/lib/
   at (/usr/lib/
   at (/usr/lib/

We should fix FC4 ant's support for classpathref.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. remove the docbuild patches from classpathx-mail.spec
2. build the classpathx-mail rpm

Actual Results:  doc target fails

Expected Results:  doc target should succeed

Additional info:

Comment 2 Vadim Nasardinov 2005-11-11 16:25:56 UTC
I'm changing the "Component" field from "ant" to "classpathx-mail".
This is not a bug in Ant -- it's a bug in Classpathx Mail's and
Classpath Inetlib's build.xml files.  Ant handles the "classpathref"
attribute of the "javadoc" task just fine.

The problem is that the versions of GNU Mail and GNU Inetlib that we
ship in this RPM both reference the non-existent path id
"nntp.classpath".  This used to be defined in early versions of these
build.xml files, but not any longer.

In the case of Inetlib, Chris fixed the bug in CVS over a year ago (on

In the case of GNU Mail, the bug is still there, so I filed a bug
report (see comment #1 above).

I updated classpath-inetlib-docbuild.patch and
classpathx-mail-docbuild.patch to fix the issue in a slightly more
correct way:

... and rebuilt the RPM as classpathx-mail-1_0-4jpp_3fc.

As far as I can tell, the (re-)generated Javadoc hasn't changed as a
result of this fix.  The only change that I observe by diffing the
pre- and post-fix /usr/share/javadoc/javamail-1.3.1/ trees is in files
named foo/bar/Baz-uses.html, for instance:


Even there, the diff seems to be due to a reordering of package names
on the page.  The actual content is the same.  This may be due to
gjdoc's brokenness:

I'm closing this ticket.

Note You need to log in before you can comment on or make changes to this bug.