[
https://issues.jboss.org/browse/JBIDE-12150?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-12150 at 8/17/12 11:09 AM:
--------------------------------------------------------------------
I tried to reproduce it, and it turns out to happen the most, if I recreate a new
appliaction. When reimporting the very same application, it'll not always happen.
Restults are still very unpredictable. Sometimes it just works, sometimes I get the
expected broken repo
was (Author: adietish):
I tried to reproduce it, and it only occurrs if you (re-)create a new application
(with the very same name) on OpenShift. it does not occurr if you re-import the very same
application into a new project.
Git repository is sometimes corrupted after application creation
----------------------------------------------------------------
Key: JBIDE-12150
URL:
https://issues.jboss.org/browse/JBIDE-12150
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Final
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.2, 3.4.x
Attachments: JBIDE-12150.patch, MissingObjectException.png, openshift-status.png,
settings-untracked-jsdtscope-committed.png
If happens that when importing a new application to your workspace, the resulting
(cloned) git repository is corrupted.
--
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