January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19036) Cleanup Central TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19036?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19036: ------------------------------- Git Pull Request: (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/258) > Cleanup Central TP > ------------------ > > Key: JBIDE-19036 > URL: https://issues.jboss.org/browse/JBIDE-19036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: discovery > Affects Versions: 4.2.1.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > It seems that the jbtcentral targetplatform contains some features that are already included in JBT and JBDS. Namely: > * org.jboss.tools.forge.feature.feature.group > * org.jboss.tools.forge.m2e.feature.feature.group > So those features should probably trimmed out of the target platform. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19099) When installing JBT 422 into RH DevToolset 3, downloading an EAP runtime fails with exception

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19099: ------------------------------------ Summary: When installing JBT 422 into RH DevToolset 3, downloading an EAP runtime fails with exception Key: JBIDE-19099 URL: https://issues.jboss.org/browse/JBIDE-19099 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.2.2.Final Reporter: Len DiMaggio On RHEL 6.6, with OpenJDK 1.7 * Install devtoolset-3 * Install JBoss Tools 4.2.2 into devtoolset-3 * Attempt to instal web kitchensink quickstart * Exception raised in trying to download/install EAP runtime: Unhandled event loop exception No more handles (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: no swt-xulrunner-gtk-4427 in java.library.path no swt-xulrunner-gtk in java.library.path Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4427.so Can't load library: /home/jbossqa/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19098) When installing JBT 4.2.2 into RH Dev Tool Set 3, welcome screen is then shown as white background

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19098: ------------------------------------ Summary: When installing JBT 4.2.2 into RH Dev Tool Set 3, welcome screen is then shown as white background Key: JBIDE-19098 URL: https://issues.jboss.org/browse/JBIDE-19098 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.2.2.Final Reporter: Len DiMaggio On RHEL 6.6, with OpenJDK 1.7 * Install devtoolset-3 * Install JBoss Tools 4.2.2 into devtoolset-3 * Welcome screen is then shown as all white backgound (see attached screenshot) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3331) Installation of JBDS/JBoss Tools into Red Hat Developer Toolset

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3331?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3331: ------------------------------------ Just to recap: Test 1 - On RHEL 6.6, with OpenJDK 1.7 * Install devtoolset-3 * Install JBoss Tools 4.2.2 into devtoolset-3 * The issues listed above related to the welcome screen and the kitchensink web quickstart were seen Test 2 - On RHEL 7.0, with OpenJDK 1.7 * Install devtoolset-3 * Install JBoss Tools 4.2.2 into devtoolset-3 * The issues listed above related to the welcome screen and the kitchensink web quickstart were NOT seen Test 3 - On RHEL 6.6, with OpenJDK 1.7 * Install JBDS 8.0, upgrade to 8.0.2 * The issues listed above related to the welcome screen and the kitchensink web quickstart were NOT seen > Installation of JBDS/JBoss Tools into Red Hat Developer Toolset > --------------------------------------------------------------- > > Key: JBDS-3331 > URL: https://issues.jboss.org/browse/JBDS-3331 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: updatesite > Environment: RHEL Desktop > Reporter: Burr Sutter > Assignee: Len DiMaggio > Attachments: Download_EAP.png, log, Non_reproducible_error.png, RHEL66_jbosstools-diagnostics-20150127000831.zip, RH_Dev_Toolset.png, Welcome.png > > > As a RHEL Desktop user and application developer, I wish to install the JBDS/JBoss Tools features/plug-ins into my previously installed version of DTS - Developer Toolset > https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/ > Help - Install New Software -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19097) performOk() and performCancel() method in TabbedPreferencesPage should return true only if all its tabs return true

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19097: -------------------------------------- Summary: performOk() and performCancel() method in TabbedPreferencesPage should return true only if all its tabs return true Key: JBIDE-19097 URL: https://issues.jboss.org/browse/JBIDE-19097 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Alpha1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Priority: Minor Fix For: 4.3.0.Alpha1 org.jboss.tools.common.model.ui.preferences.TabbedPreferencesPage.performCancel() and performOk() always return true now. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Rafael Benevides edited comment on JBDS-3199 at 1/27/15 1:03 PM: ----------------------------------------------------------------- It looks like that you didn't include the cheatsheet headers as I need to do in this fix: https://github.com/wildfly/wildfly-archetypes/commit/d0e920d5f96cdfb1fe6a... I can do that now cause I'm available to work on JDF-800 at this moment, but I don't want to colide with you work. was (Author: rafabene): It looks like that you didn't include the as I need to do in this fix: https://github.com/wildfly/wildfly-archetypes/commit/d0e920d5f96cdfb1fe6a... I can do that now cause I'm available to work on JDF-800 at this moment, but I don't want to colide with you work. > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on JBDS-3199: ---------------------------------------- It looks like that you didn't include the as I need to do in this fix: https://github.com/wildfly/wildfly-archetypes/commit/d0e920d5f96cdfb1fe6a... I can do that now cause I'm available to work on JDF-800 at this moment, but I don't want to colide with you work. > Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3199 > URL: https://issues.jboss.org/browse/JBDS-3199 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, upstream > Affects Versions: 8.0.0.GA > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > These "kitchensink" strings are retained: > grep -ir kitchen * > main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source> > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS" > main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true" > test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS" > test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

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: ------------------------------------- Description: !screenshot-openshift-signin.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. was: !screenshot-openshift-signin.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 has to provide then are different: v2 connections currently use username/password (and will most likely also allow x509, kerberos) while v3 connections will most likely require OAuth settings. > 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 > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: screenshot-openshift-signin.png > > > !screenshot-openshift-signin.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, 2 months

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: ------------------------------------- Description: !screenshot-openshift-signin.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 has to provide then are different: v2 connections currently use username/password (and will most likely also allow x509, kerberos) while v3 connections will most likely require OAuth settings. was: 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 has to provide then are different: v2 connections currently use username/password (and will most likely also allow x509, kerberos) while v3 connections will most likely require OAuth settings. > 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 > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: screenshot-openshift-signin.png > > > !screenshot-openshift-signin.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 has to provide then are different: v2 connections currently use username/password (and will most likely also allow x509, kerberos) while v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

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: ------------------------------------- Attachment: screenshot-openshift-signin.png > 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 > Labels: connection_wizard > Fix For: 4.3.0.Alpha1 > > Attachments: screenshot-openshift-signin.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 has to provide then are different: v2 connections currently use username/password (and will most likely also allow x509, kerberos) while v3 connections will most likely require OAuth settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 2015