Can I exclude an exported package from a Java module?

血红的双手。 提交于 2019-11-30 20:26:43

The JTA GitHub reads the following in confirmation to what @Alan already pointed out in a comment -

This standalone release of Java(TM) Java Transaction API (JTA), uses a Java Platform Module System "automatic" module name of java.transaction, to match the module name used in JDK 9. A future version will include full module metadata. Moreover javax.transaction.xa package is now owned by Java SE.

You can use the version with Maven(e.g) using :-

<dependency>
    <groupId>javax.transaction</groupId>
    <artifactId>javax.transaction-api</artifactId>
    <version>1.3</version>
</dependency>

Here is the release notes for JTA1.3MR.


Additionally the JEP 320: Remove the Java EE and CORBA Modules elaborates on the same -

... The javax.transaction.xa package supports XA transactions in JDBC. This "XA package" is co-located with JDBC in the java.sql module in Java SE 9. Because the java.sql module is not upgradeable, it is not possible for a standalone version of JTA to override the Java SE version of the XA package

and to further note for extensibility in your solution

...For ease of maintenance, the XA package in Java SE may be moved to a different non-upgradeable module in the future, but as an architectural matter it will remain in Java SE alongside JDBC for the long term...

and as planned

In early 2018, JTA 1.3 will be defined to consist of just the CORBA interop package; the JAR file will be updated accordingly.

tiitan

You could use javac -d -cp /PATHTOYOURFILE -d and -cp flags to compile only required directories and classpath. Classpath can also be comma seperated.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!