[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-20609: ------------------------------------ I tried mickaels branch today and here is my input (I guess most of the points were made already): * I like this approach. It makes installing EA stuff easier and more visible (even though it's kinda confusing. But I hope we can figure out how to make it less confusing) * Installing connector which has both EA and non-EA is currently very confusing. ** First, there is no way how to figure out which connectors are both EA&non-EA. This should be somehow displayed on list of connectors. We have to make that more visible, noticeable. ** Second, when user selects that connector to install, dialog pops up and even there it's not obvious which one is EA adn which one isn't - http://i.imgur.com/yR2lkWO.png (I guess, that this is a bug... that one of them should have EA certificationId ("Experimental - Early Access") according to earlyaccess discovery jar.) * In current version of JBDS (9.0.0), there is information about EA being enabled/disabled on Software/Update page shown in form of "Enable EA" checkbox... This information disappeared from Software/Update page (one has to either look at Getting Started page or open EA installation dialog - click "Manage Early Access" button). I would like to see that information directly on Software/Update page, even if that's just a simple label/warning. * Hmm... looking around now I noticed, that all connectors have "Certified" certification (even EA ones)... this is definitely a bug (the tooltip of certification is correct though...) and it's affecting also the "Select extension flavor" dialog. * another bug - in Manage Early Access dialog, the "Disable EA and related software sites" button is allways disabled. That's because the "is EA enabled" property is stored in discovery plugin preferences, but it is read from central preferences. * Another thing I noticed is that the property I was talking in bullet above is stored in workspace specific preferences (Instance scope). I believe, that storing it in eclipse specific preferences (configuration scope) would be imo better. -- This message was sent by Atlassian JIRA (v6.4.11#64026)