April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19708: -------------------------------- Fix Version/s: 4.3.0.Beta1 > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- 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 Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19731?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-19731. ---------------------------------- Resolution: Duplicate Issue > 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-19736) Update template list page to get 'openshift' templates and group accordingly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19736?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19736: ------------------------------------- Assignee: Jeff Cantrill > Update template list page to get 'openshift' templates and group accordingly > ---------------------------------------------------------------------------- > > Key: JBIDE-19736 > URL: https://issues.jboss.org/browse/JBIDE-19736 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > > When creating a template, a user should be able to choose from their project templates and those that are part of the configured (openshift) namespace. Update The template list page get templates from openshift namespace and to group templates under an appropriate folder (project or openshift) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19737) Add template info page after template list in create from app flow

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19737: ------------------------------------- Summary: Add template info page after template list in create from app flow Key: JBIDE-19737 URL: https://issues.jboss.org/browse/JBIDE-19737 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Add a template info page that identifies key aspects of a template that a user has choosen so they can ensure they want to continue -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19736) Update template list page to get 'openshift' templates and group accordingly

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19736: ------------------------------------- Summary: Update template list page to get 'openshift' templates and group accordingly Key: JBIDE-19736 URL: https://issues.jboss.org/browse/JBIDE-19736 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill When creating a template, a user should be able to choose from their project templates and those that are part of the configured (openshift) namespace. Update The template list page get templates from openshift namespace and to group templates under an appropriate folder (project or openshift) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19478) Application wizard: Add template filtering by tag

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19478?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-19478. ----------------------------------- Resolution: Done > Application wizard: Add template filtering by tag > ------------------------------------------------- > > Key: JBIDE-19478 > URL: https://issues.jboss.org/browse/JBIDE-19478 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Labels: application_wizard > 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-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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19735?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19735: ------------------------------------- Can you check if it works in JBDS? (I tried that and it worked for me). There might be an issue with the discovery catalog > 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 > 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, 11 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 updated JBIDE-19735: --------------------------------- Attachment: jbosstools-diagnostics-20150428160436.zip > 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 > 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, 11 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)

Len DiMaggio created JBIDE-19735: ------------------------------------ Summary: 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 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-431?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-431: ---------------------------------- Updated JBTIS TP 4.2.3.CR1a repo and nexus. [~phantomjinx] - please try rebuilding teiid designer w/ jbtis tp version 4.2.3.CR1a . Also - Barry gave me a teiid des to use for the first CR1 capture for QE to test: 9.0.2.Beta1 . Should I hold off giving this to QE (waiting for an update with this TP) or should I go ahead with 9.0.2.Beta1? https://github.com/jbosstools/jbosstools-integration-stack/commit/73d3c92... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.3.CR1a/ > Designer requires a new luna IS-TP complete with new version of LOCUS > --------------------------------------------------------------------- > > Key: JBTIS-431 > URL: https://issues.jboss.org/browse/JBTIS-431 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.0.Final-TP > Reporter: Paul Richardson > > https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. > Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- 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