June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21355) Properties: Allow to edit resources inline

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21355: ------------------------------------- Summary: Properties: Allow to edit resources inline (was: Edit resource properties from Properties view) > Properties: Allow to edit resources inline > ------------------------------------------ > > Key: JBIDE-21355 > URL: https://issues.jboss.org/browse/JBIDE-21355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.5.x > > > Resources are currently editable from a source editor (see JBIDE-20761). It'd be nice to have a more fined grained approach, and have the properties be directly editable from the Properties view (eg. modify label, change git source url) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21331: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Connection wizard: it looks as if the wizard is creating new connection instances several times > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-21331 > URL: https://issues.jboss.org/browse/JBIDE-21331 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > > The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification) > {code:title=ConnctionWizardPageModel} > private void initEditConnection(IConnection connection) { > this.selectedConnection = connection; > this.connection = connection.clone(); > ... > {code} > {code:title=ConnctionWizardPageModel} > public IStatus connect() { > ... > try { > this.connection = createConnection(); > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21448: ------------------------------------------ [~jpechanec] can you please provide the link to the project "EAP CLI" that you are refering to? > Allow port-forwarding of ports not defined on pod metadata > ---------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21448: ------------------------------------- Summary: Port Forwarding: Allow port-forwarding of ports not defined on pod metadata (was: Allow port-forwarding of ports not defined on pod metadata) > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21448: ------------------------------------- Labels: openshift_v3 port_forwarding_wizard (was: ) > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21355) Edit resource properties from Properties view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21355?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21355: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Edit resource properties from Properties view > --------------------------------------------- > > Key: JBIDE-21355 > URL: https://issues.jboss.org/browse/JBIDE-21355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.5.x > > > Resources are currently editable from a source editor (see JBIDE-20761). It'd be nice to have a more fined grained approach, and have the properties be directly editable from the Properties view (eg. modify label, change git source url) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21448: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Allow port-forwarding of ports not defined on pod metadata > ---------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4383?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-4383. ------------------------------- This is being done in JBDS-4399 . > Add support for installing EAP from devsuite installers > ------------------------------------------------------- > > Key: JBDS-4383 > URL: https://issues.jboss.org/browse/JBDS-4383 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21448: ------------------------------------- Priority: Critical (was: Major) > Allow port-forwarding of ports not defined on pod metadata > ---------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4383) Add support for installing EAP from devsuite installers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4383?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-4383: -------------------------------- Component/s: platform-installer (was: integration-platform) > Add support for installing EAP from devsuite installers > ------------------------------------------------------- > > Key: JBDS-4383 > URL: https://issues.jboss.org/browse/JBDS-4383 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > Related to JBDS-4362, when we eliminate the EAP bundled installer jar, we need to also add support to the devsuite installer to install EAP from there instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017