db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3986) Stop dropping build artifacts in the subversion-controlled source tree
Date Thu, 23 Sep 2010 17:54:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914124#action_12914124

Rick Hillegas commented on DERBY-3986:

Hi Myrna,

Thanks for bringing up this topic. I did edit the release targets and I did verify that the
scripts are being dropped into the bin directories of the release distributions. See the STATE
OF TESTING section of my long comment on 20-Sep-2010 above. The distributions look correct
to me, but this is clearly an area we will have to watch closely when we release 10.7. Thanks.

> Stop dropping build artifacts in the subversion-controlled source tree
> ----------------------------------------------------------------------
>                 Key: DERBY-3986
>                 URL: https://issues.apache.org/jira/browse/DERBY-3986
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: chmod.diff, derby-3986-01-aa-checkCompilerLevel.diff, derby-3986-02-af-sanity-bin-toursdb-storeless-release.diff,
derby-3986-02-ag-sanity-bin-toursdb-storeless-release.diff, derby-3986-02-ah-sanity-bin-toursdb-storeless-release.diff,
> The Derby build drops various artifacts in the source tree. Build artifacts should not
muddy subversion controlled directories but should, instead, go into temporary directories
created by the the build. 
> The following is a (perhaps partial) list of artifacts currently dropped into subversion-controlled
> Sanity directives
> Generated grammars
> The English error messages
> Data type class sizes
> Toursdb
> Temporary class for verifying compiler level

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message