-
Notifications
You must be signed in to change notification settings - Fork 423
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
Upgrade to the latest OSGi JDBC specification #2017
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding the properties and covering it bY osgi tck
Hi @laeubi, We'll look into this, confirm whether these are all the changes we need to make spec, and get back to you. Thank you for your contribution. |
Hi @laeubi, I'm unable to find the specification you're referring to. Do you happen to have a link? |
@Jeffery-Wasty no problem the specification is located here: https://docs.osgi.org/specification/osgi.cmpn/8.1.0/service.jdbc.html previous version(s): |
I see that OSGI compendium on maven has migrated to here: https://mvnrepository.com/artifact/org.osgi/osgi.cmpn, which is probably why we're still using version 5. We missed that the page had changed. However, this page only has up to version 7, is there a maven repository for compendium 8? |
R8 do not has a "fat compendium jar" anymore but many small dedicated items and therefore uses
now. |
I see, thank you. And thanks for the quick reply! |
Hi @laeubi, The dependency changes are causing test failures, as seen below, coming from the |
@Jeffery-Wasty I'll try to take a look the next days, I think I might perform the upgrade in smaller steps to see whats going on here... |
@Jeffery-Wasty I have now started with a very minimal change, that just upgrades to the new artifact location from central: It would be great if you can take a look, probably this could even be merged already as a first step. |
I created another one that do the actual code changes here: with those it should be possible to see if that alone causes any issues |
And finally we have the test execution added here: |
Thanks @laeubi, we'll take a look at each of the PRs you have linked. |
As stated in #2066, lets use this as the sole PR. If you're able to fix the test to not use Junit5 it can be included, otherwise we'll move forward without it. |
I fear the test requires JUnit5 |
My only idea is that one probabbly can create a new module that only contains this single test ... but the repo seems not really a multi-module one... so for now then we should go without the test. |
I see, thank you for looking into this. If we end up being able to use Junit5 moving forward, we can revisit adding the test on, its always good to have additional testing. For now, if we can ask you to push a commit removing the test, we can review the PR and get it merged. |
973961e
to
cdd04be
Compare
Now everything should be cleaned up and rebased |
cdd04be
to
c135923
Compare
In the latest release of the JDBC specification there was a requirement added that datasources should promote what methods they implement. mssql-jdbc implements all methods and could therefore promote all. This also migrates from the org.osgi.enterprise artifact to the more specific org.osgi.service.jdbc one and adds the official TCK test as part of the JUnit-Suite.
c135923
to
5e542c6
Compare
In the latest release of the JDBC specification there was a requirement added that datasources should promote what methods they implement. mssql-jdbc implements all methods and could therefore promote all.
This also migrates from the org.osgi.enterprise artifact to the more specific org.osgi.service.jdbc one and adds the official TCK test as part of the JUnit-Suite.
FYI @stbischof