[JBoss JIRA] (JGRP-2022) XSD schemas do not properly validate
by Manuel Dominguez Sarmiento (JIRA)
[ https://issues.jboss.org/browse/JGRP-2022?page=com.atlassian.jira.plugin.... ]
Manuel Dominguez Sarmiento commented on JGRP-2022:
--------------------------------------------------
You're thinking of XML validation, not XSD (schema) validation. The resources are valid XML, however they are invalid XSD.
Create a new project in Eclipse (any kind will do), and make sure you have XML Schema Validator turned on (Preferences -> Validation -> check that "XML Schema Validator" is enabled). Copy the three attached files into the project, and you will get the following errors as soon as validation completes:
src-resolve.4.1: Error resolving component 'RelayConfigurationType'. It was detected that 'RelayConfigurationType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/relay.xsd'. If 'RelayConfigurationType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'RelayConfigurationType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/relay.xsd'.
src-resolve.4.1: Error resolving component 'ConfigType'. It was detected that 'ConfigType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/jgroups.xsd'. If 'ConfigType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'ConfigType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/jgroups.xsd'.
src-resolve.4.1: Error resolving component 'ForkStacksType'. It was detected that 'ForkStacksType' has no namespace, but components with no target namespace are not referenceable from schema document 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/fork-stacks.xsd'. If 'ForkStacksType' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'ForkStacksType' has no namespace, then an 'import' without a "namespace" attribute should be added to 'file:///Users/Manuel/Development/workspace-mars/Test/WebContent/fork-stacks.xsd'.
> XSD schemas do not properly validate
> ------------------------------------
>
> Key: JGRP-2022
> URL: https://issues.jboss.org/browse/JGRP-2022
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.8
> Reporter: Manuel Dominguez Sarmiento
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
> Attachments: fork-stacks.xsd, jgroups.xsd, relay.xsd
>
>
> Affected resources:
> - jgroups.xsd
> - relay.xsd
> - fork-stacks.xsd
> Paste these files into an Eclipse project, or run them through Oxygen XML or any other XML / XSD validator, you will get errors relating to src-resolve.4.1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JGRP-2022) XSD schemas do not properly validate
by Manuel Dominguez Sarmiento (JIRA)
[ https://issues.jboss.org/browse/JGRP-2022?page=com.atlassian.jira.plugin.... ]
Manuel Dominguez Sarmiento updated JGRP-2022:
---------------------------------------------
Attachment: relay.xsd
jgroups.xsd
fork-stacks.xsd
> XSD schemas do not properly validate
> ------------------------------------
>
> Key: JGRP-2022
> URL: https://issues.jboss.org/browse/JGRP-2022
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.8
> Reporter: Manuel Dominguez Sarmiento
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
> Attachments: fork-stacks.xsd, jgroups.xsd, relay.xsd
>
>
> Affected resources:
> - jgroups.xsd
> - relay.xsd
> - fork-stacks.xsd
> Paste these files into an Eclipse project, or run them through Oxygen XML or any other XML / XSD validator, you will get errors relating to src-resolve.4.1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (DROOLS-1076) Initial opening of kie navigator server properties shows error dialog
by Tomas David (JIRA)
Tomas David created DROOLS-1076:
-----------------------------------
Summary: Initial opening of kie navigator server properties shows error dialog
Key: DROOLS-1076
URL: https://issues.jboss.org/browse/DROOLS-1076
Project: Drools
Issue Type: Bug
Components: eclipse plugin
Environment: JBoss Developer Studio 9.1.0.Beta2
Drools plugin 6.4.0.201601201107
Reporter: Tomas David
Assignee: Robert (Bob) Brodt
Priority: Minor
Attachments: kn_server_prop_error.png
If you open server properties of the the kie navigator tool, you will get error dialog "The currently displayed page contains invalid values". This happens only when you create new server in server view and then you open server properties in kie navigator view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6303) RemotingLoginModuleTestCase fails with the latest IBM jdk 20160108_01(SR2 FP10)
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-6303?page=com.atlassian.jira.plugin.... ]
Martin Choma moved JBEAP-3623 to WFLY-6303:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6303 (was: JBEAP-3623)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.ER6)
> RemotingLoginModuleTestCase fails with the latest IBM jdk 20160108_01(SR2 FP10)
> -------------------------------------------------------------------------------
>
> Key: WFLY-6303
> URL: https://issues.jboss.org/browse/WFLY-6303
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.Final
> Environment: Java(TM) SE Runtime Environment (build pxa6480sr2fp10-20160108_01(SR2 FP10))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160106_284759 (JIT enabled, AOT enabled)
> J9VM - R28_20160106_1341_B284759
> JIT - tr.r14.java_20151209_107110.02
> GC - R28_20160106_1341_B284759_CMPRSS
> J9CL - 20160106_284759)
> JCL - 20151231_01 based on Oracle jdk8u71-b15
> Reporter: Martin Choma
> Assignee: Martin Choma
> Priority: Minor
>
> org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase starts failing with the latest IBM jdk.
> {noformat}
> ./integration-tests.sh clean test -Dmaven.repo.local=$REPO -Dts.noSmoke -Dts.basic -Dtest=RemotingLoginModuleTestCase
> Running org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase
> Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.546 sec <<< FAILURE! - in org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase
> testNotAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase) Time elapsed: 0.031 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase.testNotAuthorizedClient(RemotingLoginModuleTestCase.java:179)
>
> testAuthorizedClient(org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase) Time elapsed: 0.026 sec <<< ERROR!
> javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://127.0.0.1:14447 (javax.net.ssl.SSLException: Received fatal alert: handshake_failure)]
> at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
> at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
> at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)
> at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)
> at javax.naming.InitialContext.lookup(InitialContext.java:428)
> at org.jboss.as.test.integration.security.loginmodules.RemotingLoginModuleTestCase.testAuthorizedClient(RemotingLoginModuleTestCase.java:165)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:53 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-3272) Running a single test on windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3272?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-3272.
-----------------------------
Resolution: Rejected
you should quote paramters like "-Dtest=clustered" not other way around.
this works also in powershell.
> Running a single test on windows
> --------------------------------
>
> Key: WFLY-3272
> URL: https://issues.jboss.org/browse/WFLY-3272
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.1.0.CR1
> Environment: Windows7
> Reporter: Martin Choma
>
> While reading "Running a single test (or specified tests)" on https://docs.jboss.org/author/display/WFLY8/WildFly+Integration+Testsuite...
> Trying
> {noformat}
> integration-tests.bat install -Dtest='*Clustered*' -Dintegration.module -Dts.clust
> integration-tests.bat clean install -Dtest=org/jboss/as/test/integration/ejb/async/*TestCase.java -Dintegration.module -Dts.basic
> {noformat}
> get error
> {noformat}
> c:\Users\mchoma\Documents\GitHub\wildfly>integration-tests.bat install -Dtest="*Clustered*" -Dintegration.module -Dts.clust
> "Calling processTestDirectives install -Dtest "*Clustered*" -Dintegration.module -Dts.clust"
> Calling ..\.\tools\maven\bin\mvn.bat install -Dtest "*Clustered*" -Dintegration.module -Dts.clust -Dintegration.module -Dsmoke.integration.tests
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WildFly Test Suite: Aggregator
> [INFO] WildFly Test Suite: Integration
> [INFO] WildFly Test Suite: Integration - Smoke
> [INFO] WildFly Test Suite: Integration - Clustering
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly Test Suite: Aggregator 8.1.0.Final-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly Test Suite: Aggregator .................... FAILURE [0.023s]
> [INFO] WildFly Test Suite: Integration ................... SKIPPED
> [INFO] WildFly Test Suite: Integration - Smoke ........... SKIPPED
> [INFO] WildFly Test Suite: Integration - Clustering ...... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.025s
> [INFO] Finished at: Fri Apr 18 09:39:54 CEST 2014
> [INFO] Final Memory: 11M/154M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Unknown lifecycle phase "*Clustered*". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<
> goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-
> sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify,
> install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundEx...
> {noformat}
> Isnt docs up to date? Or is there some problem in running tests on windows.
> Thanx,
> Martin
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:47 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-5701) Compile error in clustering/common module with older version of jdk 8
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5701?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-5701.
-----------------------------
Fix Version/s: 10.0.0.Final
Resolution: Won't Fix
It is bug in javac that was fixed in later versions
> Compile error in clustering/common module with older version of jdk 8
> ---------------------------------------------------------------------
>
> Key: WFLY-5701
> URL: https://issues.jboss.org/browse/WFLY-5701
> Project: WildFly
> Issue Type: Feature Request
> Components: Build System, Clustering
> Reporter: Paul Gier
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> When compiling with jdk version "1.8.0_31" I get a compile error in the clustering/common module.
> {noformat}
> [ERROR] /home/pgier/projects/jboss-eap/clustering/common/src/main/java/org/jboss/as/clustering/controller/ExecutionHandler.java:[54,48] no suitable method found for collect(java.util.stream.Collector<E,capture#1 of ?,java.util.Map<java.lang.String,java.lang.Object>>)
> method java.util.stream.Stream.<R>collect(java.util.function.Supplier<R>,java.util.function.BiConsumer<R,? super capture#2 of ? extends E>,java.util.function.BiConsumer<R,R>) is not applicable
> (cannot infer type-variable(s) R
> (actual and formal argument lists differ in length))
> method java.util.stream.Stream.<R,A>collect(java.util.stream.Collector<? super capture#2 of ? extends E,A,R>) is not applicable
> (cannot infer type-variable(s) capture#3 of ?,T,K,U,T
> (argument mismatch; java.util.function.Function<capture#2 of ? extends E,capture#2 of ? extends E> cannot be converted to java.util.function.Function<? super capture#2 of ? extends E,? extends capture#2 of ? extends E>))
> [INFO] 1 error
> {noformat}
> If I use a newer jdk 8 version such as "1.8.0_65", the issue does not occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:25 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
jboss-modules.jar', class 'org/jboss/modules/Main', contains string [java.specification.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months