[ https://issues.jboss.org/browse/JBIDE-24991?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24991: ------------------------------------- To understand your usecase, I'm assuming you: 1) Create a new server in local+filesystem mode 2) Open teh server editor 3) Open the launch configuration 4) Add the sysprops you want to use to override the standalone.xml values 5) Save the launch configuration 6) Get annoyed that the server editor is not updated with the new values from the launch config The launch configuration pulls data from the server editor, and not the other way around. The server editor can pull data from the underlying xml files... but those xml files won't know what value is being passed into the sysprop. If you're going through the effort of customizing the launch configuration's VM args tab, then you also need to in to the server editor and update the port section. We cannot introduce a circular logic here without breaking the tools. What you're basically suggesting is that: 1) User requests launch config 2) Launch config tries to get ports from server editor 3) Server object tries to get ports from launch config sysprops. 4) Since launch config isn't made yet, a new launch config is created, and tries to get ports from server editor 5) Server object tries to get ports from launch config sysprops. 6) Since launch config isn't made yet, a new launch config is created, and tries to get ports from server editor 7) Server object tries to get ports from launch config sysprops. 8) etc etc etc. This would be an endless loop. Basically, you can change the xml file directly, and have your changes automatically detected. But if you are opening the launch config and adding custom flags, then you must also override the port section in the editor so the tooling knows what ports to access on the server. Does this make sense to you? -- This message was sent by Atlassian JIRA (v7.2.3#72005)