January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21472) Server Adapter: Missing context menu item to show application details

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21472: ------------------------------------- Summary: Server Adapter: Missing context menu item to show application details Key: JBIDE-21472 URL: https://issues.jboss.org/browse/JBIDE-21472 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Marián Labuda In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21472) Server Adapter: Missing context menu item to show application details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21472?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21472: ---------------------------------- Labels: openshift_v2 server_adapter (was: ) > Server Adapter: Missing context menu item to show application details > --------------------------------------------------------------------- > > Key: JBIDE-21472 > URL: https://issues.jboss.org/browse/JBIDE-21472 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Labels: openshift_v2, server_adapter > > In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21471) Show in -> BrowserSim is enabled for projects on stopped server

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21471?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-21471: ---------------------------------------------- Assignee: Konstantin Marmalyukov (was: Ilya Buziuk) > Show in -> BrowserSim is enabled for projects on stopped server > --------------------------------------------------------------- > > Key: JBIDE-21471 > URL: https://issues.jboss.org/browse/JBIDE-21471 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Konstantin Marmalyukov > > It is possible to click Show in -> BrowserSim on a server module deployed on a stopped server. The result is a blank page opened in BrowserSim. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21471) Show in -> BrowserSim is enabled for projects on stopped server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21471?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21471: ----------------------------------- Assignee: Ilya Buziuk (was: Xavier Coulon) > Show in -> BrowserSim is enabled for projects on stopped server > --------------------------------------------------------------- > > Key: JBIDE-21471 > URL: https://issues.jboss.org/browse/JBIDE-21471 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Ilya Buziuk > > It is possible to click Show in -> BrowserSim on a server module deployed on a stopped server. The result is a blank page opened in BrowserSim. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21471) Show in -> BrowserSim is enabled for projects on stopped server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21471?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21471: ----------------------------------- Assignee: Xavier Coulon > Show in -> BrowserSim is enabled for projects on stopped server > --------------------------------------------------------------- > > Key: JBIDE-21471 > URL: https://issues.jboss.org/browse/JBIDE-21471 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Xavier Coulon > > It is possible to click Show in -> BrowserSim on a server module deployed on a stopped server. The result is a blank page opened in BrowserSim. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21471) Show in -> BrowserSim is enabled for projects on stopped server

by Jan Richter (JIRA)

Jan Richter created JBIDE-21471: ----------------------------------- Summary: Show in -> BrowserSim is enabled for projects on stopped server Key: JBIDE-21471 URL: https://issues.jboss.org/browse/JBIDE-21471 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.3.1.Beta2 Reporter: Jan Richter It is possible to click Show in -> BrowserSim on a server module deployed on a stopped server. The result is a blank page opened in BrowserSim. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-438) Add JAXB XJC, IMPL and Core to JBTIS TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-438?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-438: ----------------------------- Description: Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. *Project page/sources:* https://jaxb.java.net/ *Version:* 2.2.7 (no hard requirement on this specific version that I know of) *License and owner:* CDDL v1.1 and GPL v2 *Original p2 repo:* unknown *JBoss mirror:* unknown *Include Sources:* Yes *Affected projects:* Fuse IDE *Include in JBDS:* unknown *Type of dependency:* unknown *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/ https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/ https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-core/2.2.7/ {code} > org.jboss.tools.locus.jaxb-xjc [2.2.7.v20160113-1915] > org.jboss.tools.locus.jaxb-core [2.2.7.v20160114-2130] > org.jboss.tools.locus.jaxb-impl [2.2.7.v20160113-1915] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs {code} was: Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. *Project page/sources:* https://jaxb.java.net/ *Version:* 2.2.7 (no hard requirement on this specific version that I know of) *License and owner:* CDDL v1.1 and GPL v2 *Original p2 repo:* unknown *JBoss mirror:* unknown *Include Sources:* Yes *Affected projects:* Fuse IDE *Include in JBDS:* unknown *Type of dependency:* unknown *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > Add JAXB XJC, IMPL and Core to JBTIS TP > --------------------------------------- > > Key: JBTIS-438 > URL: https://issues.jboss.org/browse/JBTIS-438 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: Fuse IDE, target-platform > Reporter: Keith Babo > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha1 > > > Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). > We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. > *Project page/sources:* https://jaxb.java.net/ > *Version:* 2.2.7 (no hard requirement on this specific version that I know of) > *License and owner:* CDDL v1.1 and GPL v2 > *Original p2 repo:* unknown > *JBoss mirror:* unknown > *Include Sources:* Yes > *Affected projects:* Fuse IDE > *Include in JBDS:* unknown > *Type of dependency:* unknown > *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/ > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/ > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-core/2.2.7/ > {code} > > org.jboss.tools.locus.jaxb-xjc [2.2.7.v20160113-1915] > > org.jboss.tools.locus.jaxb-core [2.2.7.v20160114-2130] > > org.jboss.tools.locus.jaxb-impl [2.2.7.v20160113-1915] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 3 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-438) Add JAXB XJC, IMPL and Core to JBTIS TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-438?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-438: ----------------------------- Summary: Add JAXB XJC, IMPL and Core to JBTIS TP (was: Add JAXB XJC to TP) > Add JAXB XJC, IMPL and Core to JBTIS TP > --------------------------------------- > > Key: JBTIS-438 > URL: https://issues.jboss.org/browse/JBTIS-438 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: Fuse IDE, target-platform > Reporter: Keith Babo > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha1 > > > Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version). > We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin. > *Project page/sources:* https://jaxb.java.net/ > *Version:* 2.2.7 (no hard requirement on this specific version that I know of) > *License and owner:* CDDL v1.1 and GPL v2 > *Original p2 repo:* unknown > *JBoss mirror:* unknown > *Include Sources:* Yes > *Affected projects:* Fuse IDE > *Include in JBDS:* unknown > *Type of dependency:* unknown > *non-p2 repository:* https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21470) Use MessageDialog instead of MessageBox in ZombieProcessPrompter

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21470?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-21470: ---------------------------------- Assignee: Rob Stryker (was: Radim Hopp) > Use MessageDialog instead of MessageBox in ZombieProcessPrompter > ---------------------------------------------------------------- > > Key: JBIDE-21470 > URL: https://issues.jboss.org/browse/JBIDE-21470 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.1.Beta1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > > Our integration tests sometimes get stuck on this MessageBox as it creates native window which RedDeer nor SWTBot can access. Using MessageDialog enable us to handle it within our integration tests and as a bonus it matches eclipse look&feel better (imo). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21468) Delete project menu entry is not enabled to delete a project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21468?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21468: ------------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.CR1) > Delete project menu entry is not enabled to delete a project > ------------------------------------------------------------ > > Key: JBIDE-21468 > URL: https://issues.jboss.org/browse/JBIDE-21468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

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 January 2016