January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3566) include AERI in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3566: ------------------------------------------- To be clear, yes - lets get this into Beta2, please. > include AERI in JBDS > -------------------- > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) JBDS Installer should be EPL licensed

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3557: ------------------------------------------- This jira is just about the installer being EPL. That we have LGPL, ASL and other opensource licenses in the "output" of the installer should not limit our ability to license the installer under EPL. i.e. before the installer was GPL and we had EPL in the installed result. Thus no, LGPL in hibernate tools/jsf plugin is not relevant to this jira. > JBDS Installer should be EPL licensed > ------------------------------------- > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Nick Boldt > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3566) include AERI in JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3566: ------------------------------------------- I will have more info next week, but including AERI would be a good thing to do no matter if we have an endpoint or not IMO. It is optional for users to submit the reports and we would be contributing back data to eclipse.org about crashes/errors. > include AERI in JBDS > -------------------- > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 9.1.0.Beta2, 10.0.0.Alpha1 > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-703) Release Notes for 9.0.0 contain duplication and wrong text for known issue

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-703?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-703: ------------------------------- Affects Version/s: 9.0.0 > Release Notes for 9.0.0 contain duplication and wrong text for known issue > -------------------------------------------------------------------------- > > Key: TOOLSDOC-703 > URL: https://issues.jboss.org/browse/TOOLSDOC-703 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 9.0.0 > Environment: Build Name: 23115, 9.0.0 Release Notes-9.0 > Build Date: 06-10-2015 14:28:25 > Topic ID: 44858-771229 [Latest] > Reporter: Mustafa Musaji > Assignee: Misha Ali > Priority: Blocker > > Title: Known Issues > Describe the issue: > JBDS-3470: Toolbars + Icons unusable on UHD screens. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Suggestions for improvement: > JBIDE-19633 has nothing to do with UHD and the line should be removed > Additional information: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-703) Release Notes for 9.0.0 contain duplication and wrong text for known issue

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-703?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-703: ------------------------------- Sprint: 04-Jan >> 17-Jan 2016-JBDS/JBT > Release Notes for 9.0.0 contain duplication and wrong text for known issue > -------------------------------------------------------------------------- > > Key: TOOLSDOC-703 > URL: https://issues.jboss.org/browse/TOOLSDOC-703 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Release Notes > Affects Versions: 9.0.0 > Environment: Build Name: 23115, 9.0.0 Release Notes-9.0 > Build Date: 06-10-2015 14:28:25 > Topic ID: 44858-771229 [Latest] > Reporter: Mustafa Musaji > Assignee: Misha Ali > Priority: Blocker > > Title: Known Issues > Describe the issue: > JBDS-3470: Toolbars + Icons unusable on UHD screens. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1. When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Suggestions for improvement: > JBIDE-19633 has nothing to do with UHD and the line should be removed > Additional information: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20497) New Application shows New Project wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20497?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20497: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > New Application shows New Project wizard > ----------------------------------------- > > Key: JBIDE-20497 > URL: https://issues.jboss.org/browse/JBIDE-20497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > When running Create New Application and I have no project a separate dialog pops up asking for Create New project with no real explanation. > Could the Create project step not be something that gets to be a page in New Application or somehow not be so "separate" and at least with some info that you need to create project before creating application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21125) There was an error retrieving children in the OpenShift explorer Unable to find the connection for a %s named %s

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21125?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21125. ------------------------------- Fix Version/s: (was: 4.3.1.Beta2) Resolution: Duplicate Issue Closing as duplicate of JBIDE-21431 > There was an error retrieving children in the OpenShift explorer Unable to find the connection for a %s named %s > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21125 > URL: https://issues.jboss.org/browse/JBIDE-21125 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > > Nightly Build from (Nov 20) > File New OpenShift Application > eap6-basic-sti > produces: > There was an error retrieving children in the OpenShift explorer > Unable to find the connection for a %s named %s > This version of Openshift > https://github.com/hferentschik/openshift-vagrant > oc version > oc v3.1.0.4-3-ga6353c7 > kubernetes v1.1.0-origin-1107-g4c8e6f4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20731) Finish button in Import OpenShift Application wizard does nothing if repo is already cloned

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20731?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20731: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Finish button in Import OpenShift Application wizard does nothing if repo is already cloned > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20731 > URL: https://issues.jboss.org/browse/JBIDE-20731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > Finish button in OpenShift 3 Import OpenShift Application wizard is enabled if the wizard is opened via context menu of a build config even though the repository is already cloned in default git location. This allows users to click on Finish button, but nothing happens. If Import OpenShift Application is opened via context menu of a project or connection or the build config in Import OpenShift Application is selected, then the Finish button for already cloned repositories of a build config is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20597: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: docker > Fix For: 4.3.1.CR1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20513: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.1.CR1 > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016