[
https://issues.jboss.org/browse/JBIDE-13314?page=com.atlassian.jira.plugi...
]
Juergen Zimmermann commented on JBIDE-13314:
--------------------------------------------
Rob, I was using the "JBoss Tools Runtime Detection" which configured the 7.2
server as 7.0. When I explicitely configure the runtime environment as 7.1, then the issue
is gone. Thanks for the hint.
Improved support for the upcoming JBossAS 7.2
---------------------------------------------
Key: JBIDE-13314
URL:
https://issues.jboss.org/browse/JBIDE-13314
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 4.0.0.Final
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha1
JBoss Tools are already detecting a 7.2 server (compiled from upstream master). When such
a 7.2 server is started, you'll see this warning:
"WARNING: -logmodule is deprecated. Please use the system property
'java.util.logging.manager' or the 'java.util.logging.LogManager' service
loader."
The solution: In the "Open launch configuration" just remove "-logmodule
org.jboss.logmanager" from the "Program arguments" and add
"-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to the "VM
arguments".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira