[
https://issues.apache.org/jira/browse/DERBY-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138436#comment-13138436
]
Rick Hillegas commented on DERBY-5485:
--------------------------------------
The javadoc problem with IBM JDK 7 goes away if I remove
${java16compile.classpath} from the classpath specification for the derbydocs
target. When I remove that extra bit of classpath, the generated javadoc still
looks correct to me.
> Simplify PropertySetter so that it is less brittle and easier to maintain.
> --------------------------------------------------------------------------
>
> Key: DERBY-5485
> URL: https://issues.apache.org/jira/browse/DERBY-5485
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
>
> The PropertySetter task sets up classpath variables so that the build can
> take advantage of JVM-specific class libraries. Using those libraries makes
> it possible for the compiler to flag code which is supposed to run on less
> capable platforms but which calls methods from later JVMs. This is a very
> tricky problem and we seem to have reached consensus that it requires too
> much effort to make PropertySetter run correctly in all of the build
> environments which Derby developers use. I will attach a proposal for how to
> simplify PropertySetter so that it requires less effort to maintain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
