[ https://issues.jboss.org/browse/JBIDE-17919?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-17919: --------------------------------------- Validated the bug exists based on the revised repo steps. One thing I did notice after trying to save a second time is the file name is now (bug?): {{/home/jeff(1).cantrill/git/diy/diy-full.tar.gz}} which is some variation of when the file already exists and the second copy is represented USUALLY like: {{/home/jeff.cantrill/git/diy/diy-full(1).tar.gz}}. I'm not sure if this is the tooling code creating this file name or not; that requires additional investigation. At [~mlabuda] suggestion, I investigated how rhc behaves and found that it does not care if the file exists or not. It overwrites the file or creates a new one. If you do not provide the '--filename' switch, it creates a file of <project_name>.tar.gz. Subsequent calls overwrite and do not add a numerical index and/or timestamp. [~adietish] can you comment on what we should do to resolve to make it conform with intended design: # Reload the original file name instead of the 'duplicate' file name (e.g. /home/user.name/file-full.tar.gz instead of /home/user(1).name/file-full-tar.gz or /home/user.name/file-full(1).tar.gz # Allow the user to edit the file name by typing it in (currently not able) # Remove 'full/deployment' from the filename to be consistent with rhc # Add a index or timestamp to the filename to make it unique from the previous snapeshot -- This message was sent by Atlassian JIRA (v6.2.6#6264)