April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22079: ------------------------------------------ The only improvement I see here is that we can offer the user the ability to kill the existing project so that the import can still proceed. > 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 > 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-635) Add regression test for FUSETOOLS-1474

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-635?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-635: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Add regression test for FUSETOOLS-1474 > -------------------------------------- > > Key: JBTIS-635 > URL: https://issues.jboss.org/browse/JBTIS-635 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.CR1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > SSIA > + classes from other projects should be inaccessible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-635) Add regression test for FUSETOOLS-1474

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-635: ---------------------------------- Summary: Add regression test for FUSETOOLS-1474 Key: JBTIS-635 URL: https://issues.jboss.org/browse/JBTIS-635 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.CR1 Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Fix For: 4.3.0.Final SSIA + classes from other projects should be inaccessible -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22079: ------------------------------------------ This is actually caused by the fact that there already is a project with the same name (in your usecase maven tried to import a project - named after the maven artifact name in pom). The very same is true for whatever project you try to import where there already is a project with the same name in the workspace. The very same is true for the classic import wizards in eclipse: you cant import a project if the project name is already used. > 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 > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20597: ----------------------------------- Assignee: Jeff MAURY > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Labels: docker > Fix For: 4.4.x > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22034) Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22034?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22034: ----------------------------------- Assignee: Jeff MAURY > Replace Pin Console toggle tool item by Show Console Output When Standard Out Changes toggle item > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22034 > URL: https://issues.jboss.org/browse/JBIDE-22034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.4.x > > > Currently console containing output of rsync contains Pin Console toggle item which is useless there. Item should be changed to Show Console Output When Standard Out Changes which, when is enabled, show console view when output in it changes - this makes sense because if user want to track what have been rsynced, this is nice way to do it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21307: ----------------------------------- Assignee: Jeff MAURY > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. > the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: > {quote} > Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-634) Addapt tests for jbtis-4.3.0.CR1

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-634: --------------------------------- Summary: Addapt tests for jbtis-4.3.0.CR1 Key: JBTIS-634 URL: https://issues.jboss.org/browse/JBTIS-634 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.3.0.CR1 Reporter: Jozef Marko Assignee: Jozef Marko Fix For: 4.3.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22110) Unexpected error when cancelling installation (using D&D to Central)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22110?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22110: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Unexpected error when cancelling installation (using D&D to Central) > -------------------------------------------------------------------- > > Key: JBIDE-22110 > URL: https://issues.jboss.org/browse/JBIDE-22110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > Screencast: https://youtu.be/LObzeMo8TDw > Cancelling installation in phase "Retrieving listing" causes 3 unexpected errors: > {noformat} > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 12 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22110) Unexpected error when cancelling installation (using D&D to Central)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22110?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22110: ----------------------------------- Assignee: Snjezana Peco > Unexpected error when cancelling installation (using D&D to Central) > -------------------------------------------------------------------- > > Key: JBIDE-22110 > URL: https://issues.jboss.org/browse/JBIDE-22110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > Screencast: https://youtu.be/LObzeMo8TDw > Cancelling installation in phase "Retrieving listing" causes 3 unexpected errors: > {noformat} > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157) > at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84) > ... 8 more > Caused by: org.eclipse.core.runtime.OperationCanceledException > at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999) > at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101) > at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156) > ... 12 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016