[
https://issues.jboss.org/browse/JBIDE-10513?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-10513.
---------------------------------
Resolution: Done
It took me a while to replicate your situation, since you provided no instructions ;)
This bug is regarding the editor, not the core behaviour. It seems the editor properly
auto-detects just fine. the core JBossServer object was not properly dereferencing the
${jboss.management.http.port:9990} instructions. It is now. One line patch.
management ports in 7.1 as using properties causing automatic
detection to fail
-------------------------------------------------------------------------------
Key: JBIDE-10513
URL:
https://issues.jboss.org/browse/JBIDE-10513
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta1
Seems CR1 made the following changes:
< <socket-binding name="management-native"
interface="management"
port="${jboss.management.native.port:9999}"/>
< <socket-binding name="management-http"
interface="management" port="${jboss.management.http.port:9990}"/>
---
> <socket-binding name="management-native"
interface="management" port="9999"/>
> <socket-binding name="management-http"
interface="management" port="9990"/>
Two things should happen:
1) we should handle this style
2) we should fallback to default if we can't parse the file instead of creating a
"broken" editor.
Should add warning about it not being detected, just doing default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira