hi ,
i end up in the same situation.
i set up the IDE according instructions and end up an the error message.
even without adding my binding i do get this error
What needs to be done to get this resolved to be able to start OH3 in debug modus?
try to build your binding with “mvn clean install -Dohc.version=3.0.2”
hmm,
deleted the complete dev and again setup up and now the resolve works.
maybe something changed in the meanwhile.
thx anways
@wborn Again I ran into the issue twice. It seems that once you ran a regular mvn clean install (without -Dohc.version=3.0.2) some files in the repository get overwritten and afterwards you run in the sam issue even when building for 3.0.2. Last time I just deleted the org/openhab folder in the .m2 reporitory and was able to fix the issue
This time I’m no longer able to build for 2.5 after doing the same. This error shows up
[ERROR] Failed to execute goal on project org.openhab.binding.carnet: Could not resolve dependencies for project org.openhab.addons.bundles:org.openhab.binding.carnet:jar:2.5.13-SNAPSHOT: The following artifacts could not be resolved: org.openhab.core.bom:org.openhab.core.bom.compile:pom:2.5.0, org.openhab.core.bom:org.openhab.core.bom.openhab-core:pom:2.5.0, org.openhab.core.bom:org.openhab.core.bom.test:pom:2.5.0: Failure to find org.openhab.core.bom:org.openhab.core.bom.compile:pom:2.5.0 in https://openhab.jfrog.io/openhab/libs-release was cached in the local repository, resolution will not be reattempted until the update interval of openhab-release has elapsed or updates are forced -> [Help 1]
I tried to run “mvn clean install -U”, but problem persists. Was anything in the 2.5 repo removed causing this problem?
The 2.5.x artifacts probably depend on Bintray repos which no longer exist now it has sunset.
@wborn Today I’m running into this error
[ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.7:verify (karaf-feature-verification) on project org.openhab.binding.carnet: Feature resolution failed for [openhab-binding-carnet/3.1.0.SNAPSHOT]
[ERROR] Message: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-binding-carnet; type=karaf.feature; version=3.1.0.SNAPSHOT; filter:="(&(osgi.identity=openhab-binding-carnet)(type=karaf.feature)(version>=3.1.0.SNAPSHOT))" [caused by: Unable to resolve openhab-binding-carnet/3.1.0.SNAPSHOT: missing requirement [openhab-binding-carnet/3.1.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.binding.carnet; type=osgi.bundle; version="[3.1.0.202105110617,3.1.0.202105110617]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.binding.carnet/3.1.0.202105110617: missing requirement [org.openhab.binding.carnet/3.1.0.202105110617] osgi.wiring.package; filter:="(&(osgi.wiring.package=org.osgi.framework)(version>=1.9.0)(!(version>=2.0.0)))"]]
[ERROR] Repositories: {
[ERROR] file:/Users/markus/Dev/openhab-3/git/openhab-addons/bundles/org.openhab.binding.carnet/target/feature/feature.xml
[ERROR] mvn:org.apache.karaf.features/framework/4.2.7/xml/features
[ERROR] mvn:org.apache.karaf.features/standard/4.2.7/xml/features
[ERROR] mvn:org.openhab.core.features.karaf/org.openhab.core.features.karaf.openhab-core/3.0.2/xml/features
[ERROR] mvn:org.openhab.core.features.karaf/org.openhab.core.features.karaf.openhab-tp/3.0.2/xml/features
[ERROR] mvn:org.ops4j.pax.web/pax-web-features/7.2.11/xml/features
[ERROR] }
while running “mvn clean install -Dohc.version=3.0.2”. Nothing changed since yesterday evening except the binding code itself, just rebuild.
Was 3.0.2 removed from the build system?! In This case: How to build a binding, which runs on OH3.0.2 (stable release)?
I’m not aware of any changes to this so I’d think it should still work like that.
Problem solved after reinstalling the IDE,thx
@wborn fyi (and others)
once more I’m not able to build (yesterday evening it works fine, this morning again missing dependencies).
[ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.3.1:verify (karaf-feature-verification) on project org.openhab.binding.carnet: Feature resolution failed for [openhab-binding-carnet/3.1.0.SNAPSHOT]
[ERROR] Message: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=openhab-binding-carnet; type=karaf.feature; version=3.1.0.SNAPSHOT; filter:="(&(osgi.identity=openhab-binding-carnet)(type=karaf.feature)(version>=3.1.0.SNAPSHOT))" [caused by: Unable to resolve openhab-binding-carnet/3.1.0.SNAPSHOT: missing requirement [openhab-binding-carnet/3.1.0.SNAPSHOT] osgi.identity; osgi.identity=org.openhab.binding.carnet; type=osgi.bundle; version="[3.1.0.202105130609,3.1.0.202105130609]"; resolution:=mandatory [caused by: Unable to resolve org.openhab.binding.carnet/3.1.0.202105130609: missing requirement [org.openhab.binding.carnet/3.1.0.202105130609] osgi.wiring.package; filter:="(&(osgi.wiring.package=javax.measure)(version>=2.1.0)(!(version>=3.0.0)))"]]
[ERROR] Repositories: {
[ERROR] file:/Users/markus/Dev/openhab-3/git/openhab-addons/bundles/org.openhab.binding.carnet/target/feature/feature.xml
[ERROR] mvn:org.apache.karaf.features/framework/4.3.1/xml/features
What I did
- Clean project in Eclipse
- Maven->Update Project in Eclipse
- Resolve dependencies in Eclipse->Save
- mvn clean install -Dohc.version=3.0.2
= no success
This fixed my issue (maybe after the other steps)
- Remove binding from dependencies->Resolve->Update
- Add binding->Resolve->Save
1 Like
The above fixed an issue for me as the build was passing but openHAB was complaining about missing javax.measure when the jar was placed into the addons folder of openHAB 3.1m4
Unresolved requirement: Import-Package: javax.measure; version="[2.1.0,3.0.0)"
After doing the above the jar now works perfect. I don’t build for V2.5 anymore but I used to on this machine 8 months ago, so guessing I had some stuff left over that was causing issues.
1 Like
@wborn Today I get the following warnings when starting my binding in Eclipse
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions
INFORMATION: Adding the extensions from bundle org.apache.cxf.cxf-rt-frontend-jaxrs (112) [org.apache.cxf.jaxrs.JAXRSBindingFactory]
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions
INFORMATION: Adding the extensions from bundle org.apache.cxf.cxf-rt-rs-sse (114) [org.apache.cxf.transport.sse.SseProvidersExtension]
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions
INFORMATION: Adding the extensions from bundle org.apache.cxf.cxf-rt-transports-http (116) [org.apache.cxf.transport.http.HTTPTransportFactory, org.apache.cxf.transport.http.HTTPWSDLExtensionLoader, org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder, org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder, org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider]
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
INFORMATION: Aries Blueprint packages not available. So namespaces will not be registered
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
INFORMATION: Aries Blueprint packages not available. So namespaces will not be registered
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
INFORMATION: Aries Blueprint packages not available. So namespaces will not be registered
Mai 19, 2021 9:37:15 VORM. org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
INFORMATION: Aries Blueprint packages not available. So namespaces will not be registered
Mai 19, 2021 9:37:15 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.apache.aries.jax.rs.whiteboard.internal.client.ClientBuilderImpl of service javax.ws.rs.client.ClientBuilder in bundle org.apache.aries.jax.rs.whiteboard
Mai 19, 2021 9:37:15 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.apache.cxf.jaxrs.impl.RuntimeDelegateImpl of service javax.ws.rs.ext.RuntimeDelegate in bundle org.apache.aries.jax.rs.whiteboard
Mai 19, 2021 9:37:15 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.apache.cxf.jaxrs.sse.client.SseEventSourceBuilderImpl of service javax.ws.rs.sse.SseEventSource.Builder in bundle org.apache.aries.jax.rs.whiteboard
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.http.Http1FieldPreEncoder of service org.eclipse.jetty.http.HttpFieldPreEncoder in bundle org.eclipse.jetty.http
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.websocket.common.extensions.identity.IdentityExtension of service org.eclipse.jetty.websocket.api.extensions.Extension in bundle org.eclipse.jetty.websocket.common
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.websocket.common.extensions.fragment.FragmentExtension of service org.eclipse.jetty.websocket.api.extensions.Extension in bundle org.eclipse.jetty.websocket.common
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.websocket.common.extensions.compress.PerMessageDeflateExtension of service org.eclipse.jetty.websocket.api.extensions.Extension in bundle org.eclipse.jetty.websocket.common
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.websocket.common.extensions.compress.DeflateFrameExtension of service org.eclipse.jetty.websocket.api.extensions.Extension in bundle org.eclipse.jetty.websocket.common
Mai 19, 2021 9:37:16 VORM. org.apache.aries.spifly.BaseActivator log
INFORMATION: Registered provider org.eclipse.jetty.websocket.common.extensions.compress.XWebkitDeflateFrameExtension of service org.eclipse.jetty.websocket.api.extensions.Extension in bundle org.eclipse.jetty.websocket.common
I did
- Project cleam
- updated dependencies in Eclipse
- mvn clean install with -U
What does " Aries Blueprint packages not available" mean?
Looks like some harmless info logging. But it would be better to create new topics if it has nothing to do with your original topic. 