August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13809) [Config Editor] Content assist and help pages on the config.xml editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13809?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-13809: --------------------------------- Summary: [Config Editor] Content assist and help pages on the config.xml editor (was: Content assist and help pages on the config.xml editor) > [Config Editor] Content assist and help pages on the config.xml editor > ---------------------------------------------------------------------- > > Key: JBIDE-13809 > URL: https://issues.jboss.org/browse/JBIDE-13809 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Provide conent assist and help pages on valid values of config.xml -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13810) [Config Editor] Format for the generated XML on the config.xml editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13810?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-13810: --------------------------------- Summary: [Config Editor] Format for the generated XML on the config.xml editor (was: Format for the generated XML on the config.xml editor) > [Config Editor] Format for the generated XML on the config.xml editor > --------------------------------------------------------------------- > > Key: JBIDE-13810 > URL: https://issues.jboss.org/browse/JBIDE-13810 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > the formatting of the generated xml when config.xml is used is not good. It should insert nodes on the proper places -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15816) [Config Editor] Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15816?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15816: --------------------------------- Summary: [Config Editor] Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor (was: Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor) > [Config Editor] Add new lines when adding Preferences or Access to cordova config.xml via Cordova Configuration Editor > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15816 > URL: https://issues.jboss.org/browse/JBIDE-15816 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Environment: JBT 4.1.1 Beta1a Beta1-v20131026-0906-B486 > Reporter: Vlado Pakan > Priority: Minor > Fix For: 4.2.x > > > 1. Create new Hybrid Mobile project > 2. Open config.xml file in Cordova Configuration Editor > 3. Add Preference or Access > ASSERT: Preference or Access is added to config.xml source > It would be nice if added Preferences or Access is added to new line in config.xml instead of adding it directly at the end of previously added item -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15769) [Config Editor] Only Android parameters added to parameters table

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15769?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15769: --------------------------------- Summary: [Config Editor] Only Android parameters added to parameters table (was: Only Android parameters added to parameters table) > [Config Editor] Only Android parameters added to parameters table > ----------------------------------------------------------------- > > Key: JBIDE-15769 > URL: https://issues.jboss.org/browse/JBIDE-15769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In Cordova Configuration Editor, Platform Properties mode: > 1. Click Add for first features table (opens Cordova Plugin Discovery window) > 2. Select check box for cordova item (e.g., org.apache.cordova.camera) > 3. Click Next > 4. Click Finish > Outcomes: > * "Camera" is added to feature table > * "android-package" is added to parameter table > * Following is added to file in config.xml mode > {noformat} > <feature name="Camera"> > <param name="android-package" value="org.apache.cordova.camera.CameraLauncher" /> > <param name="ios-package" value="CDVCamera" /> > </feature> > {noformat} > So looks like only the Android parameter is being added to the parameter table. Should the iOS parameter be automatically added to the parameter table too? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18051) [Config Editor] Could not add plugin from platform properties

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18051?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18051: --------------------------------- Summary: [Config Editor] Could not add plugin from platform properties (was: Aerogear: Could not add plugin from platform properties) > [Config Editor] Could not add plugin from platform properties > ------------------------------------------------------------- > > Key: JBIDE-18051 > URL: https://issues.jboss.org/browse/JBIDE-18051 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta3 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17865) [Config Editor] Can't open config.xml with Cordova Configuration Editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17865?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-17865: --------------------------------- Summary: [Config Editor] Can't open config.xml with Cordova Configuration Editor (was: Can't open config.xml with Cordova Configuration Editor) > [Config Editor] Can't open config.xml with Cordova Configuration Editor > ----------------------------------------------------------------------- > > Key: JBIDE-17865 > URL: https://issues.jboss.org/browse/JBIDE-17865 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR1 > Reporter: Alexey Kazakov > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.2.x > > > 1. Install ionic - http://ionicframework.com/docs/guide/installation.html > 2. Create a new project: {code}ionic start todo blank{code} > 3. Import the project as a plain eclipse project > 4. Open config.xml with Cordova Configuration Editor > 5. FAILURE: > {code} > java.lang.NullPointerException > at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.getConfigXml(WidgetModel.java:222) > at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.<init>(WidgetModel.java:83) > at org.jboss.tools.aerogear.hybrid.core.config.WidgetModel.getModel(WidgetModel.java:94) > at org.jboss.tools.aerogear.hybrid.ui.config.internal.ConfigEditor.getWidget(ConfigEditor.java:109) > at org.jboss.tools.aerogear.hybrid.ui.config.internal.ConfigEditor.setTitle(ConfigEditor.java:54) > at org.jboss.tools.aerogear.hybrid.ui.config.internal.ConfigEditor.init(ConfigEditor.java:49) > at org.eclipse.ui.internal.EditorReference.initialize(EditorReference.java:390) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:304) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869) > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:983) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:662) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:766) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:737) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:731) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:715) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1251) > at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:66) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4622) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:218) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:488) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:454) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:692) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:385) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1126) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3182) > at org.eclipse.ui.internal.WorkbenchPage.access$23(WorkbenchPage.java:3104) > at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3086) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3081) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3045) > at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:338) > at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:180) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17461) Black Screen on iOS simulator when rerun Cordova project

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17461?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-17461: --------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR1) > Black Screen on iOS simulator when rerun Cordova project > -------------------------------------------------------- > > Key: JBIDE-17461 > URL: https://issues.jboss.org/browse/JBIDE-17461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 > Reporter: Vlado Pakan > Assignee: Gorkem Ercan > Fix For: 4.2.0.Final > > > 1. Create and Run Hybrid Mobile project on iOS simulator > ASSERT: App is properly displayed in iOS simulator > 2. Run it again on iOS simulator > ERROR: Only black screen is displayed in iOS simulator -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-302) Fuse: Update JMXNavigator Test

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-302?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík resolved JBTIS-302. -------------------------------- Resolution: Done > Fuse: Update JMXNavigator Test > ------------------------------ > > Key: JBTIS-302 > URL: https://issues.jboss.org/browse/JBTIS-302 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > Update JMXNavigatorTest to check JMX nodes of running Fuse Server with deployed project -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18136: -------------------------------------- This is very likely a problem with the config.xml file on your project.. Can you check if it exist and possibly post a copy of it? > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16586) Move Engine switching from BrowserSim preferences to Eclipse preferences

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16586?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16586: --------------------------------------------- Okey! sounds good. > Move Engine switching from BrowserSim preferences to Eclipse preferences > ------------------------------------------------------------------------ > > Key: JBIDE-16586 > URL: https://issues.jboss.org/browse/JBIDE-16586 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.2.0.Alpha2 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.CR1 > > > Add possibility to select BrowserSim rendering engine in Eclipse preferences. > Right now it's possible only within BrowserSim preferences. > Default engine is WebKit not javafx and therefore user has to have installed Safari and 32bit java on 64 bit MS Windows to be able to run BrowserSim and set engine to javafx. > It would be more user friendly to set engine within BrowserSim/CordovaSim Eclipse preferences section. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 August 2014