[jbosstools-issues] [JBoss JIRA] (JBIDE-13314) Improved support for the upcoming JBossAS 7.2

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-13314.
---------------------------------

    Resolution: Rejected


Two things to note here:

1) There will be no public release of AS 7.2
2) The only way I am seeing these incorrect launch args is if you are using the 7.0 server adapter to create your 7.2 server. If you want to use the unofficial unreleased as7.2, please use the 7.1 server adapter, as its arguments have already been fixed re: logmodule. 
                
> 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