[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- thanks for the screencast, here are some initial comments then later on some concerns: a) I assume the dialog does not show up if there is just one connector available and it is GA'ed (non-early access), right ? b) it should automatically select an option - I suggest the supported version and after that what user chose last. c) earlyaccess should not be the first item in the list. d) how do I disable earlyaccess so it will remove the EA updatesite from the list of updatesites it will look at ? and now the issue with this approach: Once you have installed something from early access the earlyaccess updatesite is added to your jbds install and thus the choice you have here really does not guarantee you that the GA bits will be installed over what is in the earlyaccess. IMO, once a user the first time have said yes to earlyaccess and thus *enabled* earlyaccess he don't really have a choice anymore until he disables it. About the making JBDS users aware of using older JBDS - that was the main issue in this jira and I suggested a few times now how to do it (introduce a new connector type or certification which won't install anything but provide a way to tell users where to get things from). It is not an either or situation we have here - we need this (to stop having jiras and discussions about Fuse etc. missing from the field) AND we need to investe in having Fuse build compatible enough with JBDS - but the latter haven't worked the last 4 years and i'm sure we won't be much better of in the future nor does enabling earlyacccess by default work (as described above). What is so difficult/wrong about providing a way for us to tell users to go use another version for download ? (sure - it hurts my professional soul having to do it, but not handling it is no longer an option). -- This message was sent by Atlassian JIRA (v6.3.15#6346)