-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OSGi Metadata #280
Comments
@waynebeaton could you please assign me to do this issue ? |
@waynebeaton Does anyone have some requirements? Options:
Here would be my first Draft with bnd-maven plugin:
in pritty Print
|
I wonder about some of the version ranges on the package imports. Guava is currently at version 33.3.0.jre. Many projects have been "working hard" to get rid of guava because they have a bad habit of breaking API and produce new major versions. Ideally this dependency would not be there... JGit released 7.0.0 for 2024-09 so probably best to update that. |
@merks I was looking at Guava just last night. We have a security advisory on the version that gets resolved by the build. I'd been tinkering with forcing the use of an updated version. It's a transitive dependency of Guice. I don't think that I can remove it completely. |
Nice to have.
No opinion.
No opinion beyond the component versioning that is expressed in the pom files.
Nice to have.
Tests are always good. |
All versions are calculated by bnd - so ots just the used versions. PR #377 |
I've updated the Maven build to use this version. |
Unfortunately yes and I proposed dropping at google/guice#1785 and already did some work. But to avoid Guava in this repo I created #386. |
@merks FYI, JGit 7.0.0+ requires Java 17. I didn't notice until the Jenkins build failed. I hesitate to update the JRE requirement without putting some more thought into it, so I'm going to revert to the most recent release in the 6.x stream. I've opened #388 to discuss updating to Java 17. I'm thinking that we should just do it, but want to capture the decision explicitly. |
I see. Yes, as we merrily progress to Java 21 for SimRel, it's easy to overlook that there is also significant merit it running on older versions of Java. For what it's worth, when moving to version 7.x's APIs in Oomph there was only a single deprecated method removed that had an impact.... |
@HannesWell here is no close button for me to close this. could you please |
Thanks for the patch. |
Let's make the core artifact into an OSGi bundle.
The text was updated successfully, but these errors were encountered: