This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 145930 - Bunch of not tracked files in db
Summary: Bunch of not tracked files in db
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-02 14:48 UTC by Alexander Kouznetsov
Modified: 2008-09-26 12:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
hg stat output (152.42 KB, text/plain)
2008-09-02 14:49 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2008-09-02 14:48:33 UTC
When I run hg stat I get several hundreds of not tracked files under db folder. Is it possible to do not show them when
hg stat is executed? I know about -X option, but it is not the best solution, I believe.
Comment 1 Alexander Kouznetsov 2008-09-02 14:49:56 UTC
Created attachment 68876 [details]
hg stat output
Comment 2 Michal Zlamal 2008-09-02 15:36:45 UTC
reassigned to correct component.

Those files should be registered in .hgignore file with filter like:
^db\test\unit\data\db-derby-


Comment 3 Andrei Badea 2008-09-02 23:30:20 UTC
Why are these files in the data directory to begin with? I though the infrastructure for getting a db connection in
tests was supposed to only use the embedded Derby driver. Or are the files just a leftover from the previous solution,
which was starting a Derby server?
Comment 4 David Vancouvering 2008-09-03 00:43:36 UTC
I agree, these files shouldn't be there.  I will make sure that these files aren't being copied any more.
Comment 5 Andrei Badea 2008-09-23 17:21:09 UTC
Reporter: do you still reproduce this issue starting from a clean checkout (or at least from an empty result of "hg
stat")? I can't, nor can I see any code in the db module expanding Derby. If you can, please attach steps to reproduce.
Comment 6 David Vancouvering 2008-09-24 19:53:19 UTC
We were not able to get to these issues before code freeze - changing target
milestone to 'future'
Comment 7 Alexander Kouznetsov 2008-09-26 12:39:01 UTC
The issue seems to be fixed already.
Comment 8 Alexander Kouznetsov 2008-09-26 12:39:20 UTC
verified