[jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

["Andrew McIntyre (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12359065 ] 

Andrew McIntyre commented on DERBY-587:
---------------------------------------

David - it looks like you missed the derbydocs_exclusions.ant file in the javadoc fix patch. I've checked it in with revision 350292.

It's unfortunate that it's now necessary to copy basically the entire source tree, almost 1700 files, to generate the javadoc. But, since javadoc itself doesn't have the ability to exclude a list of files, only packages, I don't know what else to do either. If anyone knows a way to get Ant to generate a list of files (like the find command) that we could then filter, let me know.

> Providing JDBC 4.0 support for derby
> ------------------------------------
>
>          Key: DERBY-587
>          URL: http://issues.apache.org/jira/browse/DERBY-587
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Versions: 10.2.0.0
>     Reporter: V.Narayanan
>     Assignee: V.Narayanan
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: bug587_javadoc.diff, jdbc4.0.sxw, jdbc4.diff
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: [jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

[Bryan Pendleton <bp...@amberpoint.com>]

>  It would be  
> interesting if you can get the "derbydocs" javadoc build going using  
> multiple nested filesets, excluding the classes listed in tools/ 
> javadoc/derbydocs_excludes.ant, and avoid the need to copy the entire  
> source tree to a new directory before generating the javadoc.

I'm possibly looking at this too simplistically, but I just tried
this simple change (attached) and it seemed to generate the correct javadoc
for me. In addition to tweaking the build.xml to pass the java classes
as nested filesets, rather than by making a source tree copy, I also
had to add a few more patterns to derbydocs_excludes.ant, to tell javadoc
to keep its hands off of build.xml files, properties files, etc.

Of course, I don't have a lot of experience generating Derby javadoc
so please try it and tell me whether you think it actually *does*
generate the correct javadoc.

thanks,

bryan

Re: [jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

[Andrew McIntyre <mc...@gmail.com>]

On Dec 1, 2005, at 11:08 AM, Bryan Pendleton wrote:

> > If anyone knows a way to get Ant to generate a list of files
> > (like the find command) that we could then filter, let me know.
>
> I'm always up for puttering around with Ant scripts. Between
> <fileset>, <patternset>, and <selector>, there's a lot of power
> there. Maybe you could send me some more details about what you'd
> exactly like Ant to be able to do, and I could fiddle with it for a  
> while?

Javadoc accepts an @{file} argument for a file which contains a list  
of the files to be javadoc'd. Ant, unfortunately, doesn't include a  
facility for generating such a list of files.

Good news, though. It appears that recent versions of Ant will now  
generate the file list for you from <fileset> elements. It would be  
interesting if you can get the "derbydocs" javadoc build going using  
multiple nested filesets, excluding the classes listed in tools/ 
javadoc/derbydocs_excludes.ant, and avoid the need to copy the entire  
source tree to a new directory before generating the javadoc. And if  
you get that working, then it should be simple to get the  
publishedapi target to work in a similar fashion.

Let me know if you're interested in working on that, otherwise I'll  
take a look.

thanks,
andrew

Re: [jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

[Bryan Pendleton <bp...@amberpoint.com>]

 > If anyone knows a way to get Ant to generate a list of files
 > (like the find command) that we could then filter, let me know.

I'm always up for puttering around with Ant scripts. Between
<fileset>, <patternset>, and <selector>, there's a lot of power
there. Maybe you could send me some more details about what you'd
exactly like Ant to be able to do, and I could fiddle with it for a while?

thanks,

bryan