February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21654) add aeri for jboss tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21654?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21654: ---------------------------------------- Component/s: aeri (was: usage) > add aeri for jboss tools > ------------------------ > > Key: JBIDE-21654 > URL: https://issues.jboss.org/browse/JBIDE-21654 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > We have the possibility to get at test environment for error reporting for JBoss Tools. > For that we need Mars.2 (pre-Mars.2 will not work) and the latest aeri. > Thus we can't add it by default to i.e. usage (unless we want to force upgrade everyone), but we can at least include it in the default set. > In Neon we can add to usage. > jira here is to capture this + implement the extension point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21356) Make OpenShift 3 resource edition more robust

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21356?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21356. --------------------------------- Assignee: Fred Bricon Resolution: Done Made sure to fall back on wst's JSON editor (or the default editor, if the former is unavailable), in case opening the current editor fails. Had to append the resource name with .json in order to get colored syntax in the JSON editor > Make OpenShift 3 resource edition more robust > --------------------------------------------- > > Key: JBIDE-21356 > URL: https://issues.jboss.org/browse/JBIDE-21356 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Following [~scabanovich]'s comment in JBIDE-20761: > {quote} > My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem. > {quote} > Until we can rely on Eclipse's upcoming JSON editor (in Neon), we should try to harden editor detection/opening -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21675) Text editor of OpenShift resource should provide more information about resource

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21675?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21675. --------------------------------- Resolution: Done Added project as prefix to resource name. In master and maintenance. > Text editor of OpenShift resource should provide more information about resource > -------------------------------------------------------------------------------- > > Key: JBIDE-21675 > URL: https://issues.jboss.org/browse/JBIDE-21675 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > When I choose Edit.. in context menu of an OpenShift resource, its open a new text editor with JSON of resource. Currently name/title of such text editor is in format "resource type : resource name" (example "Image Stream : bug-consolidator"). If I have more such editor opened, e.g. I have a staging project, testing project and production project with same resource name, it is difficult to find out to which resource the content of editor belongs (it is possible but it requires to read content and find namespace or selflink which contain project name). > It would be nice if editor of OpenShift resource would contain at least project name in its name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21648: ------------------------------------- should be fine :D > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Priority: Blocker > Fix For: 4.3.2.Final > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21460) Server adapter: NPE at Show In Web Browser if connection is not connected

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21460?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21460: ----------------------------------- Assignee: Viacheslav Kabanovich > Server adapter: NPE at Show In Web Browser if connection is not connected > ------------------------------------------------------------------------- > > Key: JBIDE-21460 > URL: https://issues.jboss.org/browse/JBIDE-21460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > Attachments: not-authorized-error.png > > > 1. Create an OpenShift connection, do not choose save password/token. > 2. Create an OpenShift server for the connection. > 3. Close Eclipse with Server view active > 4. Restart Eclipse, select Server view. > 5. In context menu of the server, select Show In Web Browser. > 6. 'Sign In' dialog appears, select cancel. > (Note: First time when I got it, dialog did not appear, later I could not repeat steps that would skip the dialog.) > 7. Failure: NPE while executing getWelcomePageUrl(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-21648: ------------------------------------------ Sure! Do we have a deadline? I can do it by Feb 18th. Otherwise I'll have to find a time > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Priority: Blocker > Fix For: 4.3.2.Final > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21703) Server adapter wizard: pod deployment path is always default (/opt/app-root/src)

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21703?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-21703: ------------------------------------- Assignee: Jeff Cantrill (was: Andre Dietisheim) > Server adapter wizard: pod deployment path is always default (/opt/app-root/src) > -------------------------------------------------------------------------------- > > Key: JBIDE-21703 > URL: https://issues.jboss.org/browse/JBIDE-21703 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21677) Change branding for EAP server types

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21677?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21677: -------------------------------- Attachment: JBIDE-21677.png Attaching screenshot of shadowman in action > Change branding for EAP server types > ------------------------------------ > > Key: JBIDE-21677 > URL: https://issues.jboss.org/browse/JBIDE-21677 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: JBIDE-21677.png > > > 1) Change branding for EAP small icon to shadowman. Ask Catherine > 2) Change name to "Red Hat JBoss Enterprise Application Platform x.y" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21700) Listen to pod redeployment after changing deployment configuration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21700?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21700: ----------------------------------- Assignee: Jeff Cantrill > Listen to pod redeployment after changing deployment configuration > ------------------------------------------------------------------ > > Key: JBIDE-21700 > URL: https://issues.jboss.org/browse/JBIDE-21700 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > We need an easy way to detect a deployment configuration change triggered a new deployment and then be notified of its completion -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21100. --------------------------------- Resolution: Cannot Reproduce Bug Ok! Thanks for the update! > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016