June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19829: ---------------------------------- Agreed. This was going to be part of the cleanup work that needs to be done. -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering Red Hat Office: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Add Oauth support to the Openshift Connection Wizard > ---------------------------------------------------- > > Key: JBIDE-19829 > URL: https://issues.jboss.org/browse/JBIDE-19829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png > > > Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth > * Remove server type verify button > * Add v3 auth box (Auto/OAuth/Basic) > * Optional... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19829) Add Oauth support to the Openshift Connection Wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19829: ---------------------------------- I dont know when v1beta1 will be dropped. I'll see if I can find out today. -- Jeff Cantrill Senior Software Engineer, Red Hat Engineering Red Hat Office: 703-748-4420 | 866-546-8970 ext. 8162420 jcantril(a)redhat.com http://www.redhat.com > Add Oauth support to the Openshift Connection Wizard > ---------------------------------------------------- > > Key: JBIDE-19829 > URL: https://issues.jboss.org/browse/JBIDE-19829 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: check-server-type-disabled.png, enlessly-loading.png, ok-enabled.png, Proposed Connection Wizard Chages.png, retrieve-error.png > > > Modify the connection wizard so the v3 server can auto-detect the auth type and support OAuth > * Remove server type verify button > * Add v3 auth box (Auto/OAuth/Basic) > * Optional... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19820: ------------------------------------------ Im importing with validation enabled. numbers before fix: M6 628,575,577,612 (in seconds) = average 598s M6+ batch feature: 843,832,924,877 (in seconds) = average 869s M6 + CDI 794,712 = average 753s after fix M7 632,691,651,638 = 653s M7 + batch feature 792,750,726,800 = 767s M7 + CDI feature 778, 738 = 758s I will measure with validation off. But different machine will have some impact on these numbers too. > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta1 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19786: --------------------------------------------- what is ETA of when staging will have recent update/release ? > Connection wizard: cannot connect to console.stg.openshift.com > -------------------------------------------------------------- > > Key: JBIDE-19786 > URL: https://issues.jboss.org/browse/JBIDE-19786 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: unable-to-connect.png, webconsole.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19463) Cannot connect to remote server in JMX Navigator

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19463: --------------------------------------------- I dont follow why it is a problem when we already talk JMX to the server. If this was for some completely unknown server I grok there is an issue, but why is it not working for servers we *do know* ? And how is this different from former jmx UI code where I could connect to remote servers ? Sorry for the questions but trying to grok what is causing the problem of simply being able to connect ? browsing custom types is a different issue. > Cannot connect to remote server in JMX Navigator > ------------------------------------------------ > > Key: JBIDE-19463 > URL: https://issues.jboss.org/browse/JBIDE-19463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > When you start a remote EAP 6.3 server with management enabled and set up and then want to connect in JMX Navigator, it does not work - double clicking the connection will not do anything and when you right-click, there is no Connect item. > For local servers this works fine - there is a Connect item when you right-click the server in JMX Navigator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19820: --------------------------------------------- so slava says 3 minutes as base and rastislav has 10 minutes as its based ? That is quite some difference. is this machine dependent or because rastislav imported with validation enabled ? > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta1 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19820: --------------------------------------------- rastislav - and how was these numbers *before* the suggested fix ? > Batch feature makes wildfly import way slower > --------------------------------------------- > > Key: JBIDE-19820 > URL: https://issues.jboss.org/browse/JBIDE-19820 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.3.0.Beta1 > > > I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies. > I did a 4 runs with following results: > M6 was able to import WF 628,575,577,612 (in seconds) = average 598s > M6 with batch feature: 843,832,924,877 (in seconds) = average 869s -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-19808: ----------------------------------------- Hey [~nickboldt] So I did create a jenkins at {code}$JENKINS/job/jbosstools-apache-directory-update-site/{code} over the weekend. You may want to take a look at the publishing script component to determine whether it can be improved. Build #12 executed successfully, publishing [this|http://download.jboss.org/jbosstools/updates/requirements/apache-dir...]. This snapshot validates in JBT-IS successfully and works with no issues in Teiid Designer. > Teiid Designer would like to depend on org.apache.directory.studio plugins > -------------------------------------------------------------------------- > > Key: JBIDE-19808 > URL: https://issues.jboss.org/browse/JBIDE-19808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, teiid > Affects Versions: 4.2.3.Final > Reporter: Paul Richardson > Assignee: Barry LaFond > Attachments: build.xml, p2.diff > > > *Reason:* > Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478]. > The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense. > The current working implementation of Teiid with this widget can be found here: > https://github.com/phantomjinx/teiid-designer/tree/ldap-studio > The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits. > *Project page/sources:* > * [directory.apache.org|https://directory.apache.org] > * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] > * [udpate site | http://directory.apache.org/studio/update/2.x/] > *Version:* 2.0.0 > *License and owner:* Apache licence and Foundation > *Original p2 repo:* http://directory.apache.org/studio/update/2.x/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director... > *Include Sources:* Not available from existing update site but may well be in the next release. > *Affected projects:* Teiid Designer > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > * org.apache.directory.api.ldap.model > * org.apache.directory.studio.common.core > * org.apache.directory.studio.common.ui > * org.apache.directory.studio.connection.core > * org.apache.directory.studio.connection.ui > * org.apache.directory.studio.ldapbrowser.common > * org.apache.directory.studio.ldapbrowser.core > * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency > {code} >  > <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> > <repository location="http://directory.apache.org/studio/update/2.x/"/> > <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/> > </location> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19551) Ionic Palette: Empty list item

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19551?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19551. ------------------------------- Verified with JBT 4.3.0-Beta1-v20150528-2309-B9993 > Ionic Palette: Empty list item > ------------------------------ > > Key: JBIDE-19551 > URL: https://issues.jboss.org/browse/JBIDE-19551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: Linux Ubuntu. GTK 3. > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: fixed.png, list.png > > > In New List wizard, if there is more than one item then all items but the first are empty: > !list.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19793) Update HTML5 Ionic palette to the latest ionic 1.0 JS/CSS

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19793?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19793. ------------------------------- Verified with JBT 4.3.0-Beta1-v20150528-2309-B9993 > Update HTML5 Ionic palette to the latest ionic 1.0 JS/CSS > --------------------------------------------------------- > > Key: JBIDE-19793 > URL: https://issues.jboss.org/browse/JBIDE-19793 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > > Ionic 1.0 has been released: > http://blog.ionic.io/announcing-ionic-1-0/ > http://code.ionicframework.com/ > We should add the following links when using Ionic Palette: > {code:html} > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0/js/ionic.bundle.js"></script> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015