[
https://issues.apache.org/jira/browse/DERBY-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394865#comment-15394865
]
Bryan Pendleton commented on DERBY-6899:
----------------------------------------
Alternatively, perhaps we could at least have the docs build.xml file check
to see that the right classes are in the classpath, and stop immediately
if the classpath does not seem to be set correctly.
We could perhaps use something similar to this, from the code's build.xml:
{code}
<!-- Make sure compiler level is Java 6 level or higher -->
<target name="checkCompilerLevel">
<available property="compilerAtCorrectLevel" classname="java.sql.SQLType"/>
<fail unless="compilerAtCorrectLevel" message="Compiler level must be Java
8 or later."/>
</target>
{code}
> Improve docs build.xml to remove CLASSPATH requirement
> ------------------------------------------------------
>
> Key: DERBY-6899
> URL: https://issues.apache.org/jira/browse/DERBY-6899
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Bryan Pendleton
>
> As described in DERBY-6898, the docs build currently requires that
> you set a custom CLASSPATH when running Ant, otherwise you get
> build errors.
> We don't have this requirement with the main code build, so I wonder
> if we can improve the docs build.xml so that we don't need to remember
> to set a custom CLASSPATH prior to runing the docs build.
> See the derby-dev email thread from July, 2016, entitled "Need dita help"
> for more discussion about this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
