-
Notifications
You must be signed in to change notification settings - Fork 25
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
Wrong OSGi relation between JCA 1.7 and JTA 1.3 (JavaEE8, JakartaEE8) #120
Comments
Could you create a PR to review and I can investigate how to get a service release out there? |
Sure - I'll prepare it tomorrow (CET time here) |
Hmm, I'm a bit confused with the branches... In theory, https://github.com/eclipse-ee4j/jca-api/tree/EE4J_8 branch should be used for JCA 1.7 work. However this branch' pom contains version However both |
…ith [1.2,2) OSGi version range Signed-off-by: Grzegorz Grzybek <[email protected]>
If the 1.7.x branch was created starting with 1.7.4 tag, I'd create a PR from https://github.com/grgrzybek/jca-api/commits/1.7.x branch. |
See also jakartaee/transactions#186 |
…32 is resolved
I'm working on https://github.com/ops4j/org.ops4j.pax.transx OSGi project and I want to polish the dependencies related to different JavaEE APIs.
I also maintain my own matrix of versions (no JavaEE 9 yet) here
There is some confusion about JTA 1.2/1.3 and JCA 1.7 versions
However I checked available Maven central artifacts:
javax.resource/javax.resource-api/1.7
hasImport-Package: ...,javax.transaction;version="[1.2,1.3)",javax.transaction.xa;version="[1.2,1.3)"
javax.resource/javax.resource-api/1.7.1
hasImport-Package: ...,javax.transaction;version="[1.3,2.0)",javax.transaction.xa
jakarta.resource/jakarta.resource-api/1.7.4
hasImport-Package: ...,javax.transaction;version="[1.3,2.0)",javax.transaction.xa
However each of the above has some problems...
javax.transaction
and JakartaEE8 should be compatible with JavaEE8, so the range should be[1.2,2)
doc-files
package which is a result of wrong maven-bundle-plugin configurationThe text was updated successfully, but these errors were encountered: