[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15482 at 10/14/13 10:20 PM: --------------------------------------------------------------- {quote}use of a composite site is bad and causing issues{quote} The reason it's "bad" is that contents of {code}staging/<job_name>{code} and {code}staging.previous/<job_name>{code} are *subject to change* w/ each new published build. So the statically coded composite site [1] contents may point to different content unexpectedly DURING a build, resulting in unresolved IUs, because one or more of the child sites suddenly contain a DIFFERENT version of the component's build. [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... The solution, as outlined in this JIRA (before all the comments above began), is to avoid that issue by instead generating the composite*.xml files to point to the ACTUAL build folders, eg., in this example [2]. So instead of having URLs with "staging.previous" you'd have {code} staging/CI/jbosstools-server_master_JBDS2741/2013-09-24_14-46-04-B13/all/repo staging/CI/jbosstools-server_master_JBDS2741/2013-09-25_14-46-04-B14/all/repo staging/CI/jbosstools-server_master_JBDS2741/2013-09-25_18-46-04-B15/all/repo ... {code} [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... If this is not the solution you want, please suggest an alternative approach. I'm coding based on the spec that [~dgolovin] put forth, documented above in the *Description* field. {quote}that is why I suggested doing that as part of those other issues.{quote} Which other issues? was (Author: nickboldt): {quote}use of a composite site is bad and causing issues{quote} The reason it's "bad" is that contents of {code}staging/<job_name>{code} {code}staging.previous/<job_name>{code} are subject to change w/ each new published build. So the statically coded composite site [1] contents may point to different content unexpectedly DURING a build, resulting in unresolved IUs. [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... The solution, as outlined in this JIRA (before all the comments began), is to avoid that issue by instead generating the composite*.xml files to point to the ACTUAL build folders, eg., in this example [2]. [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.... If this is not the solution you want, please suggest an alternative approach. I'm coding based on the spec that [~dgolovin] put forth, documented above in the *Description* field. {quote}that is why I suggested doing that as part of those other issues.{quote} Which other issues? -- 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