[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12914: ------------------------------- Assignee: Mickael Istria -- 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

[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-12914. ------------------------------------ Resolution: Done Parent pom now declares usage of Tycho 0.16. -- 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

[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12914 at 11/17/12 12:35 PM: --------------------------------------------------------------- New problem... Tycho 0.16 is more insistent that all sites listed in a composite be present. This is fine once we're bootstrapped, but when I purge the contents of builds/staging/<jobnames>/ to ensure we don't accidentally mix the streams and that we can build everything from scratch, I instead get this: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--base/26/console} [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0.... [ERROR] Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0..... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_stable... {code} Obviously there's no *jbosstools-4.0_stable_branch.component--base* site, because we're building *jbosstools-4.0_stable_branch.component--base* for the first time. was (Author: nickboldt): New problem... Tycho 0.16 is more insistent that all sites listed in a composite be present. This is fine once we're bootstrapped, but when I purge the contents of builds/staging/<jobnames>/ to ensure we don't accidentally mix the streams and that we can build everything from scratch, I instead get this: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--base/26/console} [INFO] Adding repository http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0.... [ERROR] Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0..... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_stable.... -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0..... {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12914: ------------------------------------ With p2.atomic.composite.loading=false added to all _composite_ sites, eg., {code:title=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/compositeArtifacts.xml} <property name="p2.atomic.composite.loading" value="false"/> {code} we get simply a {color:yellow}*WARNING*{color} instead of the {color:red}ERROR{color} above: {code} [WARNING] Failed to access p2 repository http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4..., use local cache. Neither http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4... nor http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4... found. [WARNING] Failed to access p2 repository http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4..., use local cache. Neither http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4... nor http://download.jboss.org/jbosstools/builds/staging.previous/jbosstools-4... found. {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12914: ------------------------------- Fix Version/s: 4.0.0.CR2 (was: 4.0.0.CR1) -- 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

[ https://issues.jboss.org/browse/JBIDE-12914?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-12914. ------------------------------ Fix Version/s: 4.0.0.CR1 (was: 4.0.0.CR2) Resolution: Done Workaround should no longer be needed. Closing again. -- 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