[ https://issues.jboss.org/browse/JBIDE-20664?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20664: --------------------------------------------- if you post this somewhere else and it does not get automatically added somewhere and result in mixing of stable and staging urls then all fine by me - but then I really don't see the point of having it if we can't actually make use of this automation more than when just needing to setup an experiment. IMO the thing in JBIDE-20100 should have been done by [~pleacu] doing a discovery build from master which we then just included and be done with it and if that had not been possible then created a fork of it and do a temporary build and tell those who wanted a mockup to pass in the appropriate system property to test so it was very explicit that this is not what is actually what is in master nor what will be released. I hope you guys do realize when I talk about mixing staging/ development/ sites im not only talking about the discovery site itself but that if our GA includes a staging build of IS discovery users will suddenly end up with updatesites being mixed in from other sites referenced in the discovery.xml ....luckily most of those are today extracted into ide.properties but they have fallbacks that would end up in mixing users updatesites. Hence why I cannot see this be automated by dynamically fetching latest builds from IS into JBoss Tools master/maintanence release builds. -- This message was sent by Atlassian JIRA (v6.4.11#64026)