April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22149) Server adapter wizard: nothing happens if I select a route and pick "Server Adapter" from the context menu

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22149?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22149. --------------------------------- Context menu has been removed. Verified in JBDS 10.0.0.Alpha1 B5227. > Server adapter wizard: nothing happens if I select a route and pick "Server Adapter" from the context menu > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22149 > URL: https://issues.jboss.org/browse/JBIDE-22149 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Fred Bricon > Labels: openshift_v3, respin-b, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22150) Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22150?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22150. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22150 > URL: https://issues.jboss.org/browse/JBIDE-22150 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > When opening a New OpenShift 3 Server Adapter wizard via context menu of a service in Properties view, the selected service from properties view is not preselected in the wizard. This is happening for more services within one project. It select first service under a project in the wizard. Preselection of a service for different projects works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22154) IllegalArgumentException thrown when starting debug mode with services missing env vars

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22154?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22154. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5227. > IllegalArgumentException thrown when starting debug mode with services missing env vars > --------------------------------------------------------------------------------------- > > Key: JBIDE-22154 > URL: https://issues.jboss.org/browse/JBIDE-22154 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > Create an openshift app following the steps from https://htmlpreview.github.io/?https://github.com/redhat-helloworld-msa/h... > After importing the maven project in eclipse and creating a server adapter, if you try to start in debug mode, an exception will be thrown because we're trying to update the env var list in the deployment config, but it doesn't already exists -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22242?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22242: --------------------------------------- Priority set to critical because of UX perspective. > OpenShift Explorer: Reorganize context menus > -------------------------------------------- > > Key: JBIDE-22242 > URL: https://issues.jboss.org/browse/JBIDE-22242 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3, ux > Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png > > > It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service). > See screenshots of context menus: > connection > !connection_cm.png! > project > !project_cm.png! > service > !service_cm.png! > pod > !pod_cm.png! > Here is the guideline how should context menus look like > https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22242?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22242: ---------------------------------- Priority: Critical (was: Major) > OpenShift Explorer: Reorganize context menus > -------------------------------------------- > > Key: JBIDE-22242 > URL: https://issues.jboss.org/browse/JBIDE-22242 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3, ux > Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png > > > It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service). > See screenshots of context menus: > connection > !connection_cm.png! > project > !project_cm.png! > service > !service_cm.png! > pod > !pod_cm.png! > Here is the guideline how should context menus look like > https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22242: ------------------------------------- Summary: OpenShift Explorer: Reorganize context menus Key: JBIDE-22242 URL: https://issues.jboss.org/browse/JBIDE-22242 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service). See screenshots of context menus: connection !connection_cm.png! project !project_cm.png! service !service_cm.png! pod !pod_cm.png! Here is the guideline how should context menus look like https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-709: -------------------------------------------- > WIP: Convert doc to md > JBDS 9.1 GA: Document a use case for Forge Tooling > -------------------------------------------------- > > Key: TOOLSDOC-709 > URL: https://issues.jboss.org/browse/TOOLSDOC-709 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Forge > Fix For: 9.1 GA > > > Document a use case for Forge tooling. > 1. Draft a potential use case for what users may want to do with forge. > 2. Get review on use case idea from a relevant SME or QE person > 3. Write an intro and flesh out the use case with relevant screenshots > 4. Get QE review > 5. Create upstream and downstream versions of approved content. > a. Add CSP version to customer portal > b. Send Misha upstream version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22232) New OpenShift Application wizard: Make selection of an OS project in application wizard consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22232?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22232: ------------------------------------- Description: When opening a New OpenShift Application wizard from context menu of a connection or via central or via shell menu File - New - OpenShift Application, the selected OpenShift project in the wizard is random (e.g. having several project aaa, bbb, ccc, ddd, eee1, eee2, eee3 the order of projects was following eee1 aaa bbb bbb bbb ccc eee1 aaa bbb). We could preselect a first project to have it consistent. steps to reproduce: # ASSERT: make sure that you have several OpenShift projects # EXEC: launch application wizard Result: The project that is pre-selected in the wizard is not consistent. was:When opening a New OpenShift Application wizard from context menu of a connection or via central or via shell menu File - New - OpenShift Application, the selected OpenShift project in the wizard is random (e.g. having several project aaa, bbb, ccc, ddd, eee1, eee2, eee3 the order of projects was following eee1 aaa bbb bbb bbb ccc eee1 aaa bbb). We could preselect a first project to have it consistent. > New OpenShift Application wizard: Make selection of an OS project in application wizard consistent > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-22232 > URL: https://issues.jboss.org/browse/JBIDE-22232 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard > Fix For: 4.4.0.Alpha1 > > > When opening a New OpenShift Application wizard from context menu of a connection or via central or via shell menu File - New - OpenShift Application, the selected OpenShift project in the wizard is random (e.g. having several project aaa, bbb, ccc, ddd, eee1, eee2, eee3 the order of projects was following eee1 aaa bbb bbb bbb ccc eee1 aaa bbb). We could preselect a first project to have it consistent. > steps to reproduce: > # ASSERT: make sure that you have several OpenShift projects > # EXEC: launch application wizard > Result: > The project that is pre-selected in the wizard is not consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3850: ------------------------------------- [~dgolovin], [~jrichter1] these are my findings so far: * I found two live JS code coverage tools - [Istanbul|https://github.com/gotwarlost/istanbul] and [JSCover|http://tntim96.github.io/JSCover] * JSCover is implemented in Java, Istanbul is implemented in JavaScript * Istanbul seems to be preferred by JS community * Istanbul can be integrated with Mocha, Jasmine and Karma I suggest that we use *Istanbul* We have 3 types of tests that should generate code coverage statistics: # unit tests - multi-platform, they only need Node.js, launched using Mocha, run on _npm test_ # browser tests - multi-platform, they need Node.js, launched using Karma, they test Angular-specific code (directives etc), run on _npm test_ # ui tests - platform-specific, run with built installer binary, using Protractor, run on _npm run ui-test_ For now, I only focused on unit tests. I have PoC on my feature branch but # I was not able to run it with Babel 5 # when we want to upgrade to Babel 6, we either need to wait for JSPM 0.17 (cannot estimate when will be released) or remove JSPM completely (JBDS-3769) which is half-way done on my feature branch (only need to fix Karma tests) # when I removed JSPM, I still need to use latest development release of Istanbul (1.0.0-alpha.2) instead of latest stable release (0.4.3) [~dgolovin], [~jrichter1] how do we want to proceed? > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha1 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-729) JBDS 9.1 GA: Release Notes

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-729?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-729: -------------------------------------------- [~mhusnain], I have not been able to publish the RNs due to the publican error that I get after I run rhpkg. Can you please publish them once you are in office on Tuesday? Thanks! > JBDS 9.1 GA: Release Notes > -------------------------- > > Key: TOOLSDOC-729 > URL: https://issues.jboss.org/browse/TOOLSDOC-729 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > Create release notes for GA -- 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 April 2016