Community
Participate
Working Groups
Builds using Tycho snapshot started failing suddenly yesterday (2014/06/26). You can find an example at: https://textuml.ci.cloudbees.com/job/kirra-api/80/console [WARNING] Error injecting: org.eclipse.tycho.core.locking.FileLockServiceImpl com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/eclipse/core/runtime/internal/adaptor/BasicLocation at org.eclipse.tycho.core.locking.FileLockServiceImpl.<init>(Unknown Source) while locating org.eclipse.tycho.core.locking.FileLockServiceImpl 1 error at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1006) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032) ... Caused by: java.lang.NoClassDefFoundError: org/eclipse/core/runtime/internal/adaptor/BasicLocation at org.eclipse.tycho.core.locking.FileLockServiceImpl.<init>(FileLockServiceImpl.java:28) ... 118 more Caused by: java.lang.ClassNotFoundException: org.eclipse.core.runtime.internal.adaptor.BasicLocation
this is probably a temporary maven repository cache issue on your side (either local maven repo or intermediate nexus proxy cache) after change http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=30a5c5c2f49773d7097e12fa40ade0a259592e9b Try deleting ~/.m2/repository/org/eclipse/tycho and/or or forcing artifact updates (mvn -U) In case you are using a maven repository manager, make sure its proxy is up to date too.
I think that this is more likely due to our partially deploying CI job: http://ci.tesla.io:8080/view/Tycho/job/tycho/
The underlying issue is tracked here: bug 435050 *** This bug has been marked as a duplicate of bug 435050 ***