[jbosstools-issues] [JBoss JIRA] (JBIDE-14828) Application Wizard: if git clone directory already exist i cannot do anything
[
https://issues.jboss.org/browse/JBIDE-14828?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-14828.
---------------------------------
Resolution: Done
If the user has already cloned the eap-quickstarts repository in their destination clone
directory, it won't re-force a downloading of the repository. It will not delete the
local content at all. It will simply re-use the local copy they have already cloned. This
can save a lot of time for people who have already downloaded the repository and don't
wish to re-clone it into a new folder every single time they import the project.
If the user does wish to re-clone it, or if he has made changes to the local repository
and wishes to get a new clean one from upstream, he can simply choose a new target
destination / clone folder, same as before.
However the above problem does exist. If the user has already cloned the repository AND
deleted the target subfolder from the filesystem, it seems the 'filtering' code
will not find the matching subfolder and will instead try to import the entire git repo.
Please open a new issue for this.
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)