[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Mustafa Musaji edited comment on JBDS-3085 at 7/15/14 4:36 AM: --------------------------------------------------------------- {quote} You have to be more clear here - what do you think the early access feature in new JBoss Central is for if not for installing early access components the user haven't installed yet ? (With clear warnings of course) {quote} Perhaps my understanding is not clear, but, installing early access components is fine, but that shouldn't change the version of JBDS. Install all the early access components you want, none of them are supported etc. {quote} so you are fine to install addons that makes the product unsupported and cannot be undone {quote} They make the components unsupported, not the product. If customer installs an early access version of "angularjs tooling" but then has an issue with his workspace for example, if he's running an Alpha release of JBDS it's not supported. If he's running JBDS GA with a early access of "angularjs tools", he's still supported with any issue not related to angularjs tooling. If you want to upgrade the user to a non supported version, we have to have a way customer can go back to a supported version easily without it affecting their workspace/projects and existing tools. At the moment, I believe this is not possible or as [~nickboldt] says, is "problematic at best". I'm starting to think even with warnings and pop ups, this isn't a good idea. was (Author: mmusaji): {quote} You have to be more clear here - what do you think the early access feature in new JBoss Central is for if not for installing early access components the user haven't installed yet ? (With clear warnings of course) {quote} Perhaps my understanding is not clear, but, installing early access components is fine, but that shouldn't change the version of JBDS. Install all the early access components you want, none of them are supported etc. {so you are fine to install addons that makes the product unsupported and cannot be undone} They make the components unsupported, not the product. If customer installs an early access version of "angularjs tooling" but then has an issue with his workspace for example, if he's running an Alpha release of JBDS it's not supported. If he's running JBDS GA with a early access of "angularjs tools", he's still supported with any issue not related to angularjs tooling. If you want to upgrade the user to a non supported version, we have to have a way customer can go back to a supported version easily without it affecting their workspace/projects and existing tools. At the moment, I believe this is not possible or as [~nickboldt] says, is "problematic at best". I'm starting to think even with warnings and pop ups, this isn't a good idea. -- This message was sent by Atlassian JIRA (v6.2.6#6264)