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.
Waiting for marketing for url to diplay, but we need to have a V2 and V3 server node popup menu to call a page that will contain V2, V3 info and registration/subscription info. P2 per marketing request so that it is part of 6.5 to help the registration/subscription goals.
The Register item will only be enabled when the installation is not registered. the item will open the browser on the URL that is coming from marketing.
Created attachment 71420 [details] the first pass patch
passing this to nitya. double check the stuff labelled 'TODO'. Note: there are still significant tasks that need to get the registration relay service back-end ready to start accepting registrations that this feature would generate.
Integrated into 'main-golden', will be available in build *200810111401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/098872f0ea22 User: nityad@netbeans.org Log: #149148 : added GlassFish modules as friends to support Register action for v2 & v3
the register action on a v3 node depends on the moving reglib to the ide cluster.
Created attachment 71721 [details] v3 changes patch
Integrated into 'main-golden', will be available in build *200810140201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/6ff64288ddf6 User: nityad@netbeans.org Log: #149148 : Registration support for v2 plugin
this has been resolved for v2 servers. v3 needs to be addressed by more extensive changes.
The best resolution strategy for this issue is dependent on an architectural level change. Those changes are in code controlled by other teams, so it may not happen in time. Other strategies involve significantly more coding and increased risk.
passed the 48 hour window... considered approved
I will take this one back now.
adding a menu item to the server node was considered 'polluting the UI', I have opened a couple enhancements that include info about other UI strategies that appear to be more acceptable. See issue 150565 and issue 150567. I am closing this issue, as a dup of 150565 (though it is really a dup of both issues) *** This issue has been marked as a duplicate of 150565 ***