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: | Plugins under validation are not correctly handled | ||
---|---|---|---|
Product: | updatecenters | Reporter: | ent38 <ent38> |
Component: | Pluginportal | Assignee: | Jan Pirek <jpirek> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Screenshots |
Description
ent38
2013-06-02 16:12:57 UTC
Created attachment 135227 [details]
Screenshots
Screenshots
Verified on NB 7.3.0, not 7.0, of course. Hello Jonathan, let me summarize the not working scenario. 1. I create a plugin (*.zip) consisting of two NBM files (a.nbm and b.nbm) with OpenIDE-Module-Specification-Version="1.0". 2. It gets approved which automatically publishes the plugin on Experimental Plugin Portal Update Center (EPPUC). 3. The 1.0 plugin is verified so users can install it from the Plugin Portal Update Center (PPUC). 4. I upload new *.zip binary of the plugin containing three NBM files (a.nbm, b.nbm and c.nbm) with OpenIDE-Module-Specification-Version="1.1". 5. The plugin is now available this way: PPUC: 1.0 and EPPUC: 1.1. 6. I request new verification of the plugin. 7. Now you say that when users decide to download 1.0 version of my plugin from PPUC, they will download a.nbm:1.1, b.nbm:1.1? Thanks for your clarification! -Jirka Hi, Yes, it is exactly this scenario. Honzo, can you please take a look at this? Version-to-be-yet-verified should not show up on the live PPUC. Thanks! |