April 2015 - jbosstools-issues - Jboss List Archives

[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)

[ https://issues.jboss.org/browse/JBIDE-19731?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19731: ------------------------------------ Assignee: Gorkem Ercan > 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 > Assignee: Gorkem Ercan > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19733: ------------------------------------ Assignee: Ilya Buziuk > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19735) Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)"

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19735: ------------------------------------ Assignee: Fred Bricon > Creating a AngularJS project from scratch fails with an error of: java.lang.IllegalArgumentException: invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19735 > URL: https://issues.jboss.org/browse/JBIDE-19735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Attachments: jbosstools-diagnostics-20150428160436.zip > > > To recreate: > * Create from scratch a new AngularJS with Forge project. > * Have the project creation install AngularJS Eclipse > Observe this error reported in a dialog in the UI: > An error has occurred. See error log for more details. > invalid range "[0.4)": invalid version "0.4)": non-numeric "4)" > The full .log is in the attached diagnostic file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19744: ------------------------------- Fix Version/s: 4.2.3.Final > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19744?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19744: ---------------------------------- Assignee: Nick Boldt > jbosstools-build has both 4.2.x and 4.2.X and with different content > -------------------------------------------------------------------- > > Key: JBIDE-19744 > URL: https://issues.jboss.org/browse/JBIDE-19744 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.3.Final > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.3.Final > > > Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. > The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... > indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) > We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19741 at 4/30/15 11:20 AM: -------------------------------------------------------------- Reason I suggest we de-dupe here is that the jbosstools-src.zip [1] is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) [1] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. was (Author: nickboldt): Reason I suggest we de-dupe here is that the jbosstools-src.zip is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19741: ------------------------------------ Reason I suggest we de-dupe here is that the jbosstools-src.zip is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19745) rename jbosstools-build-ci 4.3.x to jbosstools-4.3.x

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19745: ------------------------------------------- Summary: rename jbosstools-build-ci 4.3.x to jbosstools-4.3.x Key: JBIDE-19745 URL: https://issues.jboss.org/browse/JBIDE-19745 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Rydahl Andersen 4.3.x is not following the convention all other repos has. lets get it renamed to jbosstools-4.3.x to avoid confusion and document in readme on master that its a legacy branch only kept there for old builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-640: ------------------------------------- Summary: Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS Key: TOOLSDOC-640 URL: https://issues.jboss.org/browse/TOOLSDOC-640 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Components: General documentation issues Affects Versions: 4.3.0.Final Reporter: Len DiMaggio Assignee: Misha Ali Fix For: 4.3.0.Final This is related to: https://issues.jboss.org/browse/JBIDE-19716 The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 6 months

1
0
0 / 0

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

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19036?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19036. ------------------------------ > 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: Nick Boldt > Priority: Minor > Fix For: 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.15#6346)

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