[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3085: ------------------------------------------- Just to be clear - I never suggested we do this for JBDS 8 and the current setup. I said the whole idea about earlyaccess was to *eventually* allow for this scenario. To answer the questions: A) There is zero difference here from any other earlyaccess content. No, we don't support easily uninstalling/downgrading that either. We *should* but we don't at the moment since we always remove the old versions, only keep the new ones. But in short - zero difference from this to other things in early access. B) support already said they were ok with earlyaccess providing alpha/beta releases - that is what the whole point of earlyaccess is. Wether that is JBDS itself or just addons like JBDS-IS really should have zero difference from support POV. C) I don't see a problem here since we now have the global properties to handle that jbds will go fetch the right examples based on your installed version, this situation with EAP 6.x differences is not at all related to this issue - i.e. its an issue that already exist today and we already have multiple version support for that and finally its early access, some stuff are expected to break D) plenty of things which is why I have not raised any jiras about this but simply discussed it in comments to not make it sound more scary than it is. This is part of why there are jiras discussing making sure we can actually identifiy earlyaccess content is installed and provide a list of the plugins/bundles that are supported vs non-supported and yes we'll need to handle the uninstall usecases better to allow installing early access. All that being said I don't think first attempt at this would be *FULL* JBDS update - but simply *parts* of it. Like, a newer version of Thym or maybe even Tern as opposed to full 8.1.0.Alpha1 content. -- This message was sent by Atlassian JIRA (v6.2.6#6264)