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: | Corrupted attach wizard | ||
---|---|---|---|
Product: | profiler | Reporter: | ehucka <ehucka> |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | VERIFIED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | exceptions' stacktraces |
Description
ehucka
2006-11-02 19:54:28 UTC
Created attachment 35741 [details]
exceptions' stacktraces
It works fine for me. Please provide more information. As I described above most of scenarios ends with exceptions and not changing panels in the wizard. More details: NetBeans IDE Dev (Build 200610231800) 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b102 Linux version 2.6.16-1.2122_FC5 running on i386 en_US (nb); UTF-8 NetBean Profiler 6.0 061103 Steps to Reproduce: 1. invoke Attach Profiler action 2. set project <Global Attach> 3. press Attach Wizard button 4. in Attach Wizard select e.g. Application target type 5. select Local machine and Direct attach invocation 6. press Next button 7. you will get to 2. step Review Attach Settings 8. press Next button Result: 1. Steps list (the left blue column) shows 3. steps Manual Integration selected 2. wizard panel shows still Review Attach Settings 3. attached exceptions are thrown 4. Next button is enabled 5. after you will press Next button once more you will get into a state when there is not selected any item in left navigation list and wizard panel is empty still can't reproduce it. are you able to reproduce it with a fresh clean user dir? yes, of course, fresh userdir, no project opened But I tried to reinstall whole ide and it helped. I had installed some other packs in previous installation but now I cannot reproduce the behaviour with all packs installed again. Strange. The exceptions are probably not useful too. So I'm closing it as invalid now. verified Duplicate of Issue 97411. No more valid in 6.0 after removing 1.4.2 support. *** This issue has been marked as a duplicate of 97411 *** v |