[
https://issues.apache.org/jira/browse/DERBY-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4845:
--------------------------------------
Attachment: check-build.ksh
I used the attached script to find out which files were not picked up by an
incremental build. Here's what I found:
* java/tools/org/apache/derby/iapi/tools/i18n/LocalizedResource.java
Modifications to this file are detected by incremental builds, but it will be
compiled using another build target than what's used by full builds. Full
builds will compile against Java 1.4.2 libraries, whereas incremental builds
will compile against the JSR-169 stubs. Incremental builds fail because the
class calls ResultSet.getBigDecimal(int), which is not part of JSR-169.
* java/engine/org/apache/derby/jdbc/EmbedXAResource.java
* java/engine/org/apache/derby/jdbc/JDBC.java
* java/engine/org/apache/derby/iapi/transaction/TransactionControl.java
* java/engine/org/apache/derby/iapi/transaction/TransactionListener.java
* java/engine/org/apache/derby/iapi/security/SecurityUtil.java
* java/drda/org/apache/derby/mbeans/drda/NetworkServerMBean.java
Modifications to these files are not detected by incremental builds.
In addition, none of the files under java/demo/localcal and java/demo/scores
are picked up by incremental builds, but they are not compiled by full builds
either.
> Improve the dependency tracking for our build targets
> -----------------------------------------------------
>
> Key: DERBY-4845
> URL: https://issues.apache.org/jira/browse/DERBY-4845
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Reporter: Rick Hillegas
> Attachments: check-build.ksh
>
>
> Derby is supposed to have an incremental build. That is, if you change a
> file, then the following command should recompile the file:
> ant all
> There are several places in the graph of Derby build targets where this is
> not true. If you change a file in certain packages, a subsequent "ant all"
> won't notice the change. This issue is a place where we can track these bugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
