[jbosstools-issues] [JBoss JIRA] (JBIDE-9934) handle the case where a project already exist with the same name
Thursday, 1 December
2011
Thu, 1 Dec
'11
3:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-9934?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen edited comment on JBIDE-9934 at 12/1/11 9:17 AM:
---------------------------------------------------------------------
edited: this comment was talking about file permissions for chmod 0600 for ssh files - not
related to this issue.
was (Author: maxandersen):
File f = ...
// set f permission to correspond to 'chmod 0600' read/write only for user
// First clear all permissions for both user and others
f.setReadable(false, false);
f.setWritable(false, false);
// Enable only readable for user
f.setReadable(true, true);
f.setWritable(true, true);
If you do the above in a different sequence you don't end up with chmod 0600.
handle the case where a project already exist with the same name
----------------------------------------------------------------
Key: JBIDE-9934
URL: https://issues.jboss.org/browse/JBIDE-9934
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Fix For: 3.3.0.M5
when you import a project via openshift it does not handle the case where a project of
the same name already exist. It does warn you but then the wizard "crashes".
Two tests:
Import the same openshift app twice.
or
create a project with same name
then import openshift app with project with same name.
Needs to be tested for both the maven and general import scenario.
--
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