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 232349 - Apache JMeter plugin install
Summary: Apache JMeter plugin install
Status: REOPENED
Alias: None
Product: platform
Classification: Unclassified
Component: Plugin Manager (show other bugs)
Version: 8.0.2
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-07 20:52 UTC by lehel
Modified: 2015-09-11 15:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lehel 2013-07-07 20:52:46 UTC
Product Version = NetBeans IDE Dev (Build 201307062300)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.7.0_25
Runtime = Java HotSpot(TM) Client VM 23.25-b01

From Tools-Plugins-Available Plugins installing the JMeter plugin, Netbeans freezes at:
unpacking org-netbeans-modules-profiler-loadgen.nbm
Comment 1 Petr Cyhelsky 2013-07-08 08:15:08 UTC
I've just tried it, although the progress is stuck for some time at the point you mentioned, it eventually finishes.
Comment 2 lehel 2013-07-08 08:30:44 UTC
Then maybe should we consider this, as a problem of slowness?
Comment 3 emi 2015-07-20 00:28:01 UTC
This is an UX bug of the autoupdate UI. It's not acceptable to have the progress bar stuck at 67% for 10 minutes.

The user will rightfully believe NetBeans is stuck and try to kill it (the Cancel button is also disabled this whole time).

(See Geertjan's blog https://blogs.oracle.com/geertjan/entry/faq_jmeter_and_netbeans_ide :

> The plugin takes a long time to install. Unpacking hangs at 67%, during the unpacking of 'org-netbeans-modules-loadgenerator.nbm'. When this happens, don't worry, just wait a bit longer, for me it took about 10 minutes and then the installation succeeded.)

If the autoupdate classes are unable to estimate properly, it would be better to switch the progress to inDeterminate (or maybe even call suspend?).