August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account

by Steve Speicher (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20001?page=com.atlassian.jira.plugi... ] Steve Speicher commented on JBIDE-20001: ---------------------------------------- Sounds right to me > Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-20001 > URL: https://issues.jboss.org/browse/JBIDE-20001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Steve Speicher > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Screen Shot 2015-06-09 at 10.35.54 AM.png > > > The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers. > Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3 > An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3327) Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3327?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3327. ---------------------------- Assignee: Misha Ali (was: Michelle Murray) Closing since done. Changed assignee to Misha, not Michelle. > Add OS X 10.10 Yosemite to the support matrix - JBDS 9.0 > -------------------------------------------------------- > > Key: JBDS-3327 > URL: https://issues.jboss.org/browse/JBDS-3327 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 8.0.2.GA > Reporter: Martin Malina > Assignee: Misha Ali > Fix For: 9.0.0.Beta2 > > > We have been testing primarily on Yosemite (and Mavericks) for some time and there's no reason why not include Yosemite. > This is the JBDS support matrix doc: https://access.redhat.com/articles/427493 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20203) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20203?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20203: ------------------------------------------ merged and pushed to upsteam/master > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-20203 > URL: https://issues.jboss.org/browse/JBIDE-20203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [OpenShift]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20332) [Bower] Better user experience when running 'Bower Update' on a default bower.json file

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20332?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20332: ------------------------------------- [~psrna], I have fixed it with JBIDE-20319. Console view will be shown on every "Bower Update" launch (once it will be executed console title will change to smth. like "<terminated> Bower Update") > [Bower] Better user experience when running 'Bower Update' on a default bower.json file > --------------------------------------------------------------------------------------- > > Key: JBIDE-20332 > URL: https://issues.jboss.org/browse/JBIDE-20332 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > > Running 'Run As -> Bower Update' on a default bower.json (that one created by Bower Init wizard' results in no visible action. That is under my opinion a bad user experience. I personally have hit 'Run as' 3 times to be sure something has started. > I suggest, that we show the console, with something like 'bower update terminated' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20409) [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard

by Yue Wang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20409?page=com.atlassian.jira.plugi... ] Yue Wang commented on JBIDE-20409: ---------------------------------- It's much better if you can keep the console open and gray out that red button on console, users may think forwarding is till running if they see the red button there because clicking the red button can stop port forwarding. > [origin_intservice_59]Port Forwarding Console: should stop when I stop forwarding in wizard > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20409 > URL: https://issues.jboss.org/browse/JBIDE-20409 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150731-0236-B931 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Since stop port-forwarding console can stop port forwarding, port-forwarding console should be terminated when when I stop forwarding from wizard. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20001) Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20001?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20001: ------------------------------------------ I implemented a logic (https://github.com/jbosstools/jbosstools-openshift/pull/721) where the link is only shown if the user selects "OpenShift v2" as server type and uses openshift.redhat.com as server. Sounds about right? [~jcantrill][~sspeiche]? > Confusing New->Connection dialog that tells v3 and Enterprise users to create an Online account > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-20001 > URL: https://issues.jboss.org/browse/JBIDE-20001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Steve Speicher > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Screen Shot 2015-06-09 at 10.35.54 AM.png > > > The Eclipse tooling is intended to be used with V2 Online (for now) and V3 when it is available. Also it is intended to be used with on-premise Enterprise instances, which do not require an Online account. This instruction may be confusing to these customers. > Along these lines, the V3 Server is prefilled with the URL for the online service which may not work for some time. I propose selecting a different default value for V3 > An alternative could be that after they enter the URL they could attempt to "valid it" or "open in browser". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20417) NPE while trying to create an OpenShift project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20417?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20417. --------------------------------- Labels: openshift_v3 (was: ) Assignee: Fred Bricon Fix Version/s: 4.3.0.CR1 Resolution: Done Added null check on status. The error message is now more explicit: !http://content.screencast.com/users/fbricon/folders/Jing/media/38bbc4af-d880-4e5b-909a-7fe7311e12bf/00000137.png|width=550! (although I have no idea why this is happening) > NPE while trying to create an OpenShift project > ----------------------------------------------- > > Key: JBIDE-20417 > URL: https://issues.jboss.org/browse/JBIDE-20417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) > When trying to create an openshift project, I get an exception when clicking finish : > !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! > {noformat} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > The NPE actually occurs in a catch block, where e.getStatus() is null: > {code} > } catch (OpenShiftException e) { > return OpenShiftUIActivator.statusFactory().errorStatus( > NLS.bind("Could not create project \"{0}\": {1}", getModel().getProjectName(), e.getStatus().getMessage()), e); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20417) NPE while trying to create an OpenShift project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20417?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20417: -------------------------------- Description: I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) When trying to create an openshift project, I get an exception when clicking finish : !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! {noformat} java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} The NPE actually occurs in a catch block, where e.getStatus() is null: {code} } catch (OpenShiftException e) { return OpenShiftUIActivator.statusFactory().errorStatus( NLS.bind("Could not create project \"{0}\": {1}", getModel().getProjectName(), e.getStatus().getMessage()), e); } {code} was: I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) When trying to create an openshift project, I get an exception when clicking finish : !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! The NPE actually occurs in a catch block, where e.getStatus() is null > NPE while trying to create an OpenShift project > ----------------------------------------------- > > Key: JBIDE-20417 > URL: https://issues.jboss.org/browse/JBIDE-20417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > > I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) > When trying to create an openshift project, I get an exception when clicking finish : > !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! > {noformat} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:52) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > The NPE actually occurs in a catch block, where e.getStatus() is null: > {code} > } catch (OpenShiftException e) { > return OpenShiftUIActivator.statusFactory().errorStatus( > NLS.bind("Could not create project \"{0}\": {1}", getModel().getProjectName(), e.getStatus().getMessage()), e); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20417) NPE while trying to create an OpenShift project

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20417: ----------------------------------- Summary: NPE while trying to create an OpenShift project Key: JBIDE-20417 URL: https://issues.jboss.org/browse/JBIDE-20417 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Fred Bricon I'm running OS3 as a vagrant image (https://github.com/jcantrill/jctoolbox/blob/jimmi_based_box/openshift/Vag...) When trying to create an openshift project, I get an exception when clicking finish : !http://content.screencast.com/users/fbricon/folders/Jing/media/2ce1f1c3-892d-4f25-a991-bba7af592aa5/00000136.png|width=600! The NPE actually occurs in a catch block, where e.getStatus() is null -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20332) [Bower] Better user experience when running 'Bower Update' on a default bower.json file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20332?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20332: -------------------------------------- Assignee: Ilya Buziuk > [Bower] Better user experience when running 'Bower Update' on a default bower.json file > --------------------------------------------------------------------------------------- > > Key: JBIDE-20332 > URL: https://issues.jboss.org/browse/JBIDE-20332 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript-bower > Affects Versions: 4.3.0.Beta2 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Fix For: 4.3.0.CR1 > > > Running 'Run As -> Bower Update' on a default bower.json (that one created by Bower Init wizard' results in no visible action. That is under my opinion a bad user experience. I personally have hit 'Run as' 3 times to be sure something has started. > I suggest, that we show the console, with something like 'bower update terminated' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 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 August 2015