September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16965) Application menu not shown when browsersim is opened

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16965?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16965: ------------------------------------------------ Moved to 4.3.x since Upstream bug was moved to 4.5 > Application menu not shown when browsersim is opened > ---------------------------------------------------- > > Key: JBIDE-16965 > URL: https://issues.jboss.org/browse/JBIDE-16965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1 > OS X Mavericks > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Labels: upstream > Fix For: 4.3.x > > Attachments: browsersim-menu.png > > > *Upstream bug* https://bugs.eclipse.org/bugs/show_bug.cgi?id=426062 > When I open browsersim by clicking the icon in JBDS menu bar, browsersim is launched, I can see the app in the dock, the window is active, but for some reason the system menu bar stays locked in JBoss Developer Studio. But the menu is dead - the only way to get the Browsersim menu is to swich to some other app and then back to Browsersim. > !browsersim-menu.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16965) Application menu not shown when browsersim is opened

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16965?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-16965: ------------------------------------------- Fix Version/s: 4.3.x (was: 4.2.0.Final) > Application menu not shown when browsersim is opened > ---------------------------------------------------- > > Key: JBIDE-16965 > URL: https://issues.jboss.org/browse/JBIDE-16965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1 > OS X Mavericks > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > Labels: upstream > Fix For: 4.3.x > > Attachments: browsersim-menu.png > > > *Upstream bug* https://bugs.eclipse.org/bugs/show_bug.cgi?id=426062 > When I open browsersim by clicking the icon in JBDS menu bar, browsersim is launched, I can see the app in the dock, the window is active, but for some reason the system menu bar stays locked in JBoss Developer Studio. But the menu is dead - the only way to get the Browsersim menu is to swich to some other app and then back to Browsersim. > !browsersim-menu.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12571) Connection wizard: Eclipse preferences: allow users to define a default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12571?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12571: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Connection wizard: Eclipse preferences: allow users to define a default server > ------------------------------------------------------------------------------ > > Key: JBIDE-12571 > URL: https://issues.jboss.org/browse/JBIDE-12571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Labels: connection_wizard, new_and_noteworthy > Fix For: 4.3.x > > Attachments: 2012-09-10 13.10.bmml, 2012-09-10 13.10.bmml, 2012-09-10 13.10.png > > > Add UI to the preferences that allows users to provide a default OpenShift server to connect to. In terms of widget we need a text-field for the server url and a checkbox that allows people to refer to the default server that is defined in the openshift configfurations (~/.openshift/express.conf and /etc/openshift/express.conf). If the checkbox is checked, the text-field is disabled, prefilled with the server that is present in the (rhc cli-tooling) openshift configuration. Once unchecked the user can enter a default server and override the openshift server that is configured in the configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16040) Embed wizard: Web balancer cartridge should not be listed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16040?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16040: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Embed wizard: Web balancer cartridge should not be listed > --------------------------------------------------------- > > Key: JBIDE-16040 > URL: https://issues.jboss.org/browse/JBIDE-16040 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: embed_wizard > Fix For: 4.3.x > > Attachments: haproxy_cartridge.png > > > There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed. > !haproxy_cartridge.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16168) Server Adapter: should not publish if the application is not running

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16168?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16168: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Server Adapter: should not publish if the application is not running > -------------------------------------------------------------------- > > Key: JBIDE-16168 > URL: https://issues.jboss.org/browse/JBIDE-16168 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: server_adapter > Fix For: 4.3.x > > > If you pick "Publish" from the context menu of an OpenShift Server Adapter, then the adapter will git push to the OpenShift git repository. > This makes no sense if the application, that holds the git repository, is not running. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support explicit deployments

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-2864 at 9/3/14 10:57 AM: ----------------------------------------------------------------- this went out of time for JBDS 8.0.0 GA. We eventually want this to happen in upcoming releases. Suggesting to move this to JBDS 9.0.0 GA was (Author: adietish): this went out of time for JBDS 8.0.0 GA. We eventually want this to happen in upcoming releases > Support explicit deployments > ---------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.0.x > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3139) Error when isnstalling AngularJS from JBoss Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3139?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3139: -------------------------------------- [~dgolovin] I noticed org.jboss.tools.jst.jsdt is not part of default JBDS installation (from installer). Is this expected or should it be included in JBDS feature? > Error when isnstalling AngularJS from JBoss Central > --------------------------------------------------- > > Key: JBDS-3139 > URL: https://issues.jboss.org/browse/JBDS-3139 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.0.CR1-v20140831-0335-B201 > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Critical > Labels: respin-a > Fix For: 8.0.0.CR1 > > > Getting this error when trying to install AngularJS from JBoss Central: > The following connectors are not available: AngularJS for WebTools -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support explicit deployments

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2864: ---------------------------------------- this went out of time for JBDS 8.0.0 GA. We eventually want this to happen in upcoming releases > Support explicit deployments > ---------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.0.x > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2868: ----------------------------- CDW release: - (was: ?) > Support multiple protocols when talking to OpenShift servers > ------------------------------------------------------------ > > Key: JBDS-2868 > URL: https://issues.jboss.org/browse/JBDS-2868 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andre Dietisheim > Fix For: 8.0.x > > > The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2868: ----------------------------------- CDW devel_ack: - (was: ?) Status: New (was: New) > Support multiple protocols when talking to OpenShift servers > ------------------------------------------------------------ > > Key: JBDS-2868 > URL: https://issues.jboss.org/browse/JBDS-2868 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andre Dietisheim > Fix For: 8.0.x > > > The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014