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.
| Summary: | [65cat] Local history is cleaned every start up | ||
|---|---|---|---|
| Product: | versioncontrol | Reporter: | Michel Graciano <hmichel> |
| Component: | Localhistory | Assignee: | issues@versioncontrol <issues> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | misterm, mmirilovic, tstupka |
| Priority: | P1 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Michel Graciano
2008-10-23 17:12:09 UTC
Product Version: NetBeans IDE 6.5 RC1 (Build 200810171318) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Linux version 2.6.24-21-generic running on i386; ISO-8859-1; pt_BR (nb) Userdir: /home/hmichel/.netbeans/6.5rc1 Can't reproduce. Could you please provide further details? Project type? Do you use any other version control? Ok, try to set local history to 99 days and restart your IDE. I changed my local history to 99 a long time ago, and any problem until now. Now, I tested with 120 and 10 days and it is working now. A mystic number 99? BTW, I tested with 666 and works to. :P BTW, if you need any additional info, just let me know. Reproduced for 99 days only. Tomas, could you please have a look at it? Lowering priority - P2. This can be fixed into the patch 1 - if all agree. I don't agree, it should be fixed for release. In my point of view, it causes data loss (P1) and, users like me who uses local history a lot will not like this idea. For me is not necessary a local history if I can't trust in it. It is the same thing I run a refactor to guarantee the quality of a code change and can't trust on it, why we need this feature? I agree that just a few people will face it, but I can reproduce for some numbers, so, I really wish that this fixed for FCS. fixed in trunk e2a3cb674f22 I have reviewed the fix, it seems safe to me. Settings class now returns long instead of int type, preventing the overflow. This should be enough because long values are already used elsewhere, particularly in the cleanup code. What should I to do to make it available for 6.5 RC2? hmichel, we are on the way to fix this one into RC2. The only pending step is to wait some time for objection and test the fix in trunk. It would be really great if you will help us with second part : - download the build with integrated fix on (it hasn't been propagated yet, so wait until tomorrow please): http://deadlock.netbeans.org/hudson/job/trunk/lastSuccessfulBuild/artifact/nbbuild/dist/zip/ - test the build & verify it So, we can integrate it into release65 clone (be available in RC2). Thanks in advance, Marian merged in releas65 eb09666c3cb0 v. 20081027043244 v. on RC2 *** Issue 157253 has been marked as a duplicate of this issue. *** |