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.
Development build #200302190100 of NetBeans 3.5 Solaris 5.8 with build #20 of JDK 1.4.1 ClearCase profile from 03/02/20 Description: ============ "Versioning Explorer" popup menu does not retrieve revisions of a file but throws NPE through request processor instead. This is very significant bug in the profile and should be resolved immediately. Steps to reproduce: =================== 1. Mount ClearCase VOB tag as VCS filesystem. 2. Invoke "Versioning Explorer" on some ClearCase file element. 3. Below attached exception is thrown and its node says "Please wait..." forever.
Created attachment 9117 [details] NullPointerException I am referring to.
The NPE is already fixed (from Feb 20).
Yes, you are right Martin. The exception is not thrown any longer and "Please wait..." status is not present too. However, I am convinced we can't release without functioning versioning explorer.
Peter, the point of this issue is not the NPE, but the fact, that Versioning Explorer does not show any revisions for ClearCase. So there are several options how to resolve this issue: - you resolve it as wontfix and QA may verify it (considering that there is a tight schedule) - if QA will not verify this, we may ask for a waiver for S1S 5.0 - if we will not get a waiver, we would have to fix it. But the final decission is on you, whether you're going to implement this or not.
No Martin, according to valid waiving process P1 issues must be fixed. Only P2 bugs may be waived.
> according to valid waiving process P1 issues must be fixed. > Only P2 bugs may be waived. So in this case, Peter do you think, that you will be able to fix that? Do you need some more information about the problem?
A question about testing. What are the main use cases for the version explorer?
Well, versioning explorer is at least supposed to provide tree of all revisions and branches on files contained in data node where the action was invoked. Then it should offer "Diff" action on a revisions that will show the diff against the latest revision. Nice to have would be some branching support.
Hmm...this functionality is available through the version tree function. If there is an alternative way to get this functionality it helps put an outer bound on how much effort to put into this.
I see no way of making this work in Nevada. The implementation of VCS core functionality for this depends on CVS-specific functionality. In particular the generic VersioningDataNode sets up node children as follows: super(data, new NumDotRevisionChildren(null)); This class makes an assumption that all VCS systems have revision strings of the form num.num.num etc. This is not true for clearcase. In particular it fails to pass the accept() test because there are no dots to be counted by NumDotRevisionItem.numDots(revisionString). I've implemented the class which passes the clearcase data structures into the versioning system, but this seems to now be a vcs core issue.
Then, why are we doing some ClearCase integration at all ? There is always an alternative way - use VCS system specific GUI. As for the dots format of versions VSS does not provide it too. Martin creates numbers himself so that version tree can be built. Can't you do the same ? If not, can you disable the "Versioning Explorer" action or at least invoke proper ClearCase GUI component. I disagree to have this issue as resolved later. If nothing is doable ask for waiver.
*** Issue 31918 has been marked as a duplicate of this issue. ***
Resolving as later since there will be issue #32063 fixed into NB 3.5. This problem however should be resolved into NB 4.0.
The way versioning API is written is cvs-centric in the sense that it assumes revisions in the form of <num>.<num>. There's a new issue #32570 which should solve this problem.
Just a quick survey. Do we still plan to fix this issue into 4.0 ?
Reopening in order to get my question answered ...
It depends whether S1S needs that. Since this depends on a better versioning APIs, issue #32570 should be probably P1 defect as well (there are no suitable APIs to implement this). Peter, will you continue on ClearCase integration in 4.0?
I believe so.
Scheduling for promo-D.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team