May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22287) Test: Provide ability to run integration tests

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22287: ---------------------------------------- Summary: Test: Provide ability to run integration tests Key: JBIDE-22287 URL: https://issues.jboss.org/browse/JBIDE-22287 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Andre Dietisheim We should provide the ability to run integration tests in a way that's separate from running pure unit tests. There already is at least 1 integration test that's run with the unit tests currently: [DockerHubRegistryTest|https://github.com/adietish/jbosstools-openshift/bl...]. We shoud separate this integration test (and the other ones that there might be?) and provide * a specific maven profile for integration tests only * a separate test suite -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22287) Test: Provide ability to run integration tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22287?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22287: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 > Test: Provide ability to run integration tests > ---------------------------------------------- > > Key: JBIDE-22287 > URL: https://issues.jboss.org/browse/JBIDE-22287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.4.0.Alpha2 > > > We should provide the ability to run integration tests in a way that's separate from running pure unit tests. There already is at least 1 integration test that's run with the unit tests currently: [DockerHubRegistryTest|https://github.com/adietish/jbosstools-openshift/bl...]. We shoud separate this integration test (and the other ones that there might be?) and provide > * a specific maven profile for integration tests only > * a separate test suite -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-687) Update new project wizard tests for the new version of drools plugin

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/JBTIS-687?page=com.atlassian.jira.plugin.... ] Tomas David updated JBTIS-687: ------------------------------ Summary: Update new project wizard tests for the new version of drools plugin (was: Update new project wizard tests for the new version of plugin) > Update new project wizard tests for the new version of drools plugin > -------------------------------------------------------------------- > > Key: JBTIS-687 > URL: https://issues.jboss.org/browse/JBTIS-687 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: drools/ jBPM, QE > Reporter: Tomas David > Assignee: Tomas David > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-687) Update new project wizard tests for the new version of plugin

by Tomas David (JIRA)

Tomas David created JBTIS-687: --------------------------------- Summary: Update new project wizard tests for the new version of plugin Key: JBTIS-687 URL: https://issues.jboss.org/browse/JBTIS-687 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: drools/ jBPM, QE Reporter: Tomas David Assignee: Tomas David -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22276) Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22276?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-22276. ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) Resolution: Rejected I see your point. Also according to Eclipse user guidelines: {code} Guideline 5.8 Use a Browse Button whenever an existing object is referenced in a wizard. {code} Thus rejecting this one. The case with local template is a bit different because we allow users to browse 2 "different" locations and therefore we have Workspace and File System buttons, what is correct, I think. > Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22276 > URL: https://issues.jboss.org/browse/JBIDE-22276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > In New OpenShift Server Adapter wizard there is a text widget for Eclipse project. Next to it there is a Browse... button which allow to select an eclipse project from workspace. > IN New OpenShift Application Wizard there is a text widget for Eclipse project to be used for a new application. Next to it there is a Browse... button which allow to select an eclipse project from workspace. (On the same wizard page user can select a template from local file system/workspace and there we use correct buttons.) > Earlier we were using Browse... button for real browsing using native file browser/chooser. Now we use it for selecting a project from workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22276) Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22276?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22276 at 5/2/16 4:33 AM: --------------------------------------------------------------- I see your point. I should have checked it - also according to Eclipse user guidelines: {code} Guideline 5.8 Use a Browse Button whenever an existing object is referenced in a wizard. {code} Thus rejecting this one. The case with local template is a bit different because we allow users to browse 2 "different" locations and therefore we have Workspace and File System buttons, what is correct, I think. was (Author: mlabuda): I see your point. Also according to Eclipse user guidelines: {code} Guideline 5.8 Use a Browse Button whenever an existing object is referenced in a wizard. {code} Thus rejecting this one. The case with local template is a bit different because we allow users to browse 2 "different" locations and therefore we have Workspace and File System buttons, what is correct, I think. > Server Adapter Wizard, Application Wizard: Browse... button should be Workspace... button > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22276 > URL: https://issues.jboss.org/browse/JBIDE-22276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > In New OpenShift Server Adapter wizard there is a text widget for Eclipse project. Next to it there is a Browse... button which allow to select an eclipse project from workspace. > IN New OpenShift Application Wizard there is a text widget for Eclipse project to be used for a new application. Next to it there is a Browse... button which allow to select an eclipse project from workspace. (On the same wizard page user can select a template from local file system/workspace and there we use correct buttons.) > Earlier we were using Browse... button for real browsing using native file browser/chooser. Now we use it for selecting a project from workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22031) Deploy Docker wizard: set message to "Deployment Configuration & Scalability"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22031?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22031: ------------------------------------------ [~scabanovich] can you please provide more details? > Deploy Docker wizard: set message to "Deployment Configuration & Scalability" > ----------------------------------------------------------------------------- > > Key: JBIDE-22031 > URL: https://issues.jboss.org/browse/JBIDE-22031 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22253) Update to SWTBot 2.4.0

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22253?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22253: ------------------------------------ [~maxandersen], all RedDeer modules (except the recorder) have zero dependency on SWTBot. > Update to SWTBot 2.4.0 > ---------------------- > > Key: JBIDE-22253 > URL: https://issues.jboss.org/browse/JBIDE-22253 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa, target-platform > Affects Versions: 4.3.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > *Reason:* SWTBot 2.4.0 comes with several fixes (about menus) and other that JBT/JBDS can probably take advantage of > *Project page/sources:* http://eclipse.org/swtbot > *Version:* 2.4.0 > *License and owner:* EPL, Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/swtbot/releases/2.4.0 > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.4.0/ > *Include Sources:* No > *Affected JBoss Tools components:* tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > {code} > If applicable: > *non-p2 repository:* ... > *non-p2 ids:* ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-674: ----------------------------------------- Hi Max, I agree this might be a bit confusing. In fact, we deprecate the category which installs a set of runtime detectors. Some of the runtimes will be removed and some of them will be still supported (such as drools runtime detector). So, in other words we deprecate the way how to install runtime detectors. The drools runtime detector can be installed by installing Drools category. > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png, dep5.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-684) Removed org.eclipse.swtbot dependency + more refactoring

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-684?page=com.atlassian.jira.plugin.... ] stanislav kaleta resolved JBTIS-684. ------------------------------------ Resolution: Done > Removed org.eclipse.swtbot dependency + more refactoring > -------------------------------------------------------- > > Key: JBTIS-684 > URL: https://issues.jboss.org/browse/JBTIS-684 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.2.6.CR2, 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016