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: | Request to publish jVi (vi/vim) for NetBeans 7.0 plugin on Stable 6.9.1 UC | ||
---|---|---|---|
Product: | updatecenters | Reporter: | err <err> |
Component: | Stable | Assignee: | Petr Jiricka <pjiricka> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jkovalsky |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 179047 |
Description
err
2011-05-04 23:24:36 UTC
http://netbeans.org/community/guidelines/au-request-form.html is where I filled in the form. That page is out of date. Ernie, that form is only for NetBeans versions up to 6.9. In 7.0 we consolidated Update Centers and the recommended way is to publish plugin(s) on the Plugin Portal and ask for verification(s) which will get the plugin(s) to the Plugin Portal Update Center which is already registered in the standard distribution of the NetBeans IDE. It's up to Petr though how this request will be resolved. I agree with Jirka - Ernie, can you please use the plugin portal and request verification against 7.0? I also agree that the form is out of date - the page should stress that this is a legacy mechanism used for previous NetBeans releases, and for 7.0 the plugin portal is the right avenue. > use the plugin portal and request
> verification against 7.0?
Will do. I was confused; this form was recommended and I was in the middle of getting a release for 7.0 ready...
This brings up an issue for me. Version handling. Typically a separate release of jVi is required for each NB release, nb65/nb67 was the only exception. Following the pattern of publishing an update center, going forward I guess I'll have the plugins
jVi for nb7.0 UC
jVi for nb7.1 UC
etc.
Will all of these show up in the plugin list on a users system?
If you upload a new version and only request verification for 7.0, then the previous version will continue to be available to 6.9 users, and the newly uploaded version will be visible to 7.0 users. So I think we are fine in this respect. Still, I agree the version management on the plugin portal could be improved - there is issue #198001 filed for this. What Petr wrote is correct but only for users installing your plugin from the Plugin Portal Update Center via built-in Plugins manager. If you upload new binary it will replace the previous version available from the web browser. The old version will remain published on the Plugin Portal Update Center until you ask for new verification. We are looking into ways how to solve the plugin versioning issue. If the above workaround is not usable for you the clearest solution would be to publish multiple entries in the Plugin Portal for different NetBeans versions. Besides, I have updated the UC process description [1] in the Wiki so hopefully, nobody else will use the AUC form for NetBeans 7.0 and newer. I am marking this issue as FIXED. If you want, please add your comments to issue #198001. |