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] Issue Comment Edited: (DERBY-3986) Stop dropping build artifacts in the subversion-controlled source tree
Date Thu, 23 Sep 2010 17:46:33 GMT

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

Rick Hillegas edited comment on DERBY-3986 at 9/23/10 1:44 PM:
---------------------------------------------------------------

Hi Kathey and Myrna,

Did you perform the following steps in this order when you sync'd up to the changes introduced
by this patch:

ant clobber
svn update

That is the order of operations which is expected to work. The reverse order will leave a
lot of cruft in the source tree. The cruft will confuse the build and produce a lot of noise
for "svn status". So just to repeat, the following sequence of steps will result in an experience
which is consistent with the symptoms you are seeing:

svn update
ant clobber

If your environments are still broken, the following may help:

1) Throw away your subversion client and re-initialize it from scratch. This is the technique
used by Kristian and Knut to unwedge the automated builds.

2) Or, set your client to before revision 999928, then do "ant clobber", then do "svn update"

Thanks,
-Rick


      was (Author: rhillegas):
    Hi Kathey and Myrna,

Did you perform the following steps in this order when you sync'd up to the changes introduced
by this patch:

ant clobber
svn update

That is the order of operations which is expected to work. The reverse order will leave a
lot of cruft in the source tree. The cruft will confuse the build and produce a lot of noise
for "svn status". So just to repeat, the following sequence of steps will result in an experience
which is consistent with the symptoms you are seeing:

svn update
ant clobber

If your environments are still broken, the following may help:

1) Throw away your subversion client and re-initialize it from scratch. This is the technique
used by Kristian and Knut to unwedge the automated builds.

2) Set your client to before revision 999928, then do "ant clobber", then do "svn update"

Thanks,
-Rick

  
> 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: 10.5.1.1
>            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,
mk-sanity-dir.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
space:
> 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.


Mime
View raw message