May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3851) Refactor the gulp package task

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3851?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3851: ------------------------------ Summary: Refactor the gulp package task (was: Split gulpfile.js to multiple modules to simplify maintenance) > Refactor the gulp package task > ------------------------------ > > Key: JBDS-3851 > URL: https://issues.jboss.org/browse/JBDS-3851 > Project: Red Hat Developer Studio (DevStudio) > 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 > > > Split Gulp task 'package' into multiple separate tasks -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22291) Deploy Docker Wizard: Add connection info

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22291: -------------------------------- Story Points: 2 > Deploy Docker Wizard: Add connection info > ----------------------------------------- > > Key: JBIDE-22291 > URL: https://issues.jboss.org/browse/JBIDE-22291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22273) Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22273?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22273: ---------------------------------------- Fixing JBIDE-22256 should fix this. [~mmalina]: I let you decide whether it's better to keep this issue open to remind about checking it, or to close it since it won't require additional development/integration effort compared to JBIDE-22256. > Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory > ----------------------------------------------------------------- > > Key: JBIDE-22273 > URL: https://issues.jboss.org/browse/JBIDE-22273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > > When I instal JBT 4.4.0.Alpha1 nightly into Eclipse Java EE Neon M6, I get this after starting Eclipse: > {code} > Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory: {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand} vs {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand@25fb43a9} > {code} > It's actually twice there and it then happens again at various times. > I'm on Mac. And BTW I haven't seen this in JBDS, only in JBT. -- 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 Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-674: ---------------------------------- [~maxandersen] [~apodhrad] - Hey Max - Andrej beat me to it - since the drools runtime detector will be the only one left I've eliminated the runtime detector category and moved the drools runtime detector back under the BRMS 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] (JBIDE-22291) Deploy Docker Wizard: Add connection info

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22291: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 > Deploy Docker Wizard: Add connection info > ----------------------------------------- > > Key: JBIDE-22291 > URL: https://issues.jboss.org/browse/JBIDE-22291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22289) Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22289?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22289: ------------------------------------- Priority: Critical (was: Major) > Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22289 > URL: https://issues.jboss.org/browse/JBIDE-22289 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > If I start typing name of image in Deploy Image to OpenShift wizard in the Image Name: text widget, suggestions are provided (autocomplete). If I select an image in this suggestion box by hitting Enter key, and then click by mouse on Next button, the next wizard page (Deployment Configuration and Scalability) shows this suggestion box again and on top, even it disappeared in previous wizard page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22289) Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22289?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22289: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 > Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22289 > URL: https://issues.jboss.org/browse/JBIDE-22289 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > If I start typing name of image in Deploy Image to OpenShift wizard in the Image Name: text widget, suggestions are provided (autocomplete). If I select an image in this suggestion box by hitting Enter key, and then click by mouse on Next button, the next wizard page (Deployment Configuration and Scalability) shows this suggestion box again and on top, even it disappeared in previous wizard page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22277 at 5/2/16 8:19 AM: ------------------------------------------------------------------ [~jeffmaury] good idea! I'd implement the ability to read the kubeconfig in openshift-restclient-java (https://issues.jboss.org/projects/OSJC in jira and https://github.com/openshift/openshift-restclient-java on github) - something we wished to have for a long time already. was (Author: adietish): [~jeffmaury] good idea! I'd implement the ability to read the kubeconfig in openshift-restclient-java ([OSJC|https://issues.jboss.org/projects/OSJC] in jira and https://github.com/openshift/openshift-restclient-java in github. > Auto guess Openshift connections > -------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22277: ------------------------------------------ [~jeffmaury] good idea! I'd implement the ability to read the kubeconfig in openshift-restclient-java ([OSJC|https://issues.jboss.org/projects/OSJC] in jira and https://github.com/openshift/openshift-restclient-java in github. > Auto guess Openshift connections > -------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22278) Explorer: should be made visible when a new Connection is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22278?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22278: ------------------------------------- Summary: Explorer: should be made visible when a new Connection is created (was: OpenShift Explorer should be made visible when a new Connection is created) > Explorer: should be made visible when a new Connection is created > ----------------------------------------------------------------- > > Key: JBIDE-22278 > URL: https://issues.jboss.org/browse/JBIDE-22278 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Labels: connection_wizard, explorer, openshift_v3 > Fix For: 4.4.x > > > OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. > Could be done through a connection listener in the UI activator -- 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