June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19891) Replace OK/Cancel button with close

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19891?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19891: ---------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/628) > Replace OK/Cancel button with close > ----------------------------------- > > Key: JBIDE-19891 > URL: https://issues.jboss.org/browse/JBIDE-19891 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: ok-enabled.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-19891) Replace OK/Cancel button with close

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19891?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19891: ---------------------------------- Attachment: (was: enlessly-loading.png) > Replace OK/Cancel button with close > ----------------------------------- > > Key: JBIDE-19891 > URL: https://issues.jboss.org/browse/JBIDE-19891 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: ok-enabled.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-19891) Replace OK/Cancel button with close

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19891?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19891: ---------------------------------- Attachment: (was: retrieve-error.png) > Replace OK/Cancel button with close > ----------------------------------- > > Key: JBIDE-19891 > URL: https://issues.jboss.org/browse/JBIDE-19891 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Attachments: ok-enabled.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-19795) Bower support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19795: ------------------------------------- [~maxandersen], on Mac Os I have faced the following issue with running bower from eclipse {code} env: node: No such file or directory {code} Basically, everything works fine when eclipse is running from console. Breakage happens when eclipse is run from desktop. Also, on both windows and ubuntu everything worked just fine even for desktop runs. Any ideas how this can be handled ? > Bower support > ------------- > > Key: JBIDE-19795 > URL: https://issues.jboss.org/browse/JBIDE-19795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Final > > > Need to have initial [Bower|http://bower.io/] tools support: > *The gist* > Bower tooling should initially support several bower API commands : > |Command||Description| > | *bower init* |creates a *bower.json* file| > |*bower install <package>*|installs packages to *bower_components* folder| > |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory| > |*bower update* |updates installed packages to their newest version according to *bower.json*| > Basically, the main idea of the implementation is the following: > Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration* > Native bower tools must be preinstalled > *The main questions & proposals:* > 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.) > 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature? > 3. Implementation details: > - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) > - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19891) Replace OK/Cancel button with close

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19891: ------------------------------------- Summary: Replace OK/Cancel button with close Key: JBIDE-19891 URL: https://issues.jboss.org/browse/JBIDE-19891 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-19853) GTK3 (only): Erroneous labels in application wizard tree

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19853: ------------------------------------------ [~snjeza] [~maxandersen] looks like we have a problem with this issue since it looks as if [~snjeza] fix wont make it to Mars final. I chatted with Alexander Kurtakov and he didnt know of a workaround. {quote} (03:59:43 PM) adietish: akurtakov: any chance that https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 makes it to mars? it's pretty critical to JBoss Tools OpenShift tooling (04:24:36 PM) akurtakov: adietish: Mars is done deal now (04:25:49 PM) akurtakov: even more critical fixes were postponed for SR1 (04:26:33 PM) akurtakov: adietish: e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=457476 (04:28:15 PM) akurtakov: adietish: to get a change now is kind of impossible (04:29:11 PM) akurtakov: adietish: any change will need 2 committers + 2 component leads to test/approve it (04:29:31 PM) akurtakov: and no component lead to veto it (which I haven't seen happening) (04:29:57 PM) akurtakov: https://www.eclipse.org/eclipse/development/plans/freeze_plan_4_5.php#Fix... (04:37:11 PM) akurtakov: adietish: sorry, I wish I had the power to push stuff now but the freeze plan is really hard (04:37:25 PM) akurtakov: I tried to soften it last year with no success (04:37:37 PM) adietish: akurtakov: fully understand. Now I try to figure out what our plan B would then look like (04:41:59 PM) adietish: akurtakov: is there any way we could work around it? (04:42:57 PM) akurtakov: I can't think of one {quote} This is critical since v2 application wizard wont work properly with GTK3 then. Any idea? > GTK3 (only): Erroneous labels in application wizard tree > -------------------------------------------------------- > > Key: JBIDE-19853 > URL: https://issues.jboss.org/browse/JBIDE-19853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Priority: Blocker > Labels: application_wizard > Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png > > > When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded. > When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way: > !gtk2-new-app-wizard-1.png! > unfolding the "Basic Cartridges" produces the following: > !gtk2-new-app-wizard-2.png! > Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows: > !gtk3-new-app-wizard-1.png! > ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same: > !gtk3-new-app-wizard-2.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19853: ---------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > GTK3 (only): Erroneous labels in application wizard tree > -------------------------------------------------------- > > Key: JBIDE-19853 > URL: https://issues.jboss.org/browse/JBIDE-19853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: application_wizard > Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png > > > When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded. > When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way: > !gtk2-new-app-wizard-1.png! > unfolding the "Basic Cartridges" produces the following: > !gtk2-new-app-wizard-2.png! > Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows: > !gtk3-new-app-wizard-1.png! > ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same: > !gtk3-new-app-wizard-2.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19796) Forge editor changes are not applied after changing font preferences

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19796?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-19796: ------------------------------------ Description: 1. Start the Forge console 2. Go to Eclipse Settings -> General -> Appearance -> Colors and Fonts 3. Choose the _Forge Console Font_ under the Forge category 4. Apply changes 5. Forge console editor should have been changed to match your settings, but it does not. was: 1. Start the Forge console 2. Go to Eclipse Settings -> General -> Appearance -> Colors and Fonts 3. Choose the _Forge Console Font_ under the Forge category 4. Apply changes 5. Forge console editor should have changed to match your settings, but it does not. > Forge editor changes are not applied after changing font preferences > -------------------------------------------------------------------- > > Key: JBIDE-19796 > URL: https://issues.jboss.org/browse/JBIDE-19796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.3.x > > > 1. Start the Forge console > 2. Go to Eclipse Settings -> General -> Appearance -> Colors and Fonts > 3. Choose the _Forge Console Font_ under the Forge category > 4. Apply changes > 5. Forge console editor should have been changed to match your settings, but it does not. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19808: ------------------------------------ "I have altered the job. Pray I don't alter it any further." - "This job's getting simpler all the time." -- https://www.youtube.com/watch?v=WpE_xMRiCLE Using the new rsync.sh script you can skip much of the steps you did and simply call the script with a local source (-s) and remote target (-t) path. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-apache-di... --> http://download.jboss.org/jbosstools/updates/requirements/apache-director... We've actually got a way to wrap this script into a mojo so you can simply call `mvn deploy` in your root pom, should you want to use it for other Integration Stack projects. Details in this job, for example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson//job/jbosstools-server_m... > 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-19786) Connection wizard: cannot connect to console.stg.openshift.com

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-19786. ----------------------------------- Resolution: Done [~adietish] [~maxandersen] Added user kind to to openshift-restclient-java so we could complete the oauth connection via the wizard > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015