January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19085) tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19085?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19085: ---------------------------------- Fix Version/s: 4.3.0.Alpha1 > tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19085 > URL: https://issues.jboss.org/browse/JBIDE-19085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > from grdryn on irc: > "Hi folks, tools.jboss.org/downloads/ shows latest devstudio as 8.0.2.GA, but jboss.org/products/devstudio/download/ still lists 8.0.0.GA > ^Just FYI...I'm not sure if that's normal, or if the latter should be updated" > and yes, we should look at making it possible to mark an install as "updatesite" only or somehow refer to the "nearest" installer. > i.e. maybe something like: > {code} > updatesite_only: true > {code} > and then just refer to old installer link in the download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19085) tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19085?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19085: ------------------------------------- Assignee: Xavier Coulon > tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19085 > URL: https://issues.jboss.org/browse/JBIDE-19085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > > from grdryn on irc: > "Hi folks, tools.jboss.org/downloads/ shows latest devstudio as 8.0.2.GA, but jboss.org/products/devstudio/download/ still lists 8.0.0.GA > ^Just FYI...I'm not sure if that's normal, or if the latter should be updated" > and yes, we should look at making it possible to mark an install as "updatesite" only or somehow refer to the "nearest" installer. > i.e. maybe something like: > {code} > updatesite_only: true > {code} > and then just refer to old installer link in the download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19076) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19076?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19076: ------------------------------------------ merged to upstream/master > For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-19076 > URL: https://issues.jboss.org/browse/JBIDE-19076 > 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.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [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. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [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.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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3199: ----------------------------------- Ok I will. Please wait for my +1 > 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-19076) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19076?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19076: ------------------------------------------ bumped to 2.6.100 and ran the build: {quote} [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jbosstools-openshift .............................. SUCCESS [0.494s] [INFO] openshift.plugins ................................. SUCCESS [0.008s] [INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [3.233s] [INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.220s] [INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [2.240s] [INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.588s] [INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [4.136s] [INFO] openshift.tests ................................... SUCCESS [0.006s] [INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [26.412s] [INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [28.348s] [INFO] openshift.features ................................ SUCCESS [0.009s] [INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.205s] [INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.276s] [INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.127s] [INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.138s] [INFO] openshift.site .................................... SUCCESS [27.417s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18:07.579s [INFO] Finished at: Tue Jan 27 14:56:48 CET 2015 [INFO] Final Memory: 101M/1522M [INFO] ------------------------------------------------------------------------ {quote} > For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift] > ------------------------------------------------------------------------------------- > > Key: JBIDE-19076 > URL: https://issues.jboss.org/browse/JBIDE-19076 > 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.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [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. > Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [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.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19085) tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19085?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19085: -------------------------------- Component/s: website > tools.jboss.org devstudio downloads does not mention it is update site content only and to use 8.0.0 installer > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19085 > URL: https://issues.jboss.org/browse/JBIDE-19085 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Reporter: Max Rydahl Andersen > > from grdryn on irc: > "Hi folks, tools.jboss.org/downloads/ shows latest devstudio as 8.0.2.GA, but jboss.org/products/devstudio/download/ still lists 8.0.0.GA > ^Just FYI...I'm not sure if that's normal, or if the latter should be updated" > and yes, we should look at making it possible to mark an install as "updatesite" only or somehow refer to the "nearest" installer. > i.e. maybe something like: > {code} > updatesite_only: true > {code} > and then just refer to old installer link in the download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19091) Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19091?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19091: -------------------------------- Component/s: browsersim > Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-19091 > URL: https://issues.jboss.org/browse/JBIDE-19091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.2.2.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > > Both SWT and JavaFX are affected. > Stack trace for javaFx web engine: > {code} > Exception in thread "JavaFX Application Thread" org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.widgets.Widget.error(Widget.java:476) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348) > at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1075) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.inject(RippleInjector.java:68) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector.access$1(RippleInjector.java:55) > at org.jboss.tools.vpe.cordovasim.events.RippleInjector$1.run(RippleInjector.java:44) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:301) > at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:298) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.application.PlatformImpl$6.run(PlatformImpl.java:298) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2759) Document Maven Tools functionality in User Guide

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2759?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2759: ------------------------------------------- I think the basics usecases are: * Create a Maven project from scratch * Import an existing Maven Project And most likely importing is going to be what *majority* of users are doing. The content of this depends if we want to cover explaining how maven itself works or just focus on what is important in context of eclipse. My vote is mainly for focusing what is importing in context of eclipse and thus explain how maven integration in eclipse works - what is good and what is bad about it. I would explain how you can edit the pom.xml to add/change a dependency and when that is done explain the need to run Update project configuration. Then I would cover how to setup using an additional repository in settings.xml like maven.repository.redhat.com either manually or by using our maven repository dialog. Advanced how to: * cover how to enable autdownload of source and javadoc * usage of maven source lookup container (it somewhat automatces the autodownload) * explain maven lifecycles and how it can result in warnings/errors you as user don't really care or want to care about - in here explain how jboss tools and eclipse provides some autoconfiguration based on what plugins are useed and document the maven properties you can use to turn on/off this auto config such as enable hibernate, annotation processors, war projects etc. > Document Maven Tools functionality in User Guide > ------------------------------------------------ > > Key: JBDS-2759 > URL: https://issues.jboss.org/browse/JBDS-2759 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, requirements > Reporter: Michelle Murray > Assignee: Michelle Murray > Labels: JBDS80_Approved_Scope > Fix For: 8.x > > > Add a chapter to the JBDS User Guide on Maven Tools. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-385) Browse button in ESB project creation wizard is too narrow

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-385?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-385: ----------------------------------------- [~apodhrad] Can you try something for me? Create a new Static Web Project - New->Other->Web->Static Web Project- and let me know if you see the same thing. I don't create those controls - they come from underlying frameworks in Eclipse, so I'm wondering if something upstream has been corrupted somehow? I'm not seeing it with plane jane Luna plus the JBTIS target platform but will try with JBDS 8.0.2.GA + JBDS-IS 8.0.0.CR1. > Browse button in ESB project creation wizard is too narrow > ---------------------------------------------------------- > > Key: JBTIS-385 > URL: https://issues.jboss.org/browse/JBTIS-385 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: ESB > Affects Versions: 8.0.0.CR1 > Environment: JBDS 8.0.2.GA + JBDS-IS 8.0.0.CR1 (contains ESB Tools 1.5.520.Final-v20141209-1859-B53) > Reporter: Andrej Podhradsky > Assignee: Brian Fitzpatrick > Attachments: esb_wizard.png > > > Browse button in ESB project creation wizard is too narrow, see the attachment. Note that the button works fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19042) Cannot login via Openshift Explorer on Openshift "Can not verify User"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19042?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19042. -------------------------------------- Resolution: Won't Fix resolving with WONT_FIX since we dont have the manpower to fix outdated versions, we only maintain current versions. > Cannot login via Openshift Explorer on Openshift "Can not verify User" > ---------------------------------------------------------------------- > > Key: JBIDE-19042 > URL: https://issues.jboss.org/browse/JBIDE-19042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.x > Environment: Win7, jdk7, Openshift Online > Reporter: Stylianos Koussouris > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.2.Final > > Attachments: CannotVerifyUser.JPG > > > Trying to connect via Openshift explorer to Openshift Online, the credentials are correct and working from the Web UI, I receive > Unknown error, can not verify user > and in the log > !ENTRY org.jboss.tools.openshift.express.ui 4 4 2015-01-15 15:01:37.848 > !MESSAGE > !STACK 0 > java.lang.NullPointerException > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:113) > at com.openshift.internal.client.RestService.request(RestService.java:151) > at com.openshift.internal.client.RestService.request(RestService.java:107) > at com.openshift.internal.client.RestService.request(RestService.java:100) > at com.openshift.internal.client.RestService.request(RestService.java:81) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:252) > at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Similar Issue reported: https://forums.openshift.com/unknown-error-can-not-verify-user -- 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