April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19072. ------------------------------ Resolution: Done Had to reopen to mark the Epic as "Done". Closing again. > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: 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...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3246) As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3246?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3246: ----------------------------- Epic Name: Usage analytics/Error feedback (was: Usage analytis/Error feedback) > As part of JBoss Tools team I would like to gather usage, feedback, download statistics to get better insight into what are our users do/struggle with so I can fix issues and implement features that matters and help the user > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3246 > URL: https://issues.jboss.org/browse/JBDS-3246 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 9.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19072: ------------------------------- Epic Status: Done > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: 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...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17265) Build should be easy to use on jenkins and locally with predictable results

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17265?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17265. ------------------------------ Resolution: Done Closed. Please use JBIDE-19730 for future Epic grouping. > Build should be easy to use on jenkins and locally with predictable results > --------------------------------------------------------------------------- > > Key: JBIDE-17265 > URL: https://issues.jboss.org/browse/JBIDE-17265 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19731) Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19731: ------------------------------------ Summary: Selecting "remove" before a hybrid mobile engine is created logs exception - no feeback is provided to users in the UI Key: JBIDE-19731 URL: https://issues.jboss.org/browse/JBIDE-19731 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Priority: Minor To recreate: * With no hybrid mobile engines defined * Preferences->Hybrid Mobile-> Engines * Click on "remove" and the exception is logged - no feedback is provided to the user in the UI !ENTRY org.eclipse.ui 4 0 2015-04-28 14:30:25.700 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.ClassCastException: org.eclipse.thym.core.extensions.PlatformSupport cannot be cast to org.eclipse.thym.core.engine.HybridMobileEngine at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.handleRemoveEngine(AvailableCordovaEnginesSection.java:606) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.access$4(AvailableCordovaEnginesSection.java:598) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:378) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17265) Build should be easy to use on jenkins and locally with predictable results

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17265?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17265: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > Build should be easy to use on jenkins and locally with predictable results > --------------------------------------------------------------------------- > > Key: JBIDE-17265 > URL: https://issues.jboss.org/browse/JBIDE-17265 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19727: -------------------------------------- Alternate steps to recreate: * With no Mobile Engine configured: ** Preferences->Hybrid Mobile->Engines ** Select Android - the error dialog is displayed and the exception is logged > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19072) Improve plugin version auditing & how we build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19072?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19072. ------------------------------ Resolution: Done Closing. Unresolved issues are now under one of two epics: JBIDE-19729 - Version Auditing JBIDE-19730 - Build Improvement > Improve plugin version auditing & how we build > ---------------------------------------------- > > Key: JBIDE-19072 > URL: https://issues.jboss.org/browse/JBIDE-19072 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta1 > > > For JBIDE 4.3.0.Alpha1: 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...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17103: ------------------------------------- Again, the patch as submitted should be 100% source-compatible, for both callers AND implementers... so as long as all teams are compiling against the version they'll be using, there shouldn't be a problem. The only problem here would be if IS guys compile against our luna version but then run against our Mars plugins. But yes, it should be raised to them for awareness. > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19726: --------------------------------- Attachment: IMG_2768.MOV An error dialog is displayed, but it is only visible for a fraction of a second. See the attached cell phone movie - I was working on RHEL and did not have a good screencast tool. > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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