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.

Bug 127751 - Neverending "installing progress" message while installing A11y tester plugin into shared directories
Summary: Neverending "installing progress" message while installing A11y tester plugin...
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Plugin Manager (show other bugs)
Version: 6.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: dlipin
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2008-02-19 15:35 UTC by Tomas Danek
Modified: 2009-04-17 07:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2008-02-19 15:35:46 UTC 
Product Version: NetBeans IDE Dev (Build 200802171202)
Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
System: Linux version 2.6.20-16-generic running on i386; UTF-8; en_US (nb)
Userdir: /tmp/ud
----------------
1) added new updare center http://a11y.netbeans.org/nbms/updates.xml into PM
2) selected Install into shared dirs, checked a11y tester module and ran installation
3) selected immediately Run in background. Progress did not stop. This module requires restart, after click on Update
icon  (next to running progress bar) is restart offered, but dialog "Exiting IDE will terminate following processes" is
shown.
4) Anyway confirmed restart, plugin is installed ok, so probably only UI problem with running progress.
5) Was not able to reproduce again.
Comment 1 Lukas Hasik 2008-04-10 21:30:17 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 2 Antonin Nebuzelsky 2008-11-14 15:33:28 UTC 
Reassigning to the new "autoupdate/*" owner dlipin.
Comment 3 dlipin 2009-04-17 07:40:48 UTC 
Never seen such a problem with 6.5 and latest dev builds of 6.7 and no one else reported the similar.
So likely the issue has gone away together with fixing some others.