[
https://issues.jboss.org/browse/JBIDE-12241?page=com.atlassian.jira.plugi...
]
Isaac Rooskov updated JBIDE-12241:
----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: irooskov
Release Notes Text: When creating or importing an OpenShift application to the
workspace, the user must provide a destination folder for the wizard to clone to. If the
destination folder already had a project with the same name, the wizard would not
complete. Even after moving or removing the conflicting folder from outside the tooling,
the wizard would not allow a user to clone to the location. This issue has now been fixed
and the wizard will check the folder again for any conflicts once a user switches in and
out of the folder, from the wizard. (was: When creating/importing an OpenShift
application to your workspace, you have to provide a destination-folder that the wizard
would clone to. If the destination folder already had a project with the very same name,
the wizard would not let you finishing it. Moving/Removing the conflicting folder outside
Eclipse did not help since the wizard did not check the location again, the error kept
popping up. You had to close the wizard and restart your operation.
We fixed this in Alpha1, the wizard will now check the folder once you switch pages back
and forth.)
text field for git cloning destination is not decorated with error,
not revalidated when switching back and forth in the wizard pages
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-12241
URL:
https://issues.jboss.org/browse/JBIDE-12241
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Minor
Labels: new_and_noteworthy
Fix For: 3.3.2, 4.0.0.Alpha1
Attachments: missing-decorator.png, repo-path-decorated.png
--
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