[
https://issues.jboss.org/browse/JBIDE-14828?page=com.atlassian.jira.plugi...
]
Marián Labuda commented on JBIDE-14828:
---------------------------------------
In basic scenarios it works nice. But If I am using application with set context dir (e.g.
eap 6.4. basic s2i templates use kitchensink context dir, because it is contained in eap
quickstarts repo where is plenty of quickstarts) and I delete a project not only from
project explorer but also from file system (check the checkbox when prompt to delete
project), then only project is deleted from downloaded git repo of quickstarts. In this
case, wizard warn me about existing repository and dont allow me to proceed, until I
either choose different location or reuse existing repository. After checking the checkbox
to reuse repository (of quickstarts, where I earlier deleted the project), wizard is
finished successfully but it imports whole eap quickstarts project (parent of all
quickstarts) if there is no kitchensink project (which is not there because it was deleted
earlier but was not recovered). If I check checkbox "Reuse existing repository"
I understand it as overwriting of local content by the remote one. Is this behaviour, as
described above, desired?
Application Wizard: if git clone directory already exist i cannot do
anything
-----------------------------------------------------------------------------
Key: JBIDE-14828
URL:
https://issues.jboss.org/browse/JBIDE-14828
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Beta2
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Labels: application_wizard
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
Attachments: application-folder-already-exists.png
steps to reproduce:
# EXEC: create and/or import some appliaction from OpenShift to your local workspace
using the application/import wizard
# EXEC: once you have the project imported to your workspace, delete it
# EXEC: once it is deleted, go and try to re-import the very same application
Result:
The 3rd wizard page errors on the git cloning destination. You're told that the
destination folder already exists within the clone destination folder. The only way out
currently is to choose a different clone destination folder.
!application-folder-already-exists.png!
Expected:
It would help a lot if wizard would allow you to overwrite the existing destination. The
wizard could also check if the given folder holds a prior clone and then allow one to
"reuse" this folder. The given folder would then simply get imported to Eclipse
and we'd fetch instead of cloning.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)