[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Marián Labuda (JIRA)
[ 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)
10 years
[JBoss JIRA] (JBIDE-22119) Improve treatment of missing/invalid date in timestamp comparator
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22119?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22119:
------------------------------------------
thx!
merged into master
> Improve treatment of missing/invalid date in timestamp comparator
> -----------------------------------------------------------------
>
> Key: JBIDE-22119
> URL: https://issues.jboss.org/browse/JBIDE-22119
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> CreationTimestampComparator makes a resource with missing/invalid date equal to any other resource. If in a list of resources one is invalid, it will make result unpredictable. It is better to move an invalid timestamp to the end of the list by assuming that it is less than any valid timestamp, it will ensure correct sorting of resources with valid timestamps.
> Also this comparator may be reused in OpenShiftResourcePropertySection.createCreatedBySorter() - the logic is the same.
> DateTimeUtils.parse(String) is better to prevent NPE or ArrayIndexOutOfBoundsException and throw the declared ParseException for empty value instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22079:
---------------------------------------
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)
10 years
[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-646:
--------------------------------
Assignee: Paul Leacu
> Do not include BPMN2 features in the JBoss Fuse category
> --------------------------------------------------------
>
> Key: JBTIS-646
> URL: https://issues.jboss.org/browse/JBTIS-646
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Environment: JBDS-IS 9.0.0.CR1a
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Attachments: jbdsis_fuse_category.png
>
>
> The category JBoss Fuse Development should contain only the following features
> - Fuse tooling
> - SwitchYard tooling (+ BPEL/BPMN2 support)
> All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-644) Remove category JBoss Integration and SOA Development
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-644?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-644:
--------------------------------
Assignee: Paul Leacu
> Remove category JBoss Integration and SOA Development
> -----------------------------------------------------
>
> Key: JBTIS-644
> URL: https://issues.jboss.org/browse/JBTIS-644
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> I think the the category "JBoss Integration and SOA Development" is not necessary. It doesn't contain any other component that the others. Moreover it is not related any any our product and it may be confusing for users.
> So I suggest to remove it from
> - Update site
> - Red Hat Central
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-646:
-----------------------------------------
In order to have BPMN2 support in SwitchYard, it requires the BPMN2 editor - they're intrinsically linked. The SY code actually extends the BPMN2 Modeler and thus includes it as a dependency. Not sure how to extricate if if you're installing Fuse, which includes SY.
> Do not include BPMN2 features in the JBoss Fuse category
> --------------------------------------------------------
>
> Key: JBTIS-646
> URL: https://issues.jboss.org/browse/JBTIS-646
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Environment: JBDS-IS 9.0.0.CR1a
> Reporter: Andrej Podhradsky
> Attachments: jbdsis_fuse_category.png
>
>
> The category JBoss Fuse Development should contain only the following features
> - Fuse tooling
> - SwitchYard tooling (+ BPEL/BPMN2 support)
> All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21351:
-----------------------------------
Labels: respin-b (was: )
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21351:
----------------------------------------
As I didn't add the respin-a tag, I guess it was missed. [~nickboldt] Should I simply add a respin-b tag here to have it rebuilt for CR1?
About master, JBIDE-21441 includes the fix for that, so it's tracked separately.
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Fix For: 4.3.1.CR1
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years