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.
How to reproduce: 1) Create CVS structure like this: - root |- dir | ` subfile [uptodate] '- file [uptodate] 2) Try "Force" commit on file -> All OK 3) Try "Force" commit on subfile -> ERROR - File is not commited - In the "Output Window - Versioning" there is message: Nothing known about file subfile.
There is missing a part of the file path. It's a bug in CvsCommit class.
Hm, in such case it's a regression, because this works fine in NetBeans 3.4.
This is also an issue with Win2k. Using NB3.5Dev and the CVS-external Command Line system, if I "add" a file and then "commit" it, I get a "nothing known about file xxxx" CVS error. The little bit of information I've been able to find about this error suggests that cvs should be run from within the same directory as the file being committed. In Win2k's case: For: /WorkingDir/Adir/Bdir/FileToCommit /WorkingDir/Adir/Bdir: /cygwin/bin/cvs.exe commit FileToCommit Everything works well under the built-in CVS client.
Scheduled for 4.0. Workaround: Use JavaCVS for this.
I run in the same problem - but waiting for 4.0 is not a result for me. javacvs does not work with a remote cvs- repository (see issue #33158) and generic cvs ignores the package structure. Is it a problem with the command-template? COMMIT_CMD changes the directory with ${RUNCDM} but (eg.) DIFF_TEXT with ${RUNCDW}. DIFF_TEXT changes the directory on the right way but COMMIT_CMD stay on root. Hm, with changed exec-template to "${RUNCDW} ..." I get the same root-directory. COMMIT_CMD ignores ${RUNCDW} or can't resolve the right path. Or COMMIT_TEMPLATE_GETTER does not resolve the right package for the file. Hm, however - IMHO it should be fixed for 3.5. regards, josh.
Seems like a DEADLOCK for Josh :-( Could we realy try to fix those 2 issues, please? Icreasing to P2
The are probably some variables badly set. I guess the bug is in CvsCommit.java in cvs-profile module.
The paths, that are given to the forced commit are corrected in the main trunk: /cvs/vcsgeneric/profiles/cvsprofiles/src/org/netbeans/modules/vcs/profiles/cvsprofiles/commands/CvsCommit.java,v <-- CvsCommit.java new revision: 1.12; previous revision: 1.11 So [Up-to-date] files can be committed when forced. But there's one remaining problem, which is hard to fix: - when you have .java and .form file and only .java file is modified (e.g. TestFrame [Locally Modified, Up-to-date; 1.1]) and you want to preserve the same revision for both after commit (1.2) this will not work, because even when you select "Force to Commit", only the modified .java file will be committed.
Issue #33225 submitted for the remaining problem. Also I'm increasing this ro P1, because the Force Commit option is unusable.
Created attachment 10144 [details] The contextual diff.
Created attachment 10145 [details] The binary patch, that fix this problem. Put into <NB-install>/modules/patches/org-netbeans-modules-vcs-profiles-cvsprofiles/ folder.
Okay, it seems working. I could conveniently force commit of any files except the multidataobject case mentioned above. Applied Patch27997.jar patch fixed the problem. Tested in NetBeans 3.5 build #2003222350 with JDK 1.4.0 build #02 on Windows 2000.
Reviewed without objections.
approved for 3.5
Thanks for the verification, review and approval. The problem is fixed in release35 branch: /shared/data/helm/cvs/repository/vcsgeneric/profiles/cvsprofiles/src/org/netbeans/modules/vcs/profiles/cvsprofiles/commands/CvsCommit.java,v <-- CvsCommit.java new revision: 1.9.2.2; previous revision: 1.9.2.1
Thanx for your great job :D
Ok, today I've tested the patch with different packages. It's ok - the patch runs for me. Thank you. greetings, josh.
*** Issue 31798 has been marked as a duplicate of this issue. ***
OK in NB35 #200306022350