[ http://issues.apache.org/jira/browse/DERBY-1079?page=all ]
Rick Hillegas reassigned DERBY-1079:
Assign To: Rick Hillegas
Build javadoc under jdk 1.6
Key: DERBY-1079
URL:
On 4/12/06, Rick Hillegas (JIRA) derby-dev@db.apache.org wrote:
[ http://issues.apache.org/jira/browse/DERBY-1079?page=all ]
Rick Hillegas reassigned DERBY-1079:
Assign To: Rick Hillegas
Thought about this the other day. One way to go would be
Thanks, Andrew. I will play around with this. I may try something more
elaborate too:
o Use the jdk16 javadoc if ant.properties points to a 1.6 installation
o Don't exclude the jdbc40 classes from the javadoc at all. If
ant.properties doesn't point at a 1.6 intallation, then they won't be
On 4/12/06, Rick Hillegas [EMAIL PROTECTED] wrote:
o Use the jdk16 javadoc if ant.properties points to a 1.6 installation
Yep, I think that's what I was suggesting. :-)
o Don't exclude the jdbc40 classes from the javadoc at all. If
ant.properties doesn't point at a 1.6 intallation, then they
Andrew McIntyre wrote:
ships in the release.
For the engine docs, I'd suggest a similar setup. If you don't exclude
the jdbc40 classes, I'm pretty sure that javadoc will still find them
in the source and complain if it can't find the corresponding compiled
classfile.
Ah, I think you're
