February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19096: ---------------------------------------- Assignee: Jeff Cantrill (was: Andre Dietisheim) > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > the existing UI for v2 OpenShift: > * new connection: > !screenshot-openshift-signin.png! > * existing connection: > !existing-v2-connection.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19096: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/535, https://github.com/jbosstools/jbosstools-openshift/pull/542, https://github.com/jbosstools/jbosstools-openshift/pull/557 (was: https://github.com/jbosstools/jbosstools-openshift/pull/535, https://github.com/jbosstools/jbosstools-openshift/pull/542, https://github.com/jbosstools/jbosstools-openshift/pull/555) > Connection wizard: Allow v2 and v3 Connections > ---------------------------------------------- > > Key: JBIDE-19096 > URL: https://issues.jboss.org/browse/JBIDE-19096 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: existing-v2-connection.png, fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png > > > the existing UI for v2 OpenShift: > * new connection: > !screenshot-openshift-signin.png! > * existing connection: > !existing-v2-connection.png! > In order to allow us to present v2 and v3 connections we have to change the connection wizard: > When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different: > * v2 connections currently use username/password (and will most likely also allow x509, kerberos) > * v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3359 at 2/23/15 7:10 AM: -------------------------------------------------------------- [~maxandersen], I think you misunderstand. When we tested 8.0.0, we tested this with the 8.0.0 central bits - it worked. When we tested 8.0.2, we tested this with 8.0.2 central* update site - it worked/works. But now it turns out that it does not work in JBDS 8.0.0 - central* is now 8.0.2 in both. So JBDS 8.0.0 with 8.0.2 central* has this issue. So the only way to catch this in testing would be if with every point release we test central in older releases, e.g. during JBDs 8.0.2 testing period, we would need to test central in JBDS 8.0.0, 8.0.1 and 8.0.2.) *central means central update site in this context - we use the /stable/ url which always has the latest was (Author: mmalina): [~maxandersen], I think you misunderstand. When we tested 8.0.0, we tested this with the 8.0.0 central bits - it worked. When we tested 8.0.2, we tested this with 8.0.2 central update site - it worked/works. But now it turns out that it does not work in JBDS 8.0.0 - central is now 8.0.2 in both. So JBDS 8.0.0 with 8.0.2 central has this issue. So the only way to catch this in testing would be if with every point release we test central in older releases, e.g. during JBDs 8.0.2 testing period, we would need to test central in JBDS 8.0.0, 8.0.1 and 8.0.2. > Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3359: ------------------------------------- [~maxandersen], I think you misunderstand. When we tested 8.0.0, we tested this with the 8.0.0 central bits - it worked. When we tested 8.0.2, we tested this with 8.0.2 central update site - it worked/works. But now it turns out that it does not work in JBDS 8.0.0 - central is now 8.0.2 in both. So JBDS 8.0.0 with 8.0.2 central has this issue. So the only way to catch this in testing would be if with every point release we test central in older releases, e.g. during JBDs 8.0.2 testing period, we would need to test central in JBDS 8.0.0, 8.0.1 and 8.0.2. > Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Pete Muir commented on JBDS-3162: --------------------------------- {quote}As I've already said, it would seem very strange to have JBoss EAP, JBoss EWP, JBoss AS, JBoss JPP, and JBoss Fuse Service Works. It would be more reasonable to lobby that FSW simply become an approved abbreviation.{quote} Of these, correct ones are: * JBoss EAP * JBoss AS are correct. * JBoss EWP should be JBoss Web Server * JBoss JPP should be JBoss Portal Note also that the customer portal article that [~mmusaji] linked is wrong, JBoss FSW is not approved name for the JBoss Fuse Service Works product. The product code can be used in urls, file name, directory names etc. but shouldn't be used in UIs when describing a product. Unfortunately there is not much that can be done here for the existing names, they need to be the approved abbreviation. I would suggest we work work the BU to ensure that a rule is put in place for the max length of the approved abbreviations. > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 9.0.0.Alpha2 > > Attachments: JBDS-3162.suggested.png, JBDS-3162.suggested2.png > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19211) Project Examples New and Noteworthy for 4.3.0.Alpha1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19211?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19211. --------------------------------------- Resolution: Rejected > Project Examples New and Noteworthy for 4.3.0.Alpha1 > ---------------------------------------------------- > > Key: JBIDE-19211 > URL: https://issues.jboss.org/browse/JBIDE-19211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Project Examples is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19209) Maven New and Noteworthy for 4.3.0.Alpha1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19209?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19209. --------------------------------------- Resolution: Rejected > Maven New and Noteworthy for 4.3.0.Alpha1 > ----------------------------------------- > > Key: JBIDE-19209 > URL: https://issues.jboss.org/browse/JBIDE-19209 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Maven is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Maven by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19215) OpenShift New and Noteworthy for 4.3.0.Alpha1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19215?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19215. --------------------------------------- Resolution: Rejected nothing new since we stayed on v2 for now. > OpenShift New and Noteworthy for 4.3.0.Alpha1 > --------------------------------------------- > > Key: JBIDE-19215 > URL: https://issues.jboss.org/browse/JBIDE-19215 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3359: ------------------------------------------- [~psrna] at 8.0.0.GA release there was no differences. in 8.0.2 we update hybrid and other parts. At time of 8.0.2.GA testing the mails from release engineering listed the central urls to use for testing Central when doing updates. My theory is that QE might only tested against 8.0.0.GA not the 8.0.2.GA updatesite content. Can't you give me the full text description in under "show original error and build my own solution" that you get ? > Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19350) EAR project deployment to remote server (management) gets stuck

by Martin Malina (JIRA)

Martin Malina created JBIDE-19350: ------------------------------------- Summary: EAR project deployment to remote server (management) gets stuck Key: JBIDE-19350 URL: https://issues.jboss.org/browse/JBIDE-19350 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.0.Alpha1 Reporter: Martin Malina Assignee: Rob Stryker Attachments: remote-publishing-stuck.png I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %). I used the project from JBIDE-19043 - see "Steps to Reproduce". I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015