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 159051

Summary: Can not update plugin
Product: updatecenters Reporter: nnnnnk <nnnnnk>
Component: PluginportalAssignee: issues@updatecenters <issues>
Status: RESOLVED FIXED    
Severity: blocker    
Priority: P2    
Version: 6.x   
Hardware: Sun   
OS: All   
Issue Type: DEFECT Exception Reporter:
Attachments: new version of plugin

Description nnnnnk 2009-02-24 11:47:31 UTC 
Hello,
I'm trying to update my plugin (http://plugins.netbeans.org/PluginPortal/faces/ModifyPage.jsp?pluginid=14444) but
getting error message:
---
Plugin Portal Error!

You have reached this page because of an internal Plugin Portal error. Please note that you must have JavaScript enabled
to use the Plugin Portal.

If you continue to reach this page, please contact the webmaster.
--

Regards,
Nick.
Comment 1 nnnnnk 2009-02-24 11:49:37 UTC 
Created attachment 77289 [details]
new version of plugin
Comment 2 Jiri Kovalsky 2009-02-24 12:26:31 UTC 
Nikolay, I saw that you successfully updated the binary in the end. Am I right? Why did you attach the bits here?
Comment 3 nnnnnk 2009-02-24 12:40:44 UTC 
No, I have not updated the binary in the end.

On plugin page Specification Version is 0.2.1.
In attachment there is version 0.2.2.
Comment 4 Jiri Kovalsky 2009-02-24 13:05:07 UTC 
Oh yes, I tried to update it on your behalf but it really does not work. Frankly, current version of Plugin Portal is in
a bad condition and we are seriously considering what to do next. We have new Phase IV version staged but couldn't
deploy it for certain reason but we also think of other long term solutions. Please bear with us and try to update the
plugin binary once more for example tomorrow.
Comment 5 nnnnnk 2009-02-24 13:24:49 UTC 
Ok.
Thank you.
Comment 6 nnnnnk 2009-03-13 16:29:56 UTC 
I've successfully updated my plugin.
Thank you.
Comment 7 Jiri Kovalsky 2009-03-13 22:01:00 UTC 
Great, closing this issue then. Thanks for your update.