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

Rick Hillegas updated DERBY-4845:
---------------------------------

    Attachment: derby-4845-02-aa-flipUtilsAndTypes.diff

Attaching derby-4845-02-aa-flipUtilsAndTypes.diff. This patch fixes a build 
dependency problem which surfaced when I sync'd with the head of the trunk. 
Committed at subversion revision 1031174.

I think that the problem was caused by some submission which made the 
compilation of ...iapi.util start compiling what's in iapi.types. That latter 
directory has a special build target which compiles SqlXmlUtil with a special 
classpath which includes xercesImpl.jar. You can't just compile the contents of 
iapi.types with the ordinary jdk1.4 classpath.

The solution was to flip the order in which we compile ...iapi.util and 
...iapi.types. Now we compile ...iapi.types first.

Hopefully this patch doesn't destabilize someone else's build.

Touches the following file:

M      java/engine/org/apache/derby/iapi/build.xml


> 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-4845-01-aa-removeParserPrep, 
> derby-4845-02-aa-flipUtilsAndTypes.diff, 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.

Reply via email to