db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4845) Improve the dependency tracking for our build targets
Date Sat, 16 Oct 2010 18:58:22 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-4845:
--------------------------------------

    Attachment: tools-i18n.diff

Here's a patch for the issue with tools/i18n/LocalizedResource.java.

M       java/tools/build.xml

The classes in impl/tools depend on the classes in iapi/tools, but there are no dependencies
the other way around. Therefore, turn around the order of the targets and build iapi before
impl. This change ensures that LocalizedResource.java is always compiled against the JSR-169
libraries, so it will now fail to compile both in full builds and in incremental builds.

M       java/tools/org/apache/derby/iapi/tools/i18n/LocalizedResource.java

Call getObject() instead of getBigDecimal() when retrieving the value of a DECIMAL column.
Since getObject() is part of JSR-169, this will make the class compilable again. getObject()
returns a java.math.BigDecimal, so there should be no change for the embedded driver and the
client driver. The JSR-169 driver throws an exception when getObject() is called on a DECIMAL
column, but LocalizedResource already does introspection to find out if it's safe to retrieve
BigDecimal values. On JSR-169 it'll fall back to getString() as it did before.

> 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, tools-i18n.diff
>
>
> 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.


Mime
View raw message