October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2447) Issues to be resolved in SOA 5.0.3 Tooling

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBDS-2447?page=com.atlassian.jira.plugin.... ] Douglas Palmer reassigned JBDS-2447: ------------------------------------ Assignee: Paul Leacu (was: Douglas Palmer) > Issues to be resolved in SOA 5.0.3 Tooling > ------------------------------------------ > > Key: JBDS-2447 > URL: https://issues.jboss.org/browse/JBDS-2447 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: integration-platform > Affects Versions: 5.0.3.GA-SOA > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: 5.0.6.GA-SOA > > > Issues to be resolved in SOA 5.0.3 Tooling* > * This tooling is needed to support SOA-P 5.3.1 and will be certified with JBDS 5.0.2 > 1) ESB Issues > https://issues.jboss.org/browse/JBDS-2444, https://bugzilla.redhat.com/show_bug.cgi?id=894120 > JBDS 5.0.2 Core + 5.0.2 tooling is unable to recognize the 4.11.1 ESB in SOA-P 5.3.1.ER2 and later > https://issues.jboss.org/browse/JBIDE-13209 > Need to add ESB 4.12 option with constraints > 2) EDS Issues - https://bugzilla.redhat.com/show_bug.cgi?id=893201 > https://bugzilla.redhat.com/show_bug.cgi?id=873834 > Provide the relational.xmd file which has the non-prepared extension property > https://bugzilla.redhat.com/show_bug.cgi?id=893581 > (TEIIDDES-1255) Execution plan without executing the query > https://bugzilla.redhat.com/show_bug.cgi?id=893583 > (TEIIDDES-1540) Non-UTF-8 Multi-byte characters imported from csv file are garbled > Note: Related Issues Already Resolved in JBDS 5.0.2 > https://issues.jboss.org/browse/JBDS-2365 > ESB projects cannot be deployed using Server Add/Remove > https://issues.jboss.org/browse/JBIDE-13328 > as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12 > https://issues.jboss.org/browse/JBDS-2394 > ESB projects cannot be deployed using Server Add/Remove -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13399) ESB Runtime - defaults to highest supported version - when creating a new ESB project

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13399?page=com.atlassian.jira.plugi... ] Douglas Palmer reassigned JBIDE-13399: -------------------------------------- Assignee: Paul Leacu (was: Douglas Palmer) > ESB Runtime - defaults to highest supported version - when creating a new ESB project > ------------------------------------------------------------------------------------- > > Key: JBIDE-13399 > URL: https://issues.jboss.org/browse/JBIDE-13399 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: integration-platform > Affects Versions: 3.2.2.Final > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: LATER > > > Example scenario: > New install of JBDS/JBossTools, install the ESB tooling, create a server runtime for SOA 5.2, and a corresponding ESB runtime of 4.10. > Then, create a new ESB project - and the ESB runtime displayed in the wizard is 4.12, as this automatically defaults to the highest supported facet version on the runtime. > For each version of ESB, we have declared an explicit facet. In org.jboss.tools.esb.project.core, we have facets defined (4.2,4.3,4.4,4.5,4.6,4.7,4.9,4.10,4.11,4.12) and assign them to EAP runtime components (4.3,5.0,6.0) (which are specified in the AS tools plug-ins). So every version of SOA-P based on EAP 4.3, 5.x, or 6.x supports every facet version we've defined thus far - up to 4.12 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2388) Tracker issue - JBDS6 and SOA Tooling Issues

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBDS-2388?page=com.atlassian.jira.plugin.... ] Douglas Palmer reassigned JBDS-2388: ------------------------------------ Assignee: Paul Leacu (was: Douglas Palmer) > Tracker issue - JBDS6 and SOA Tooling Issues > -------------------------------------------- > > Key: JBDS-2388 > URL: https://issues.jboss.org/browse/JBDS-2388 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: integration-platform > Affects Versions: 5.0.0.GA-SOA > Reporter: Len DiMaggio > Assignee: Paul Leacu > Fix For: 6.0.0.Alpha1-SOA > > > Summary of current blocking bugs for SOA Tooling, inc. JBDS 6.0 (Eclipse Juno) > Tracker bug: https://issues.jboss.org/browse/JBDS-2388 > * Tooling Install onto JBDS 6.0 is blocked by SOA 5.3 tooling's dependency on Eclipse 3.7: > - JBDS: https://issues.jboss.org/browse/JBDS-2269 > - SOA: https://bugzilla.redhat.com/show_bug.cgi?id=855097 > - BRMS: https://bugzilla.redhat.com/show_bug.cgi?id=855100 > * API Change Issue - Cannot install the ESB tools and ESB detector with Juno > - https://issues.jboss.org/browse/JBIDE-12061 > * Related SwitchYard tooling issue > - https://issues.jboss.org/browse/JBDS-2374 > * And other tooling install bug: > - https://issues.jboss.org/browse/JBIDE-12936 > * And this SOA related bug in JBDS core - https://issues.jboss.org/browse/JBDS-2365 - blocks deploying to SOA servers. > In SOA 6, a corresponding fix should be made to move the property to SOA tooling - > https://issues.jboss.org/browse/JBDS-2406, https://bugzilla.redhat.com/show_bug.cgi?id=880647 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2350) The language "en-UK" is hardcoded in HumanTask handlers

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBDS-2350?page=com.atlassian.jira.plugin.... ] Douglas Palmer reassigned JBDS-2350: ------------------------------------ Assignee: Paul Leacu (was: Douglas Palmer) > The language "en-UK" is hardcoded in HumanTask handlers > ------------------------------------------------------- > > Key: JBDS-2350 > URL: https://issues.jboss.org/browse/JBDS-2350 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration-platform > Affects Versions: 5.0.0.GA-SOA > Reporter: Len DiMaggio > Assignee: Paul Leacu > Priority: Critical > Fix For: 6.0.0.Alpha1-SOA > > > See: https://bugzilla.redhat.com/show_bug.cgi?id=863390 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12226) org.jboss.tools.runtime.soa.test are useless

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12226?page=com.atlassian.jira.plugi... ] Douglas Palmer reassigned JBIDE-12226: -------------------------------------- Assignee: Paul Leacu (was: Douglas Palmer) > org.jboss.tools.runtime.soa.test are useless > -------------------------------------------- > > Key: JBIDE-12226 > URL: https://issues.jboss.org/browse/JBIDE-12226 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-platform > Affects Versions: 4.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Paul Leacu > Fix For: 4.0.0.Alpha1-SOA > > > The tests inside org.jboss.tools.runtime.soa.test are just copy-pasted from org.jboss.tools.runtime.test. They should be removed since they are not accurate in SOA Tooling. > Instead, the runtime-soa module should contain test that verify it is able to detect SOA-P for SOA Tooling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12384) Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12384?page=com.atlassian.jira.plugi... ] Douglas Palmer reassigned JBIDE-12384: -------------------------------------- Assignee: Paul Leacu (was: Douglas Palmer) > Error trying install JBoss SOA tools 3.? for Eclipse 4.2 (Juno) has error > ------------------------------------------------------------------------- > > Key: JBIDE-12384 > URL: https://issues.jboss.org/browse/JBIDE-12384 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform, runtime-detection > Affects Versions: 3.3.1.Final > Environment: MacOS Mountain Lion with Eclipse 4.2 (Juno). > Reporter: Robb Greathouse > Assignee: Paul Leacu > Fix For: 4.0.0.Alpha1-SOA > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth commented on JBIDE-15597: --------------------------------------------- Thanks for the update. Also, for the comments about the standards associated with indicating a pop-up menu. I mention the inconvenience because I looked through quite a few screens and topics and did not isolate what you have done in probably a few seconds. I just don't have time to learn SWT, the plugin, and some other tool that is really irrelevant to what I am doing, at this time. (But I will definitely take time to figure it out once the view is done, and I have some more time.) > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12061) Cannot install the ESB tools and ESB detector with Juno - API change

by Douglas Palmer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12061?page=com.atlassian.jira.plugi... ] Douglas Palmer reassigned JBIDE-12061: -------------------------------------- Assignee: Paul Leacu (was: Douglas Palmer) > Cannot install the ESB tools and ESB detector with Juno - API change > -------------------------------------------------------------------- > > Key: JBIDE-12061 > URL: https://issues.jboss.org/browse/JBIDE-12061 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 3.3.0.CR1 > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa... > http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.CR1.core/ > Eclipse Juno: > Version: 4.2.0 > Build id: I20120524-2100 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.0.x > > > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) > Software currently installed: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) > Only one of the following can be installed at once: > Core Runtime 3.8.0.v20120521-2346 (org.eclipse.core.runtime 3.8.0.v20120521-2346) > Core Runtime 3.8.0.v20120511-1333 (org.eclipse.core.runtime 3.8.0.v20120511-1333) > Core Runtime 3.7.0.v20110110 (org.eclipse.core.runtime 3.7.0.v20110110) > Cannot satisfy dependency: > From: Eclipse e4 Rich Client Platform 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm (org.eclipse.e4.rcp.feature.group 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm) > To: org.eclipse.core.runtime [3.8.0.v20120521-2346] > Cannot satisfy dependency: > From: Eclipse Platform 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD (org.eclipse.platform.feature.group 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD) > To: org.eclipse.rcp.feature.group [4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3] > Cannot satisfy dependency: > From: Eclipse RCP 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3 (org.eclipse.rcp.feature.group 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3) > To: org.eclipse.e4.rcp.feature.group [1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm] > Cannot satisfy dependency: > From: Eclipse Project SDK 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb (org.eclipse.sdk.feature.group 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb) > To: org.eclipse.platform.feature.group [4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD] > Cannot satisfy dependency: > From: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) > To: org.eclipse.sdk.feature.group [4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb] > Cannot satisfy dependency: > From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector 1.3.0.v20120522-1702-H4-Beta2-SOA) > To: bundle org.eclipse.core.runtime [3.7.0,3.8.0) > Cannot satisfy dependency: > From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) > To: org.jboss.tools.runtime.esb.detector [1.3.0.v20120522-1702-H4-Beta2-SOA] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13208) Allow custom 'standalone' mode directory in AS7 server plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13208?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13208: -------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) > Allow custom 'standalone' mode directory in AS7 server plugin > ------------------------------------------------------------- > > Key: JBIDE-13208 > URL: https://issues.jboss.org/browse/JBIDE-13208 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Mac OS-X 10.8.2, Java 6, Java 7, JBoss AS 7.x, JBoss EAP 6, JBDS 5.0.1 > Reporter: Duncan Doyle > Assignee: Rob Stryker > Labels: f2f2012 > Fix For: 4.2.0.Alpha1 > > > As with JBoss EAP5.x, I have the habit of working in a copy of a 'profile' directory. With JBoss AS7/EAP6 I therefore work in copies of 'standalone' and 'domain' (depending on the operational mode). When I start AS/EAP, I reference the correct server directory with the 'jboss.server.base.dir' or 'jboss.domain.base.dir' system property. This allows me, among other things, to run multiple AS/EAP instances from a single JBoss AS/EAP installation. > It seems that the JBDS AS7 plugin only allows me to reference the default 'standalone' directory. I'm not able to select a different directory in the 'JBoss Runtime' configuration screen. I would propose to add the possibility to start a JBoss AS7/EAP6 instance from a different directory than 'standalone'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15597 at 10/2/13 10:07 AM: -------------------------------------------------------------------- I replaced the separate lists by a table with 2 columns, regrouped the buttons (new, edit, remove and import, export) and added a confirmation dialog in case the users wants to delete a variable. IMHO I dont see where balsamiq is too limiting, it always works for us and is IMHO far quicker and efficient than screenshotting, editing, commenting about what's different than shown (or even paint the screenshots). was (Author: adietish): I replaced the separate lists by a table with 2 columns. IMHO I dont see where balsamiq is too limiting, it always works for us and is IMHO far quicker and efficient than screenshotting, editing, commenting about what's different than shown (or even paint the screenshots). > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 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 October 2013