[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220399#comment-16220399
]
Enrico Olivelli edited comment on SUREFIRE-1424 at 10/26/17 1:04 PM:
-
[~tibor17] As you can see I am preparing a patch.
I need an hint.
How can I run the tests on Java9, like Java9FullApiIT ?
cd surefire-integration-tests
JAVA_HOME=/path/tojdk9 mvn verify -Dit.test=Java9FullApiIT
the build fails as there is the enforcer plugin which prevents execution on
java9, I have temporary disable that check but then I think that there is some
toolchain setup to do as test fails.
Do you have any doc on how to setup the env or can you give me some hint ?
regarding the documentation, I think that the list of dependencies should not
go into surefire docs but in maven general documentation or even it is a
problem of OpenJDK itseft
was (Author: eolivelli):
[~tibor17] As you can see I am preparing a patch.
I need an hint.
How can I run the tests on Java9, like Java9FullApiIT ?
cd surefire-integration-tests
JAVA_HOME=~/dev/jdk-9 mvn verify -Dit.test=Java9FullApiIT
the build fails as there is the enforcer plugin which prevents execution on
java9, I have temporary disable that check but then I think that there is some
toolchain setup to do as test fails.
Do you have any doc on how to setup the env or can you give me some hint ?
regarding the documentation, I think that the list of dependencies should not
go into surefire docs but in maven general documentation or even it is a
problem of OpenJDK itseft
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220270#comment-16220270
]
Enrico Olivelli edited comment on SUREFIRE-1424 at 10/26/17 10:14 AM:
--
[~krzyk] you should simply add --add-modules=java.sql
AFAIK java.sql is not "deprecated" and will not be removed from JRE
you can do it using a profile which is activated only on Java9 and adds such
parameter to the argLine of surefire
was (Author: eolivelli):
[~krzyk] you should simply add --add-modules=java.sql
ASAIK java.sql is not "deprecated" and will not be removed from JRE
you can do it using a profile which is activated only on Java9 and adds such
parameter to the argLine of surefire
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213859#comment-16213859
]
Tibor Digana edited comment on SUREFIRE-1424 at 10/21/17 11:50 AM:
---
[~eolivelli]
Flag=config param means for me that this configuration would be obsolete in
Java 10, and I do not want to maintain one more parameter, therefore I vote to
drop the feature {{-add-modules java.ee.se}} of version 2.20.1 and commit the
removal in 2.21.0.Jigsaw. Of course old documentation should stay and a new one
should be added related to 2.21.0.
We already have too many configuration parameters, so better to drop this and
throw exception on Build Error (if any test fails) with clear link to our
documentation (if Java specification version >= 9).
The documentation in Surefire should mention on how to use Maven profiles,
{{-add-modules java.ee.se}} in {{argLine}} for version 2.21.0 or higher, Maven
dependencies substituting removed API and implementation, and a link to Jigsaw
doc where Oracle must update it.
If somebody removes a feature, he should obviously take care of writing
documentation which gives the user alternatives and contact the communities
about consequencies.
was (Author: tibor17):
[~eolivelli]
Flag=config param means for me that this configuration would be obsolete in
Java 10, and I do not want to maintain one more parameter, therefore I vote to
drop the feature {{-add-modules java.ee.se}} of version 2.20.1 and commit the
removal in 2.21.0.Jigsaw. Of course old documentation should stay and a new one
should be added related to 2.21.0.
We already have too many configuration parameters, so better to drop this and
throw exception on Build Error (if any test fails) with clear link to our
documentation (if Java specification version >= 9).
The documentation in Surefire should mention on how to use Maven profiles,
{{-add-modules java.ee.se}} in {{argLine}} for version 2.21.0 or higher, Maven
dependencies substituting removed API and implementation, and a link to Jigsaw
which Oracle must be update.
If somebody removes a feature, he should obviously take care of writing
documentation which gives the user alternatives and contact the communities
about consequencies.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213859#comment-16213859
]
Tibor Digana edited comment on SUREFIRE-1424 at 10/21/17 11:49 AM:
---
[~eolivelli]
Flag=config param means for me that this configuration would be obsolete in
Java 10, and I do not want to maintain one more parameter, therefore I vote to
drop the feature {{-add-modules java.ee.se}} of version 2.20.1 and commit the
removal in 2.21.0.Jigsaw. Of course old documentation should stay and a new one
should be added related to 2.21.0.
We already have too many configuration parameters, so better to drop this and
throw exception on Build Error (if any test fails) with clear link to our
documentation (if Java specification version >= 9).
The documentation in Surefire should mention on how to use Maven profiles,
{{-add-modules java.ee.se}} in {{argLine}} for version 2.21.0 or higher, Maven
dependencies substituting removed API and implementation, and a link to Jigsaw
which Oracle must be update.
If somebody removes a feature, he should obviously take care of writing
documentation which gives the user alternatives and contact the communities
about consequencies.
was (Author: tibor17):
[~eolivelli]
Flag=config param means for me that this configuration would be obsolete in
Java 10, and I do not want to maintain one more parameter, therefore I vote to
drop the feature {{-add-modules java.ee.se}} of version 2.20.1 and commit the
removal in 2.21.0.Jigsaw. Of course old documentation should stay and a new one
should be added related to 2.21.0.
We already have too many configuration parameters, so better to drop this and
throw exception on Build Error (if any test fails) with clear link to our
documentation (if Java specification version >= 9).
The documentation in Surefire should mention on how to use Maven profiles,
{{-add-modules java.ee.se}} in {{argLine}} for version 2.21.0 or higher, Maven
dependencies substituting removed API and implementation, and a link to Jigsaw
which Oracle must be updated.
If somebody removes a feature, he should obviously take care of writing
documentation which gives the user alternatives and contact the communities
about consequencies.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213718#comment-16213718
]
Julian Reschke edited comment on SUREFIRE-1424 at 10/21/17 4:00 AM:
bq. IIYUC you say that you added javax.transaction.UserTransaction via Maven
dependency on classpath but because of Java 9 already associated
javax.transaction package with internal module having same module/package name
as in your dependency, your dependency does not take precedence?
Yes.
bq. How many decisions the new configuration should do?
Not sure what you're getting at. The current situation where
{{\-\-add-modules}} is added silently definitively causes harm in cases like
this, though. An override would be appreciated.
was (Author: reschke):
> IIYUC you say that you added javax.transaction.UserTransaction via Maven
> dependency on classpath but because of Java 9 already associated
> javax.transaction package with internal module having same module/package
> name as in your dependency, your dependency does not take precedence?
Yes.
> How many decisions the new configuration should do?
Not sure what you're getting at. The current situation where
{{\-\-add-modules}} is added silently definitively causes harm in cases like
this, though. An override would be appreciated.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16213145#comment-16213145
]
Julian Reschke edited comment on SUREFIRE-1424 at 10/20/17 8:04 PM:
[~tibor17] - the problem is the default of adding {{\-\-add-modules}} under
Java 9. Because it does, {{javax.transaction.UserTransaction}} becomes
invisible, *although* it is on the classpath. My workaround is to set
{\{-\-add-modules java.xml.bind}}, so that surefire does not add
{{\-\-add-modules}} itself. A config parameter that disables this behavior
would help a lot.
If you want to reproduce this, checkout
https://svn.apache.org/repos/asf/jackrabbit/trunk/ with a revision prior to
http://svn.apache.org/r1812634, and then try to build with jdk-9.
was (Author: reschke):
[~tibor17] - the problem is the default of adding "--add-modules" under Java 9.
Because it does, javax.transaction.UserTransaction becomes invisible,
*although* it is on the classpath. My workaround is to set "--add-modules
java.xml.bind", so that surefire does not add "--add-modules" itself.
If you want to reproduce this, checkout
https://svn.apache.org/repos/asf/jackrabbit/trunk/ with a revision prior to
http://svn.apache.org/r1812634, and then try to build with jdk-9.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210846#comment-16210846
]
Alan Bateman edited comment on SUREFIRE-1424 at 10/19/17 10:27 AM:
---
It's the same issue. If you run with - -add-modules $XXX where XXX is any of
"java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll load
the java.transaction module from the JDK. I think you are instead hoping that
the Java Transaction classes on the class path will be loaded and this will
work if the - -add-modules is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with - -add-modules to use
the java.transaction in the JDK unwinds that, and makes it harder to upgrade.
was (Author: alanbateman):
It's the same issue. If you run with {{-add-modules $XXX` where XXX }} is any
of "java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll
load the java.transaction module from the JDK. I think you are instead hoping
that the Java Transaction classes on the class path will be loaded and this
will work if the {{-add-modules}} is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with {{-add-modules}} to use
the java.transaction in the JDK unwinds that, and makes it harder to upgrade.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210846#comment-16210846
]
Alan Bateman edited comment on SUREFIRE-1424 at 10/19/17 10:27 AM:
---
It's the same issue. If you run with {{-add-modules $XXX` where XXX }} is any
of "java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll
load the java.transaction module from the JDK. I think you are instead hoping
that the Java Transaction classes on the class path will be loaded and this
will work if the {{-add-modules}} is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with {{-add-modules}} to use
the java.transaction in the JDK unwinds that, and makes it harder to upgrade.
was (Author: alanbateman):
It's the same issue. If you run with {{--add-modules $XXX` where XXX }} is any
of "java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll
load the java.transaction module from the JDK. I think you are instead hoping
that the Java Transaction classes on the class path will be loaded and this
will work if the {{--add-modules}} is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with {{--add-modules}} to
use the java.transaction in the JDK unwinds that, and makes it harder to
upgrade.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210846#comment-16210846
]
Alan Bateman edited comment on SUREFIRE-1424 at 10/19/17 10:26 AM:
---
It's the same issue. If you run with {{--add-modules $XXX` where XXX }} is any
of "java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll
load the java.transaction module from the JDK. I think you are instead hoping
that the Java Transaction classes on the class path will be loaded and this
will work if the {{--add-modules}} is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with {{--add-modules}} to
use the java.transaction in the JDK unwinds that, and makes it harder to
upgrade.
was (Author: alanbateman):
It's the same issue. If you run with `--add-modules $XXX` where XXX is any of
"java.transaction", "java.corba", "java.se.ee" or "ALL-SYSTEM" then you'll load
the java.transaction module from the JDK. I think you are instead hoping that
the Java Transaction classes on the class path will be loaded and this will
work if the `--add-modules` is dropped.
This will all be much similar once the JDK jettisons these modules, the first
steps in that direction happened in JDK 9. Running with `--add-modules` to use
the java.transaction in the JDK unwinds that, and makes it harder to upgrade.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 9:20 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
your JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module {{java.base}} in
{{argLine}} and {{.mvn/jvm.config}} or add dependency {{javax:javaee-api:7.0}}
with {{test}} scope in you POM.
Another issue is that Java API is not exposed however it is inside of JRE.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications
because these two modules are a pure set of utilities and not managed by
container. The plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
your JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposed however it is inside of JRE.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications
because these two modules are a pure set of utilities and not managed by
container. The plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
>
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:43 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
your JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposed however it is inside of JRE.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications
because these two modules are a pure set of utilities and not managed by
container. The plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
your JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:37 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
your JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:34 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
such modules from Oracle web page + let the user install extensions in JRE.
Thus the user will have a chance to recover broken compatibility.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
from Oracle web page + install it in JRE. Thus the user will have a chance to
recover broken compatibility.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:33 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism and such JTA JAR/module does not exist and the only thing is to
apply {{--add-modules java.se.ee}} or any other module in {{.mvn/jvm.config}}
or add dependency {{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
If Oracle wants to delete some APIs then they should introduce a mechanism to
{{extend}} JRE and segregate deleted JAR modules with deleted API to download
from Oracle web page + install it in JRE. Thus the user will have a chance to
recover broken compatibility.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add dependency
{{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:28 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module in
you JRE installation, this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add dependency
{{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module,
this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add dependency
{{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:26 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module,
this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add dependency
{{javax:javaee-api:7.0}} with {{test}} scope in you POM.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module,
this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add
{{javax:javaee-api:7.0}}.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184813#comment-16184813
]
Tibor Digana edited comment on SUREFIRE-1424 at 9/28/17 8:25 PM:
-
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module,
this could extend Java SE API with JTA from Java EE7.
This mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add
{{javax:javaee-api:7.0}}.
Another issue is that Java API is not exposes however it is inside.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
was (Author: tibor17):
I added {{--add-modules java.se.ee}} to Version {{2.20.1}} because we wanted to
fix such ClassLoader issues reported in Jira.
This is not a regression and not a bug in Surefire. This is actually problem
with Oracle because broke backwards compatibility. Several years ago Oracle
planned to design JDK in a way that JDK would be extensible. So if you imaging
that you put {{javax}} extensions JAR {{javax.transctions.jar}} as a module,
this could extend Java SE API with JTA from Java EE7.
Another issue is that Java API is not exposes however it is inside. This
mechanism does not exist and the only thing is to apply {{--add-modules
java.se.ee}} or any other module in {{.mvn/jvm.config}} or add
{{javax:javaee-api:7.0}}.
Oracle says that {{javax.xml.bind}} and {{javax.activation}} is EE related. I
disagree. This is also SE and people use it in console Swing applications. The
plan is to delete several APIs.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>Assignee: Tibor Digana
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1424) javax.transaction.TransactionManager not visible with Java9
[
https://issues.apache.org/jira/browse/SUREFIRE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180527#comment-16180527
]
Andy Wilkinson edited comment on SUREFIRE-1424 at 9/26/17 9:24 AM:
---
This appears to be a regression in 2.20.1. The sample linked above works with
Surefire 2.20 but fails with 2.20.1. With 2.20.1, the JVM is launched with
{{--add-modules java.se.ee}} but with 2.20 it is not. Adding the {{java.se.ee}}
module breaks JTA as only some of its classes are in that module. This split
package leads to the {{NoClassDefFoundError}} reported above. This would appear
to be an unanticipated side-effect of SUREFIRE-1403.
was (Author: awilkinson):
This appears to be a regression in 2.20.1. The sample linked above works with
Surefire 2.20 but fails with 2.20.1. With 2.20.1, the JVM is launched with
{{--add-modules java.se.ee}} but with 2.20 it is not. Adding the {{java.se.ee}}
module breaks JTA as only some of its classes at in the module. This split
package leads to the {{NoClassDefFoundError}} reported above. This would appear
to be an unanticipated side-effect of SUREFIRE-1403.
> javax.transaction.TransactionManager not visible with Java9
> ---
>
> Key: SUREFIRE-1424
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1424
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Maven home: /Users/snicoll/tools/maven
> Java version: 9, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home
> Default locale: en_BE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Stephane Nicoll
>
> I am trying to port Spring Boot to Java9 and I am hitting an issue that looks
> like Maven specific. I've managed to trim down the problem to [a simple class
> that doesn't involve Spring
> Boot|https://github.com/snicoll-scratches/test-jta-java9]
> If I run this project on the command line, I get the following:
> {noformat}
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.043 s <<<
> FAILURE! - in com.example.testjtajava9.TestJtaJava9ApplicationTests
> contextLoads(com.example.testjtajava9.TestJtaJava9ApplicationTests) Time
> elapsed: 0.006 s <<< ERROR!
> java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> Caused by: java.lang.ClassNotFoundException:
> javax.transaction.TransactionManager
> at
> com.example.testjtajava9.TestJtaJava9ApplicationTests.contextLoads(TestJtaJava9ApplicationTests.java:9)
> {noformat}
> If I run that test with IntelliJ IDEA, it passes. This sample project has
> also a simple Gradle build that shows it works with Gradle as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
