You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "laingke (via GitHub)" <gi...@apache.org> on 2023/06/04 07:51:04 UTC

[GitHub] [shardingsphere] laingke opened a new issue, #26041: Transition from Java EE to Jakarta EE

laingke opened a new issue, #26041:
URL: https://github.com/apache/shardingsphere/issues/26041

   ## Feature Request
   
   **For English only**, other languages will not be accepted.
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response anymore and we cannot make decision by current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Is your feature request related to a problem?
   
   No
   
   ### Describe the feature you would like.
   
   After Jakarta EE 9 has been released, The group id `javax-***` is no longer maintained, it would be a good idea to migrate `javax` to `jakarta` namespace.
   
   The following GAVs are mentioned in shardingsphere:
   
   ```xml
   <dependency>
       <groupId>javax.transaction</groupId>
       <artifactId>jta</artifactId>
   </dependency>
   <dependency>
       <groupId>javax.annotation</groupId>
       <artifactId>javax.annotation-api</artifactId>
   </dependency>
   <dependency>
       <groupId>javax.xml.bind</groupId>
       <artifactId>jaxb-api</artifactId>
   </dependency>
   <dependency>
       <groupId>javax.activation</groupId>
       <artifactId>javax.activation-api</artifactId>
   </dependency>
   ```
   
   Here is the latest version until May 30th, 2023:
   
   ```xml
   <dependency>
       <groupId>jakarta.transaction</groupId>
       <artifactId>jakarta.transaction-api</artifactId>
       <version>2.0.1</version>
   </dependency>
   <dependency>
       <groupId>jakarta.annotation</groupId>
       <artifactId>jakarta.annotation-api</artifactId>
       <version>2.1.1</version>
   </dependency>
   <dependency>
       <groupId>jakarta.xml.bind</groupId>
       <artifactId>jakarta.xml.bind-api</artifactId>
       <version>4.0.0</version>
   </dependency>
   <dependency>
       <groupId>jakarta.activation</groupId>
       <artifactId>jakarta.activation-api</artifactId>
       <version>2.1.2</version>
   </dependency>
   ```
   
   Refs:
   [Jakarta EE Maven Coordinates](https://wiki.eclipse.org/Jakarta_EE_Maven_Coordinates)
   [Transition from Java EE to Jakarta EE](https://blogs.oracle.com/javamagazine/post/transition-from-java-ee-to-jakarta-ee)
   [Javax to Jakarta Namespace Ecosystem Progress](https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1815869031

   I test with `quarkus-shardingsphere-jdbc` and it fails to start the application
   
   ```
   Caused by: java.lang.RuntimeException: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
   	at io.quarkus.hibernate.orm.runtime.JPAConfig.startAll(JPAConfig.java:78)
   	at io.quarkus.hibernate.orm.runtime.HibernateOrmRecorder.startAllPersistenceUnits(HibernateOrmRecorder.java:101)
   	at io.quarkus.deployment.steps.HibernateOrmProcessor$startPersistenceUnits1868654632.deploy_0(Unknown Source)
   	at io.quarkus.deployment.steps.HibernateOrmProcessor$startPersistenceUnits1868654632.deploy(Unknown Source)
   	... 13 more
   Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
   	at org.apache.shardingsphere.mode.repository.standalone.jdbc.JDBCRepository.init(JDBCRepository.java:59)
   	at org.apache.shardingsphere.infra.spi.type.typed.TypedSPILoader.findService(TypedSPILoader.java:61)
   	at org.apache.shardingsphere.infra.spi.type.typed.TypedSPILoader.getService(TypedSPILoader.java:110)
   	at org.apache.shardingsphere.mode.manager.standalone.NewStandaloneContextManagerBuilder.build(NewStandaloneContextManagerBuilder.java:48)
   	at org.apache.shardingsphere.driver.jdbc.core.datasource.ShardingSphereDataSource.createContextManager(ShardingSphereDataSource.java:78)
   	at org.apache.shardingsphere.driver.jdbc.core.datasource.ShardingSphereDataSource.<init>(ShardingSphereDataSource.java:66)
   	at org.apache.shardingsphere.driver.api.ShardingSphereDataSourceFactory.createDataSource(ShardingSphereDataSourceFactory.java:95)
   	at org.apache.shardingsphere.driver.api.yaml.YamlShardingSphereDataSourceFactory.createDataSource(YamlShardingSphereDataSourceFactory.java:167)
   	at org.apache.shardingsphere.driver.api.yaml.YamlShardingSphereDataSourceFactory.createDataSource(YamlShardingSphereDataSourceFactory.java:102)
   	at org.apache.shardingsphere.driver.jdbc.core.driver.DriverDataSourceCache.createDataSource(DriverDataSourceCache.java:52)
   	at org.apache.shardingsphere.driver.jdbc.core.driver.DriverDataSourceCache.lambda$get$0(DriverDataSourceCache.java:46)
   	at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708)
   	at org.apache.shardingsphere.driver.jdbc.core.driver.DriverDataSourceCache.get(DriverDataSourceCache.java:46)
   	at org.apache.shardingsphere.driver.ShardingSphereDriver.connect(ShardingSphereDriver.java:53)
   	at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:226)
   	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:536)
   	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:517)
   	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   	at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:75)
   	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
   	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
   	at java.base/java.lang.Thread.run(Thread.java:833)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1815872070

   It seems that when quarkus build the application, it will exclude the old Java EE artifacts like `javax.xml.bind:jaxb-api`. Is there any plan to bump to Jakarata EE 10? It's a uncompatitable change from the package name `javax.` -> `jakarta.`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] laingke commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "laingke (via GitHub)" <gi...@apache.org>.
laingke commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1580523519

   @linghengqian I recently refactored the BTM project(with the latest dependies) https://github.com/laingke/btm , and an unofficial version may be released in the future. Is it possible for shardingsphere to integrate an unofficial artifact?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1577177848

   - @FlyingZC Hi, I noticed that Bitronix's repository has been archived, refer to https://github.com/bitronix/btm and https://shardingsphere.apache.org/document/5.3.2/en/dev-manual/transaction/ .  
   
   - Engineers at Software AG abandoned Bitronix in favor of Ehcache for distributed transactions.  Should we remove Bitronix-related code for this issue?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1580670032

   > @linghengqian I recently refactored the BTM project(with the latest dependies) https://github.com/laingke/btm , and an unofficial version may be released in the future. Is it possible for shardingsphere to integrate an unofficial artifact?
   
   - I think there is no problem, because Bitronix is ​​only one of the implementations of a specific SPI in ShardingSphere.  For other implementations, as long as the LICENSE is allowed by ASF, they can be included directly.  
   
   - From this point, as mentioned in https://github.com/bitronix/btm/issues/107, one of Bitronix's downstream https://github.com/mulesoft/btm/tree/support/2.1.x cannot exist in the git of ShardingSphere because of GPL LICENSE.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1696078463

   - On https://github.com/linghengqian/shardingsphere-v540-readwrite-splitting-test corresponding to commit https://github.com/linghengqian/shardingsphere-v540-readwrite-splitting-test/commit/a1203203db1d421452b8b465b58003224a936836 , I created some tests for Spring Boot OSS 3.1.2.  Except for XA distributed transactions, ordinary functions can be used normally.
   
   - The required dependencies may not be obvious, maybe I should create a documentation PR to clarify up front.
   ```xml
           <dependency> 
                <groupId>org.apache.shardingsphere</groupId> 
                <artifactId>shardingsphere-jdbc-core</artifactId> 
                <version>5.4.0</version> 
            </dependency> 
            <dependency> 
                <groupId>org.yaml</groupId> 
                <artifactId>snakeyaml</artifactId> 
                <version>1.33</version> 
            </dependency> 
            <dependency> 
                <groupId>org.glassfish.jaxb</groupId> 
                <artifactId>jaxb-runtime</artifactId> 
                <version>2.3.8</version> 
            </dependency>
   ```
   - I'm still not sure if I should merge https://github.com/apache/shardingsphere/pull/27976 before Spring Boot OSS 2.7.x ends community support (`2023-11-18`).  On the ShardingSphere side, issues from Spring Boot 2.x have increased recently.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] laingke commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "laingke (via GitHub)" <gi...@apache.org>.
laingke commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1581880874

   > > @linghengqian I recently refactored the BTM project(with the latest dependies) https://github.com/laingke/btm , and an unofficial version may be released in the future. Is it possible for shardingsphere to integrate an unofficial artifact?
   > 
   > * I think there is no problem, because Bitronix is ​​only one of the implementations of a specific SPI in ShardingSphere.  For other implementations, as long as the LICENSE is allowed by ASF, they can be included directly.
   
   That is OK, since 3.0.0-SNAPSHOT, Bitronix licensed with APACHE LICENSE 2.0.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] FlyingZC commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "FlyingZC (via GitHub)" <gi...@apache.org>.
FlyingZC commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1580103335

   @linghengqian I personally agree with the removal, atomikos and naryana are enough, and bitronix has not been maintained for a long time.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1815891001

   Or is it possible to implement a memory only repostitory? like `MemoryRepository` which does not depend on any other external persistent storage.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] github-actions[bot] commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1738008442

   There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816271860

   Well, these `javax` -> `jakarta` changes are uncompatitable and I think it needs a majar bump version to shardingsphere like `6.0.0`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1973838559

   There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816217787

   > Or is it possible to implement a memory only repostitory? like `MemoryRepository` which does not depend on any other external persistent storage.
   
   - This may be a bit troublesome. There are many modules that need to be parsed through JAXB API. Please refer to https://github.com/apache/shardingsphere/pull/29013 .  
   
   - Of course shardingsphere can be migrated to Jakarta EE 9 right away to fix this issue, it just requires me to fix #27976 .  
   
   - Merging #27976 will mean that in the existing shardingsphere example module, the spring boot example module needs to use JDK17+ to run.  We also need to declare that support for XA distributed transactions will be dropped on spring boot 2.x.  Considering that Spring Boot 2.x will end OSS support this month, and shardingsphere will release 5.4.2 in December this year, should I merge #27976 on the current version milestone?  Or merge #27976 on shardingsphere 5.4.3 or shardingsphere 5.5.0?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816375449

   > So @linghengqian are you working on this migration?
   
   - I will rebase #27976 in the next few days and ask for review.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816266920

   - According to the dependencies of `org.glassfish.jaxb:jaxb-runtime:2.3.9`, is it feasible to only do the following? The following dependencies are still in the Java EE 8 namespace, but the GAV of the corresponding dependencies is migrated to Eclipse.
   - `javax.xml.bind:jaxb-api:2.3.1` to `jakarta.xml.bind:jakarta.xml.bind-api:2.3.3`
   - `javax.activation:javax.activation-api:1.2.0` to `jakarta.activation:jakarta.activation-api:1.2.2`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] laingke commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "laingke (via GitHub)" <gi...@apache.org>.
laingke commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1631631380

   > - @laingke Hi, I would like to inquire if I can remove the btm related code from ShardingSphere now to resolve the issue https://github.com/apache/shardingsphere/issues/26896 ? 
   > 
   > - It seems unlikely that [laingke/btm](https://github.com/laingke/btm) will release its first version before the release of ShardingSphere 5.4.1.
   
   That is OK, my version still need 1 or 2 month to develop.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1575627857

   @laingke Hey, this issue is blocked at https://github.com/atomikos/transactions-essentials/issues/171. If we need to remove all of the Atomikos-related unit tests because of a namespace change, this is an issue that has to be put on the mailing list.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816285811

   So @linghengqian are you working on this migration?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1852527057

   > Or is it possible to implement a memory only repostitory? like `MemoryRepository` which does not depend on any other external persistent storage.
   
   - #27976 remains external controversy and #27976 is proposed to delay the merger by me.
   
   - I noticed the uselessness of the JAXB API while investigating #29209, and I'm now opening #29384.
   
   - #29384 removed all use of the JAXB API, retaining use only in test modules. I think this will provide an out-of-the-box experience for `Spring Boot OSS 3`/`Quarkus 3`/`Micronaut Framework 4`/`Helidon 3` users.
   
   - XA distributed transactions are still not ready on `Spring Boot OSS 3`/`Quarkus 3`/`Micronaut Framework 4`/`Helidon 3`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1668644513

   - @laingke @KouShenhai @xiaogang-github The migration to Jakarta EE 9 is already in https://github.com/apache/shardingsphere/pull/27976 . 
   
   - Assuming you are using Spring Boot OSS 3/Quarkus 3. Jakarta EE 9.1/10 users can test this PR-related branch.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] linghengqian commented on issue #26041: Transition from Java EE to Jakarta EE

Posted by "linghengqian (via GitHub)" <gi...@apache.org>.
linghengqian commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1631182028

   - @laingke Hi, I would like to inquire if I can remove the btm related code from ShardingSphere now to resolve the issue https://github.com/apache/shardingsphere/issues/26896 ? 
   - It seems unlikely that [laingke/btm](https://github.com/laingke/btm) will release its first version before the release of ShardingSphere 5.4.1.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816282163

   There is only `shardingsphere-standalone-mode-repository-jdbc` uses jaxb. All of others are test. And it seems it's only used to parse the configuration files like `H2.xml` internally. So it might not impact users?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Transition from Java EE to Jakarta EE [shardingsphere]

Posted by "zhfeng (via GitHub)" <gi...@apache.org>.
zhfeng commented on issue #26041:
URL: https://github.com/apache/shardingsphere/issues/26041#issuecomment-1816325150

   Just FYI, narayana 7.0.0.Final has been moved to support Jakara EE 10 and change the license to `Apache License V2.0`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org