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.
This is a TCR from the final review of the VCS Cache (tracked by issue 43637). The new cache implementation imposes additional constraints on the textual data being stored into it that should be documented and tested. The reviewers believe that this is important because not doing so could lead to regressions as the original cache implementation did not have these constraints. The new VCS Cache should not be integrated until this issue gets resolved.
Well, there are no additional constraints that were not in the original implementation. But I agree that having tests verifying the correct behavior when various data are provided would be good.
Mmrtine could you please link use case scripts, please. I'll code them.
Created attachment 19257 [details] Test of storage of data provided by VCS commands.
Checking in vcscore/src/org/netbeans/modules/vcscore/VcsFileSystem.java; /cvs/vcscore/src/org/netbeans/modules/vcscore/VcsFileSystem.java,v <-- VcsFileSystem.java new revision: 1.288.2.36; previous revision: 1.288.2.35 done Processing log script arguments... More commits to come... Checking in vcscore/src/org/netbeans/modules/vcscore/turbo/TurboUtil.java; /cvs/vcscore/src/org/netbeans/modules/vcscore/turbo/Attic/TurboUtil.java,v <-- TurboUtil.java new revision: 1.8.2.38; previous revision: 1.8.2.37 done Processing log script arguments... More commits to come... Checking in vcscore/test/unit/src/org/netbeans/modules/vcscore/turbo/TurboUtilTest.java; /cvs/vcscore/test/unit/src/org/netbeans/modules/vcscore/turbo/Attic/TurboUtilTest.java,v <-- TurboUtilTest.java new revision: 1.1.2.2; previous revision: 1.1.2.1 done Checking in vcscore/test/unit/src/org/netbeans/modules/vcscore/turbo/registration.xml; /cvs/vcscore/test/unit/src/org/netbeans/modules/vcscore/turbo/Attic/registration.xml,v <-- registration.xml new revision: 1.1.2.2; previous revision: 1.1.2.1 FIXED the script is implemented and passed. It'll probably require xtest hacking to make it run from build.xml. It's cross module test. XMLFS registration.xml static relative paths "../../../.." are too context sensistive,
Please, can you verify this issue? Thanks.
Verified.