search

osgi / workspace

REPLACED BY enroute.workspace
7 stars 10 forks source link

JPM cannot be indexed (Resolve-Button not working) #1

Open lostiniceland opened 9 years ago

lostiniceland commented 9 years ago

When I follow the enRoute-Tutorial I cannot use the Resolve-Button on the Run-Tab. The error occurs on the tutorial-page "Running your Code" http://enroute.osgi.org/tutorial_base/400-run.html

I used the latest BndTools 2.4 and even tried the latest Development-Build (2.5) from today. I get the same exception in both versions.

Exception during resolution. java.lang.RuntimeException: java.lang.IllegalStateException: Cannot index [JpmRepository [writable=false, name=Central, location=~/.bnd/shacache, digest=7B1CB9F8A1359B47A4DB924F2098F53EA06994AD]] due to [F55EBBDFC8EECC77B0F4AB8A5375B48C235BFAFC: java.io.IOException: Could not open URL, [404] Not Found for 'https://bndtools.ci.cloudbees.com/job/bnd.master/460/artifact/dist/bundles/biz.aQute.bnd.annotation/biz.aQute.bnd.annotation-2.4.0.jar'] at biz.aQute.resolve.internal.BndrunResolveContext.init(BndrunResolveContext.java:73) at biz.aQute.resolve.GenericResolveContext.getMandatoryResources(GenericResolveContext.java:562) at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:123) at biz.aQute.resolve.BndResolver.resolve(BndResolver.java:20) at biz.aQute.resolve.ResolveProcess.resolveRequired(ResolveProcess.java:32) at org.bndtools.core.resolve.ResolveOperation.run(ResolveOperation.java:87) at org.bndtools.core.resolve.ResolveJob.run(ResolveJob.java:57) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.IllegalStateException: Cannot index [JpmRepository [writable=false, name=Central, location=~/.bnd/shacache, digest=7B1CB9F8A1359B47A4DB924F2098F53EA06994AD]] due to [F55EBBDFC8EECC77B0F4AB8A5375B48C235BFAFC: java.io.IOException: Could not open URL, [404] Not Found for 'https://bndtools.ci.cloudbees.com/job/bnd.master/460/artifact/dist/bundles/biz.aQute.bnd.annotation/biz.aQute.bnd.annotation-2.4.0.jar'] at aQute.bnd.deployer.repository.wrapper.InfoRepositoryWrapper.init(InfoRepositoryWrapper.java:142) at aQute.bnd.deployer.repository.wrapper.InfoRepositoryWrapper.findProviders(InfoRepositoryWrapper.java:154) at aQute.bnd.deployer.repository.wrapper.Plugin.findProviders(Plugin.java:132) at biz.aQute.resolve.GenericResolveContext.findProviders(GenericResolveContext.java:222) at biz.aQute.resolve.internal.BndrunResolveContext.findFramework(BndrunResolveContext.java:216) at biz.aQute.resolve.internal.BndrunResolveContext.init(BndrunResolveContext.java:68) ... 7 more

AdrieVanDijk commented 9 years ago

I got exactly the same with the Quick Start Tutorial. After a lot of trial and error, I managed to solve it as follows:

When you go to https://bndtools.ci.cloudbees.com/job/bnd.master , you will notice that it lists several builds of this bundle, but #460, which the url in your report is referring to, is not there. Maybe they cleaned it up because it was too old, who knows.

lostiniceland commented 9 years ago

The workaround did also work for me. Thanks.

ncuka commented 9 years ago

Workaround worked like a charm. Thanks. For extremely dense people like me, the Repository sub-window is an Eclipse View located at the bottom left of the screen.