osgi / workspace

REPLACED BY enroute.workspace

OSGi enRoute Archetype

This repository represents a template workspace for bndtools, it is the easiest way to get started with OSGi enRoute. The workspace is useful in an IDE (bndtools or Intellij) and has support for continuous integration with gradle. If you want to get started with enRoute, then follow the steps in the quick-start guide.

workspace's Issues

JDK Base Line

Is there any specific reason why the "workspace" was base lined with JDK 8, is it possible to basline to JDK 7 ?

JPM cannot be indexed (Resolve-Button not working)

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

Relese repo changed on a way to 1.0

In commit c0520c1 the -releaserepo line was removed from enroute.bnd. This caused the (updated) workspace to forget about what was previously released to Release and offered to re-release everything into Local.

From the names of the repos it looks like the change was not deliberate, but an by-product of massive change, and the -releaserepo line should be reintroduced.

Example running & response nothing!

I build this example and all the things going well except when running it.
I add gogo console, no input ready. where to find the log? and where blocked?
http://localhost:8080/com.acme.prime.upper output is: The requested resource could not be found.