[
http://issues.apache.org/jira/browse/DERBY-2092?page=comments#action_12450532 ]
Andrew McIntyre commented on DERBY-2092:
----------------------------------------
There's another option as well: use svn:externals to include a specific
revision/location in the local checkout. This has the benefit of not actually
making a copy into our repo, just including by reference.
This is how the 10.1 jars are included for upgrade testing, for example. Do
'svn pg svn:externals tools/testing' to see the format. The external resource
can be pegged to a specific revision by adding -r{rev} in between the target
location and the source location.
> Add JDBC classes into Javadoc for Derby's published api
> -------------------------------------------------------
>
> Key: DERBY-2092
> URL: http://issues.apache.org/jira/browse/DERBY-2092
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> The javadoc for java.sql and javax.sql for JDBC 3 can be added into derby's
> published api javadoc fairly easily using the source files from Harmony.
> I created a folder at the top level called: java/j2se
> I then fetched the JDBC classes from Harmony
> cd java/j2se
> svn co
> http://svn.apache.org/repos/asf/incubator/harmony/enhanced/classlib/trunk/modules/sql/src/main/java/java
> svn co
> http://svn.apache.org/repos/asf/incubator/harmony/enhanced/classlib/trunk/modules/sql/src/main/java/javax
> I then added the list of java.sql and javax.sql files to the
> publishedapi_jdbc3.ant (excluding RowSet files)
> and added in the published api target this element:
> <fileset dir="${derby.j2se.src.dir}"
> includesfile="${javadoc.inclusions}"/>
> Example of the output at
> http://people.apache.org/~djd/derby/publishedapi/
--
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
