February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3360) Allign bits offered in JBoss Central with installed version of JBDS

by Martin Malina (JIRA)

Martin Malina created JBDS-3360: ----------------------------------- Summary: Allign bits offered in JBoss Central with installed version of JBDS Key: JBDS-3360 URL: https://issues.jboss.org/browse/JBDS-3360 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: central, updatesite Affects Versions: 8.0.2.GA Reporter: Martin Malina The problem in JBDS-3359 shows a broader issue. (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.) Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites: https://devstudio.redhat.com/updates/8.0/ Initially this update site contained JBDS 8.0.0 core + 8.0.0 central. But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users: 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits) Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also. I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :) -- 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.0 without triggering p2 remediation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3359: ------------------------------------ Can we clearly state the requirement that we want to see fulfilled and tested? Are we saying that: At the point in time when version N of JBDS is released, users running on release (N-1, N-2, etc.) who choose to not update to release N, should still be able to build/run all examples/quickstarts and build new projects from archetypes in Central, and JBDS should perform all necessary updates - all without forcing the user to update all of JBDS? > Cannot install Hybrid Mobile tools onto 8.0.0 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.0 without triggering p2 remediation

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3359: ------------------------------- Comment: was deleted (was: Following up on Martin's questions - how will we define the update paths that we will support? Just to confirm - are we talking about supporting users' being able to update selected subsets of new plugins that we release in JBDS updates - and not require users to update all of JBDS? Which subsets of plugin updates will we test and support? ) > Cannot install Hybrid Mobile tools onto 8.0.0 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.0 without triggering p2 remediation

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-3359: ---------------------------------- I've change the incorrect title of this jira from: "Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation" to "Cannot install Hybrid Mobile tools onto *8.0.0* without triggering p2 remediation" > Cannot install Hybrid Mobile tools onto 8.0.0 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.0 without triggering p2 remediation

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3359: ----------------------------- Summary: Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation (was: Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation) > Cannot install Hybrid Mobile tools onto 8.0.0 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 Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-3359: ---------------------------------- This is the error in 8.0.0.GA: {code} Your original request has been modified. "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead. "JBoss Tools LiveReload" is already present because other installed software requires it. It will be added to the installed software list. Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Tools Mobile Browser Simulator 3.6.1.Final-v20141209-0425-B46 (org.jboss.tools.vpe.browsersim.feature.feature.group 3.6.1.Final-v20141209-0425-B46) Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141020-1042-B317 (com.jboss.devstudio.core.package 8.0.0.GA-v20141020-1042-B317) Only one of the following can be installed at once: JBoss Tools Mobile Browser Simulator 3.6.0.Final-v20141016-1910-B34 (org.jboss.tools.vpe.browsersim.feature.feature.jar 3.6.0.Final-v20141016-1910-B34) JBoss Tools Mobile Browser Simulator 3.6.1.Final-v20141209-0425-B46 (org.jboss.tools.vpe.browsersim.feature.feature.jar 3.6.1.Final-v20141209-0425-B46) Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141020-1042-B317 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141020-1042-B317) To: org.jboss.tools.vpe.browsersim.feature.feature.group [3.6.0.Final-v20141016-1910-B34] Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141020-1042-B317 (com.jboss.devstudio.core.package 8.0.0.GA-v20141020-1042-B317) To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141020-1042-B317] Cannot satisfy dependency: From: JBoss Tools Mobile Browser Simulator 3.6.0.Final-v20141016-1910-B34 (org.jboss.tools.vpe.browsersim.feature.feature.group 3.6.0.Final-v20141016-1910-B34) To: org.jboss.tools.vpe.browsersim.feature.feature.jar [3.6.0.Final-v20141016-1910-B34] Cannot satisfy dependency: From: JBoss Tools Mobile Browser Simulator 3.6.1.Final-v20141209-0425-B46 (org.jboss.tools.vpe.browsersim.feature.feature.group 3.6.1.Final-v20141209-0425-B46) To: org.jboss.tools.vpe.browsersim.feature.feature.jar [3.6.1.Final-v20141209-0425-B46] {code} > 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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3359: ------------------------------------ Following up on Martin's questions - how will we define the update paths that we will support? Just to confirm - are we talking about supporting users' being able to update selected subsets of new plugins that we release in JBDS updates - and not require users to update all of JBDS? Which subsets of plugin updates will we test and support? > 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-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: ------------------------------------- Comment: was deleted (was: The basic implementation works. Bugs and lacking features will be filed to new jiras) > 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 commented on JBIDE-19096: ------------------------------------------ [~jcantrill] can you please review my PR https://github.com/jbosstools/jbosstools-openshift/pull/557? > 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 edited comment on JBIDE-19096 at 2/23/15 7:59 AM: ------------------------------------------------------------------- The basic implementation works. Bugs and lacking features will be filed to new jiras was (Author: adietish): merged and pushed to upstream/master. The basic implementation works. Bugs and lacking features will be filed to new jiras > 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

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