[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21791: ----------------------------------------- [~davsclaus], Right now I believe the best solution is to save the open files before running a Forge command (as IDEA does right now). Mostly because commands may rely on changing other files (persistence.xml, web.xml, etc) and not having the latest version would not work. [~maxandersen] I agree that forcing to save the open files may not be ideal solution right now in a UX perspective. In a long term, as Forge works with the Resource API, the ideal choice would be to have a https://github.com/forge/core/blob/master/resources/api/src/main/java/org... implementation in Eclipse that delegates any call from Resource.getContents() to the editor contents (as setContents would set the Editor contents too), instead of fetching directly from the java.io.File. What do you guys think? Can we go with the "Save all" approach for now and have another JIRA as a future enhancement? -- This message was sent by Atlassian JIRA (v6.4.11#64026)