7:43 a.m.
[
https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi...
]
Marián Labuda edited comment on JBIDE-22079 at 4/7/16 8:43 AM:
---------------------------------------------------------------
I found few details about this issue: This is related only when a project is a module of
maven project (maybe there are some similar cases that I am not aware of yet). And right
after a clone of git repository it tries to import module in workspace, then this error
pops up.
If a git repository is a project itself (e.g. in nodejs example templates) and I am
reusing local git repository, there is a dialog asking whether local project should be
overwritten. Upon confirmation of overwritting project in workspace, there is following
error message:
{code}Could not import project to the workspace.
org.eclipse.core.runtime.CoreException: Unable to locate git repository for project
nodejs-ex
at org.jboss.tools.openshift.egit.core.EGitUtils.connect(EGitUtils.java:263)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.operation.ImportNewProject.connectToGitRepo(ImportNewProject.java:150)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.operation.ImportNewProject.execute(ImportNewProject.java:106)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.ImportJob.runInWorkspace(ImportJob.java:79)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
with following nested error
{code}
Unable to locate git repository for project nodejs-ex
An exception stack trace is not available.
{code}
If I am using different location for git clone and I would like to overwrite workspace
project, everything works as expected.
was (Author: mlabuda):
I found few details about this issue: This is related only when a project is a module of
maven project (maybe there are some similar cases that I am not aware of yet). And right
after a clone of git repository it tries to import module in workspace, then this error
pops up.
If a git repository is a project itself (e.g. in nodejs example templates) and I am
reusing local git repository, there is a dialog asking whether local project should be
overwritten. Upon confirmation of overwritting project in workspace, there is following
error message:
{code}Could not import project to the workspace.
org.eclipse.core.runtime.CoreException: Unable to locate git repository for project
nodejs-ex
at org.jboss.tools.openshift.egit.core.EGitUtils.connect(EGitUtils.java:263)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.operation.ImportNewProject.connectToGitRepo(ImportNewProject.java:150)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.operation.ImportNewProject.execute(ImportNewProject.java:106)
at
org.jboss.tools.openshift.internal.ui.wizard.importapp.ImportJob.runInWorkspace(ImportJob.java:79)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
with following nested error
{code}
Unable to locate git repository for project nodejs-ex
An exception stack trace is not available.
{code}
Error when import a project already existing in workspace
---------------------------------------------------------
Key: JBIDE-22079
URL: https://issues.jboss.org/browse/JBIDE-22079
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Labels: import_wizard, openshift_v3
Fix For: 4.4.0.Alpha1
Attachments: import-error.png
When I am creating a new OpenShift application using an existing repo, or at least
project in workspace, it throws an error upon application creation completion. This is a
bit of pain, because even I have an existing git repo and checked the checkbox in Import
Wizard to reuse it, it tries to import project then, but it fails. But the existing
project is still usable to use it for a new OpenShift 3 server adapter and upon start of
the adapter, local changes are published to OpenShift. This issue is just about error.
Maybe we could display a dialog that such a project already exists in workspace and let
user to choose to replace it by the one being imported or keep it as it is (if user know
that the project in workspace is the correct one and he/she does not want to overwrite it
and let local changes disappear).
Error:
{code}Could not import project from
org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException:
There was a maven related error that prevented us from importing the project. We encourage
you to look into the pom in the cloned repository at
/home/mlabuda/git/jboss-eap-quickstarts.
One of the possible reasons is that there is already a project in your workspace that
matches the maven name of the OpenShift application. You can then rename your workspace
project and start over again.
An exception stack trace is not available.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)