[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 updated JBIDE-22079:
----------------------------------
Issue Type: Enhancement (was: Bug)
> 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: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: import_wizard, openshift_v3
>
> 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-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 updated JBIDE-22079:
----------------------------------
Issue Type: Bug (was: Enhancement)
> 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
> Labels: import_wizard, openshift_v3
>
> 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-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 updated JBIDE-22079:
----------------------------------
Steps to Reproduce:
ASSERT: Have a project (jboss-kitchensink from EAP template) in workspace.
EXEC: Create a new application using jboss eap template and kitchensink project (CONTEXT_DIR param is equal to kitchensink)
ASSERT: In Import wizard user is asked to provide alternative git repo if it already exists or reuse the existing one. You can choose different git clone location or reuse the one (it does not matter).
EXEC: Finish the import wizard.
RESULT: Application is trying to import a project to workspace but it fails and show the error.
> 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
> Labels: import_wizard, openshift_v3
>
> 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-22079) Error when import a project already existing in workspace
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22079:
-------------------------------------
Summary: 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
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-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 updated JBIDE-22079:
----------------------------------
Labels: import_wizard openshift_v3 (was: )
> 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
> Labels: import_wizard, openshift_v3
>
> 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-630) JBTIS Target Platform - Mars - Update to latest JBT core
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-630?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-630:
-----------------------------
Description:
*Reason:* Sync with JBT 4.3.1.CR1a
*Project page/sources:* ...
*Version:* 4.3.1.Final-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:* Leave empty
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
< org.jboss.tools.as.test.core [3.1.1.CR1-v20160324-2013-B109]
< org.jboss.tools.jmx.core.test [1.7.1.CR1-v20160324-2013-B109]
< org.jboss.tools.common [3.7.1.CR1-v20160324-0436-B104]
< org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.common.base.test [3.7.1.CR1-v20160324-0436-B104]
< org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.common.test [3.7.1.CR1-v20160324-0436-B104]
< org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.tests [3.6.1.CR1-v20160324-0436-B104]
< org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.common.base.test [3.7.1.Final-v20160401-0436-B108]
> org.jboss.tools.community.central.feature.feature.group [2.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.central.feature.feature.jar [2.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.project.examples [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.as.test.core [3.1.1.Final-v20160401-1549-B112]
> org.jboss.tools.project.examples.cheatsheet [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.jmx.core.test [1.7.1.Final-v20160401-1549-B112]
> org.jboss.tools.project.examples [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.tests [3.6.1.Final-v20160401-0436-B108]
> org.jboss.tools.common [3.7.1.Final-v20160401-0436-B108]
> org.jboss.tools.common.test [3.7.1.Final-v20160401-0436-B108]
> org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.central [2.0.1.Final-v20160401-1059-B103]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
< org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
< org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> org.jboss.tools.project.examples [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.project.examples [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.central.feature.feature.group [2.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.project.examples.cheatsheet [3.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.central [2.0.1.Final-v20160401-1059-B103]
> org.jboss.tools.community.central.feature.feature.jar [2.0.1.Final-v20160401-1059-B103]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs
{code}
was:
*Reason:* SYnc with JBT 4.3.1.CR1a
*Project page/sources:* ...
*Version:* 4.3.1.Final-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:* Leave empty
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
{code}
> JBTIS Target Platform - Mars - Update to latest JBT core
> --------------------------------------------------------
>
> Key: JBTIS-630
> URL: https://issues.jboss.org/browse/JBTIS-630
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.3.1.CR1-TP
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.3.1.Final-TP
>
>
> *Reason:* Sync with JBT 4.3.1.CR1a
> *Project page/sources:* ...
> *Version:* 4.3.1.Final-SNAPSHOT
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:* Leave empty
> *Include Sources:* Yes
> *Affected JBoss Tools components:* JBDSIS
> *Include in JBDS:* Yes (JBDSIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> < org.jboss.tools.as.test.core [3.1.1.CR1-v20160324-2013-B109]
> < org.jboss.tools.jmx.core.test [1.7.1.CR1-v20160324-2013-B109]
> < org.jboss.tools.common [3.7.1.CR1-v20160324-0436-B104]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.common.base.test [3.7.1.CR1-v20160324-0436-B104]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.common.test [3.7.1.CR1-v20160324-0436-B104]
> < org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.tests [3.6.1.CR1-v20160324-0436-B104]
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.common.base.test [3.7.1.Final-v20160401-0436-B108]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.project.examples [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.as.test.core [3.1.1.Final-v20160401-1549-B112]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.jmx.core.test [1.7.1.Final-v20160401-1549-B112]
> > org.jboss.tools.project.examples [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.tests [3.6.1.Final-v20160401-0436-B108]
> > org.jboss.tools.common [3.7.1.Final-v20160401-0436-B108]
> > org.jboss.tools.common.test [3.7.1.Final-v20160401-0436-B108]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.central [2.0.1.Final-v20160401-1059-B103]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
> < org.jboss.tools.project.examples.cheatsheet [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.central.feature.feature.group [2.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.project.examples [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.project.examples [3.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.central [2.0.1.CR1-v20160324-1911-B99]
> < org.jboss.tools.community.central.feature.feature.jar [2.0.1.CR1-v20160324-1911-B99]
> > org.jboss.tools.project.examples [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.project.examples [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.central.feature.feature.group [2.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.project.examples.cheatsheet [3.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.central [2.0.1.Final-v20160401-1059-B103]
> > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Final-v20160401-1059-B103]
> === Summary ===
> file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs
> file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22075:
---------------------------------------
Not sure, but it looks like some loop for me. See following mapping
{code}
tcp 0 0 127.0.0.1:35734 127.0.0.1:50384 ESTABLISHED
tcp6 0 0 127.0.0.1:50384 127.0.0.1:35734 ESTABLISHED
{code}
After some time, only those two lines remain in output of the netstat command.
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-630) JBTIS Target Platform - Mars - Update to latest JBT core
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-630:
--------------------------------
Summary: JBTIS Target Platform - Mars - Update to latest JBT core
Key: JBTIS-630
URL: https://issues.jboss.org/browse/JBTIS-630
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: target-platform
Affects Versions: 4.3.1.CR1-TP
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.3.1.Final-TP
*Reason:* SYnc with JBT 4.3.1.CR1a
*Project page/sources:* ...
*Version:* 4.3.1.Final-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:* Leave empty
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-628) JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-628?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-628:
--------------------------------
Assignee: Paul Leacu
> JBTIS composite sites contains 3 or 4 copies of the same IUs, and up to 3 different versions
> --------------------------------------------------------------------------------------------
>
> Key: JBTIS-628
> URL: https://issues.jboss.org/browse/JBTIS-628
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Attachments: 3-copies-of-comm.proj.examples_GA.png, 4-copies-of-comm.proj.examples_EA.png
>
>
> {quote}
> Might be nothing but the p2director install tests [1] failed on multiple org.jboss.tools.community.project.examples being defined:
> 16:55:46 INSTALL FAILED
> 16:55:46
> 16:55:46 [p2.dir] Installing tern-server-nodejs-feature.feature.group 1.1.0.201511082254.
> 16:55:46 [p2.dir] Cannot complete the install because of a conflicting dependency.
> 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples 3.0.1.CR1-v20160324-1911-B99 (org.jboss.tools.community.project.examples.feature.feature.group 3.0.1.CR1-v20160324-1911-B99)
> 16:55:46 [p2.dir] Software being installed: JBoss Tools Community Project Examples Developer Resources 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples.feature.source.feature.group 3.0.1.Beta2-v20160121-2329-B74)
> 16:55:46 [p2.dir] Only one of the following can be installed at once:
> 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.1.Beta2-v20160121-2329-B74 (org.jboss.tools.community.project.examples 3.0.1.Beta2-v20160121-2329-B74)
> 16:55:46 [p2.dir] JBoss Tools Community Project Examples 3.0.0.Final-v20151001-1531-B45 (org.jboss.tools.community.project.examples 3.0.0.Final-v20151001-1531-B45)
> I'm pulling in version 3.0.1.CR1 here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> --paull
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p...
> {quote}
> Reason for this failure is that you're pulling from TWO versions of JBT:
> * 3.0.1.Beta2-v20160121-2329-B74
> * 3.0.0.Final-v20151001-1531-B45
> You should only be pulling from ONE.
> Your composites have 3 or 4 different copies of the same features. And of those, there are 3 different VERSIONS. See screenshots. This is terribly wrong. You should only need to include a single version, and don't need to include 3-4 copies.
> Here are the URLs used by your install test job:
> http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s...
> http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-s...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22075 at 4/4/16 8:27 AM:
------------------------------------------------------------------
[~mlabuda] can you explain the above, it's not obvious at all what your netstat output stands for.
[~fbricon] is this something you could look at since you're the one that's most intimate with the debugging tooling?
was (Author: adietish):
[~fbricon] is this something you could look at since you're the one that's most intimate with the debugging tooling?
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years