[
https://issues.jboss.org/browse/JBIDE-15370?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-15370.
---------------------------------
Resolution: Rejected
I've put a lot of thought into this, but, really, there's no real way for me to
know whether a file is editable at runtime or not. Sure, 'standalone.xml' can
easily be filtered or show a warning, but what about others? What about custom names? What
about custom folders? Users can modify the launch script in any way to basically make any
file be the configuration file with which to launch.
Also, filesets are dumb. They are intentionally dumb, and a user opening it in an editor
is equivilent to a user opening it in vi or notepad.
Also, this jira has received no comments from the original poster, and no explanation as
to what he meant, so I think I need to reject this jira as unclear and user error.
There's not much I can do here. There's just no way for me to come up with an
adequate list of files or conditions for which such a warning should appear.
when port-offset is "0" and modifications are done to
servers the xml is persisted incorrectly and the port-offset is not writen
---------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-15370
URL:
https://issues.jboss.org/browse/JBIDE-15370
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Reporter: thiago andrade
Assignee: Rob Stryker
--
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