Platform information:
Hardware: Intel N100, 16 GB RAM
OS: Docker
Java Runtime Environment:
openHAB version: different versions tried
Issue of the topic: Error downloading mvn:com.github.hypfvieh/bluez-dbus-osgi/0.2.0
Please post configurations (if applicable):
Items configuration related to the issue
Sitemap configuration related to the issue
Rules code related to the issue
Services configuration related to the issue
If logs where generated please post these here using code fences:
I get serial times Error downloading mvn:com.github.hypfvieh/bluez-dbus-osgi/0.2.0 on starting container.
I tried stable, latest and an latest snapshot.
https://mvnrepository.com/artifact/com.github.hypfvieh/bluez-dbus-osgi/0.2.0
exists but i don‘t understand why download fails.
wborn
(Wouter Born)
October 2, 2024, 5:31am
2
It tries to download it from the openHAB repo but apparently it is missing. Maybe @Kai can upload it?
The library was updated in:
openhab:main
← lsiepel:bluetooth-bluez-dep
opened 07:31AM - 22 Jul 24 UTC
Resolves: https://github.com/openhab/openhab-addons/issues/17112
Changelog ve… rsion 0.2.0 (2023-07-21):
- Requires Java 11
- Uses dbus-java 4.x
- Updated interfaces to comply with bluez 5.64
- Issue https://github.com/hypfvieh/bluez-dbus/issues/48 allow unregistering of signal handlers
- Issue https://github.com/hypfvieh/bluez-dbus/issues/51 added mesh interface classes
Test jar: https://1drv.ms/u/s!AnMcxmvEeupwjvsPCmlMsWrz8RjXWQ?e=2TrXH7
lsiepel
(Leo)
October 2, 2024, 7:55am
3
I thought that dependency’s that are available on maven do not need to be available on openHAB repo.
wborn
(Wouter Born)
October 2, 2024, 11:28am
4
Currently any bundle dependency defined in a feature.xml
file needs to be manually uploaded to the openHAB Maven repo. There’s openhab-distro#1686 to improve this.
1 Like
digitaldan
(Dan Cunningham)
October 2, 2024, 10:03pm
5
I’m also getting this error on our snapshot builds
Error downloading mvn:com.fasterxml.jackson.datatype/jackson-datatype-jdk8/2.17.1
@kai can you add this as well ?
splatch
(Łukasz Dywicki)
October 3, 2024, 2:26pm
6
It is sufficient to modify org.ops4j.pax.url.mvn.cfg
:
# This contains the openHAB and default repositories.
#
org.ops4j.pax.url.mvn.repositories= \
- https://openhab.jfrog.io/openhab/libs-release@id=openhab
+ https://openhab.jfrog.io/openhab/libs-release@id=openhab, \
+ https://repo1.maven.org/maven2/@id=central
#
# Global policies override repository-specific settings (@checksum=..., @update=..., @releasesUpdate=..., ...)
1 Like
GEOFFg41
(Geoff)
January 22, 2025, 5:58am
8
Hi All
I am having the same issue but on openHAB 5.0.0
Build #4487
I am unable to install any binding because of “Error downloading mvn:com.github.hypfvieh/bluez-dbus-osgi/0.3.1”
Marketplace binding install ok
Is there a solution to this that I can implement
Thanks Geoff
laursen
(Jacob Laursen)
January 22, 2025, 7:16am
9
I think we need @Kai to upload again. See:
openhab:main
← joerg1985:bluez-dbus-osgi-0.3.1
opened 07:33PM - 20 Jan 25 UTC
This PR does update to `bluez-dbus-osgi` version `0.3.1`, as the osgi bundle of … version `0.3.0` is broken.
FYI @lsiepel
<!--
Thanks for contributing to the openHAB project!
Please describe the goal and effect of your PR here.
Pay attention to the below notes and to *the guidelines* for this repository.
Feel free to delete any comment sections in the template (starting with "<!--").
ATTENTION: Don't use "git merge" when working with your pull request branch!
This can clutter your Git history and make your PR unusable.
Use "git rebase" instead. See this forum post for further details:
https://community.openhab.org/t/rebase-your-code-or-how-to-fix-your-git-history-before-requesting-a-pull/129358
All PRs should be created using the "main" branch as base.
Important bugfixes are cherry-picked by maintainers to the patch release branch after a PR has been merged.
Add one or more appropriate labels to make your PR show up in the release notes.
E.g. enhancement, bug, documentation, new binding
This can only be done by yourself if you already contributed to this repo.
If your PR's code is not backward compatible with previous releases (which
should be avoided), add a message to the release notes by filing another PR:
https://github.com/openhab/openhab-distro/blob/main/distributions/openhab/src/main/resources/bin/update.lst
# Title
Provide a short summary in the *Title* above. It will show up in the release notes.
For example:
- [homematic] Improve communication with weak signal devices
- [timemachine][WIP] Initial contribution
# Description
Please give a few sentences describing the overall goals of the pull request.
Give enough details to make the improvement and changes of the PR understandable
to both developers and tech-savy users.
Please keep the following in mind:
- What is the classification of the PR, e.g. Bugfix, Improvement, Novel Addition, ... ?
- Did you describe the PRs motivation and goal?
- Did you provide a link to any prior discussion, e.g. an issue or community forum thread?
- Did you describe new features for the end user?
- Did you describe any noteworthy changes in usage for the end user?
- Was the documentation updated accordingly, e.g. the add-on README?
- Does your contribution follow the coding guidelines:
https://www.openhab.org/docs/developer/guidelines.html
- Did you check for any (relevant) issues from the static code analysis:
https://www.openhab.org/docs/developer/bindings/#include-the-binding-in-the-build
- Did you sign-off your work:
https://www.openhab.org/docs/developer/contributing.html#sign-your-work
# Testing
Your pull request will automatically be built and available under the following folder:
https://openhab.jfrog.io/ui/native/libs-pullrequest-local/org/openhab/addons/bundles/
It is a good practice to add a URL to your built JAR in this pull request description,
so it is easier for the community to test your Add-on.
If your pull request contains a new binding, it will likely take some time
before it is reviewed and processed by maintainers.
That said, consider submitting your Add-on in the Marketplace:
https://community.openhab.org/c/marketplace/69
Don't forget to submit a thread about your Add-on in the openHAB community:
https://community.openhab.org/c/add-ons
-->
GEOFFg41
(Geoff)
January 31, 2025, 11:09am
11
Hi All
I had to restart Openhab as I had issues, so I cleared the cache and Temp folders, and the previous issue has come back
Error downloading mvn:org.eclipse.jetty/jetty-io/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty/jetty-client/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty.websocket/websocket-common/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty.websocket/websocket-client/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty/jetty-http/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty/jetty-proxy/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty/jetty-util/9.4.46.v20220331
Error downloading mvn:org.eclipse.jetty.websocket/websocket-api/9.4.46.v20220331
2025-01-31 18:06:31.947 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed to refresh bundles after processing config update
Hope you can help
Thanks
Geoff