[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- d) so now we make it more complicated to disable the earlyaccess repository ? that seems unnecessary to me. "the fact that you have some Early-Access repositories enabled doesn't guarantee that when installing a connector, you get the Early-Access version of its features/plugins." - some EA repositories ? There are only *one* repository. And how are you avoiding it will not get the earlyaccess versions of angularjs ? "With our current implementation of Central and the connectors we have, the same feature isn't available in 2 different versions" - the intent of earlyaccess have always been to also be able to allow *earlier* versions of the same thing installed. I do not think we should limit our UX experience here to a world where we will *always* guarantee there are zero overlap between the two. And this *is* a change compared to the old UI where when earlyaccess was enabled you were not in any way offered to install the GA versions since we know it will install the EA parts once the EA site is added. So this is for sure a consequence/ambiguity this new UI introduces. "The description doesn't even mention anything about older JBDS. It's more your mind which is focused on that part than the initial user request.". Let me quote from the description which *I* wrote and which Jim provided input to - a user that just commented the exact concern about not being able to guarantee tooling are available for users to use :) ""<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."" That is the first and foremost issue and still not solved. "To me, this means that we can put current Fuse IDE as an "Early Access" connector in JBDS 9" - *we* (you and I) do not get to decide when that is available; nor is everything in JBDS-IS currently available for JBDS 9 EA so the issue still remains. The current PR does not solve the problem raised, and it currently introduces an ambiguity about what will happen wen earlyaccess repositories are added - if we are going to do a change here we need to at least make sure the behavior is not ambiguous. If we are going to leave out the "tell users when things are not even available in EA" part of this that will only happen because just by luck we have enough IS available .... but this will not help us at 9.1, 10.0, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)