January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-471) Unify component versions

by Robert (Bob) Brodt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Robert (Bob) Brodt commented on JBTIS-471: ------------------------------------------ Geez, you guys are killing me here :*) for Mars: BPMN2 metamodel: http://download.eclipse.org/modeling/mdt/bpmn2/updates/mars/1.2.1 - this is a Final BPMN2 Modeler: http://download.eclipse.org/bpmn2-modeler/updates/mars/1.2.3 - this is Beta1 BPEL Designer: http://download.eclipse.org/bpel/updates/mars/1.0.5 - this is a Final for Neon: BPMN2 metamodel: http://download.eclipse.org/modeling/mdt/bpmn2/updates/neon/1.3.0 - this is a Final BPMN2 Modeler: http://download.eclipse.org/bpmn2-modeler/updates/neon/1.3.0 - this is a Alpha1 BPEL Designer: http://download.eclipse.org/bpel/updates/neon/1.0.6 - this is a Final Yes, the Neon BPMN2 metamodel and BPEL Designer should be binary identical with their Mars counterparts, but compiled with Java 8 instead of 7. > Unify component versions > ------------------------ > > Key: JBTIS-471 > URL: https://issues.jboss.org/browse/JBTIS-471 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: junit4.8vs4.12.png > > > Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as > BPMN2 1.1.3.Final > Fuse 7.3.1.v20150728-1330-H54-Final > Teiid Designer 9.0.3.Final-v20150728-2029-B1148 > I suggest to use the format used by Teiid Designer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21458) Explorer: New deployments and pods dont refresh properly in explorer tree

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21458?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21458: --------------------------------------- Merged into feature branch > Explorer: New deployments and pods dont refresh properly in explorer tree > ------------------------------------------------------------------------- > > Key: JBIDE-21458 > URL: https://issues.jboss.org/browse/JBIDE-21458 > 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 > > Attachments: Service_added_but_shows_empty_space.png > > > Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached: > Demonstrated by: > # From eclipse, add a new project > # Expand project . note: no deployments > # From cli, add a service > # Note screen 'updates' but there is no deployment, just an empty node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build pod in explorer deployment view if it any state other then complete

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21457: ---------------------------------- Fix Version/s: 4.3.1.Beta2 > Explorer: Show build pod in explorer deployment view if it any state other then complete > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > > Display the build pod in the tree view when it starts. Once it gets to complete (success or failure) remove it from the viewer. This will allow a user to see the builds associated with a deployment and know something is happening. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-438?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-438: ---------------------------------- Locus 1.5.0.Final is out: http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc... https://repository.jboss.org/nexus/service/local/repositories/releases/co... > 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.1.Beta1-TP > > > 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-543) Add missing JBDS TP bits to JBDS IS update site zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-543?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-543: ---------------------------------- Locus 1.5.0.Final is out: http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc... https://repository.jboss.org/nexus/service/local/repositories/releases/co... > Add missing JBDS TP bits to JBDS IS update site zip > --------------------------------------------------- > > Key: JBTIS-543 > URL: https://issues.jboss.org/browse/JBTIS-543 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21478?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21478: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > New Server adapter using same build config and server is ignored > ---------------------------------------------------------------- > > Key: JBIDE-21478 > URL: https://issues.jboss.org/browse/JBIDE-21478 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created. > I would expect one of following: > a) An existing server adapter will be updated according to the latest details filled in server adapter wizard > b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21478?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21478. ----------------------------------- Resolution: Done > New Server adapter using same build config and server is ignored > ---------------------------------------------------------------- > > Key: JBIDE-21478 > URL: https://issues.jboss.org/browse/JBIDE-21478 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created. > I would expect one of following: > a) An existing server adapter will be updated according to the latest details filled in server adapter wizard > b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21478: ------------------------------------- Summary: New Server adapter using same build config and server is ignored Key: JBIDE-21478 URL: https://issues.jboss.org/browse/JBIDE-21478 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Marián Labuda Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 4.3.1.Beta2 When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created. I would expect one of following: a) An existing server adapter will be updated according to the latest details filled in server adapter wizard b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21421) New Server adapter using same build config and server is ignored

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21421?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21421. --------------------------------- Verified in nigthly build of JBDS 9.1.0.Beta2 with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153. > New Server adapter using same build config and server is ignored > ---------------------------------------------------------------- > > Key: JBIDE-21421 > URL: https://issues.jboss.org/browse/JBIDE-21421 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created. > I would expect one of following: > a) An existing server adapter will be updated according to the latest details filled in server adapter wizard > b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21424) Server adapter editor: IP in host name of a server adapter overview has cut off digit

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21424?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21424. --------------------------------- Currently locally running OpenShift instance and also internal OSE 3 instance display host names as DNS names, but those names are correct, no missing last char, I consider it done. Verified in nigthly build of JBDS 9.1.0.Beta2 with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153. > Server adapter editor: IP in host name of a server adapter overview has cut off digit > ------------------------------------------------------------------------------------- > > Key: JBIDE-21424 > URL: https://issues.jboss.org/browse/JBIDE-21424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: openshift_v3, server_adapter_editor > Fix For: 4.3.1.Beta2 > > > In a server adapter overview there is a text widget for a host name, where IP address of a service is filled in. Problem is that the IP address is missing last digit. -- 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