[ https://issues.jboss.org/browse/JBIDE-13288?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13288: --------------------------------------------- The value is you do not need to update any url or ask anyone to set -D properties what so ever since an early build will pick up version specific setup that you have uploaded. i.e. 7/0/0/Beta2-2342343342234/discovery.xml This is the whole problem you have been finding problematic - with this it just disappear. {quote} The other problem with this is that if the Discovery plugin gets respun out of band, and you have a 7/0/0/Beta2a (after Beta2 is done but before CR1) or a 7/0/0/GA-1 (after GA but before 7/0/1) you need to ensure that you have a way of telling existing users that there's a new URL to scan. How will JBDS know there's a new discovery URL? {quote} I don't understand the sequence events you present here. If there is something new that you want users to pickup you publish it into the tree you want it picked up. If you want all version 7 to pick up the proper version just put it in 7/0 and all 7.0 versions with no matching specific version in the tree will pick it up. There is no "automatic" publishing of the discovery site since it does not have the exact version info. We will add caching of course so it does not happen all the time but thats the same case as yoday. Actually, thinking about it we could just create a "7/devstudioinfo.xml" file that just lists these explicitly. Something like: {{ <info> <discovery.xml version="7" url="url7"/> <discovery.xml version="7.0.0.Alpha2-v3242344" url="url7alpha2specific"/> </info> }} The above would make all 7.* versions except 7.0.0.Alpha2-v3242344 pick up "url7", the specific version would use "url7alpha2specific". This would allow us full control over staging, dev, released builds usage of discovery and any other settings - and no need for multiple 404 requests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira