[
https://issues.jboss.org/browse/JBIDE-10759?page=com.atlassian.jira.plugi...
]
Lucia Jelinkova commented on JBIDE-10759:
-----------------------------------------
I agree that the simplified solution is enough for the Beta but when you do not mention
that in the Jira it's quite hard to validate it :-)Also for the history purposes it is
fine to have the new solution mentioned in Jira.
Git clone destination folder is not validated
---------------------------------------------
Key: JBIDE-10759
URL:
https://issues.jboss.org/browse/JBIDE-10759
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Lucia Jelinkova
Fix For: 3.3.0.Beta1
Attachments: finish-enabled.png, missing-error.png, validation.jpg
# ASSERT: make sure you have a folder in <home>/git/<project name> (ex.
former clone, empty folder, etc.) ex. have a folder <home>/git/*as*
# EXEC: launch the OpenShift Express Application wizard
# EXEC: log in and choose a new name <project name> & type (no embedded
cartridges needed) ex. "*as*" as name
# EXEC: on the project page: choose *Create new*
Result:
*Finish" is enabled even though the checkout will not be possible: You already have
a folder with the same name as the clone.
!finish-enabled.png!
The clone would have to remove that one or cancel, warning about it.
The wizard with the clone settings has no warning/error telling you that the clone
destination is not valid.
!missing-error.png!
Expected result:
*Finish* must be disabled as long as the git clone destination is invalid (already a
file/folder present). The clone settings page must decorate the *Location* input.
--
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