[ https://issues.jboss.org/browse/JBIDE-16755?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16755: ------------------------------------ [~mickael_istria] "A build timeout can be a symptom of a target-platform which is more recent than the Eclipse instance. Then it might force p2 to update much more stuff than necessary." ... this is true, but the install grinder job has been failing since Feb 28, and the changes to include Luna M6 in the 4.40.Beta1-SNAPSHOT only happened on Mar 13-14 [1]. [1] https://github.com/jbosstools/jbosstools-target-platforms/commits/4.40.x I've updated the jobs (master and 4.2.luna) to use M6 instead of M5, but it seems like the problem is more likely one of the above issues: a) two different versions of package 'javax.xml.bind' b) No property tester contributes a property com.google.gdt.eclipse.suite.isLaunchTarget to type class org.jboss.tools.central.editors.JBossCentralEditorInput c) SWT error - Internal browser is not available: No more handles d) org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 3600000 ms.: Blocking while calculating deps -- 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