July 2014 - jbosstools-issues - Jboss List Archives

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17865?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17865: ---------------------------------------- Yes, it's not a hybrid project (there is no Cordova nature) > 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 > > 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.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17909) Include Thym 0.1.0 snapshot into jbosstools TP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17909?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-17909: -------------------------------------- [~mickael_istria] it seems to work with the PRs.. Once TP is in place I can merge. > Include Thym 0.1.0 snapshot into jbosstools TP > ---------------------------------------------- > > Key: JBIDE-17909 > URL: https://issues.jboss.org/browse/JBIDE-17909 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Include thym 0.1.0 snapshot release into JBossTools TP > Reason: plugins moved to Eclipse > License and owner: EPL, Eclipse.org > Original repo: http://download.eclipse.org/thym/snapshots/ > JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNA... > Sources: THyM does not include source bundles/features yet (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=440753 ) > Affected projects: jbosstools-aerogear > Include in JBDS: Yes > Type of dependency: distribution > List of bundles added/removed: > /org.eclipse.thym > /org.eclipse.thym.android.core > /org.eclipse.thym.android.ui > /org.eclipse.thym.core > /org.eclipse.thym.ios.core > /org.eclipse.thym.ios.ui > /org.eclipse.thym.ui > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13986) Hot deployment doesn't work with JPP 6

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13986?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-13986: ---------------------------------- Component/s: upstream > Hot deployment doesn't work with JPP 6 > -------------------------------------- > > Key: JBIDE-13986 > URL: https://issues.jboss.org/browse/JBIDE-13986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein, upstream > Affects Versions: 4.0.1.Final, 4.1.0.Alpha2 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.x, 4.2.x > > > When you create portlet while JPP is running nothing will happen. Portlet is not deployed until JPP is restarted. > Tested were _JBoss Core Portlet_ and _JBoss JSF Portlet_ on JPP 6.0.0.GA -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Karl Pietrzak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Karl Pietrzak resolved JBIDE-17960. ----------------------------------- Resolution: Done Looks like it was fixed for Mac OS X too. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Karl Pietrzak > Priority: Minor > Fix For: 4.2.0.CR1 > > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17895: ---------------------------------------- [~rob.stryker] I'm assigning this to you. Your task will be to check that we get the right content and behaviour when we move to SR1. If it happens to be a blocker for ongoing work, we can still consume the patch build, but so far, it seems acceptable to wait. > Consume wtp patch build (update to Luna SR1) > -------------------------------------------- > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Optional > Fix For: 4.2.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17895: ----------------------------------- Priority: Optional (was: Major) > Consume wtp patch build (update to Luna SR1) > -------------------------------------------- > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.0.CR1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17895: ----------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR1) > Consume wtp patch build (update to Luna SR1) > -------------------------------------------- > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.2.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17895: ----------------------------------- Assignee: Rob Stryker (was: Mickael Istria) > Consume wtp patch build (update to Luna SR1) > -------------------------------------------- > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Optional > Fix For: 4.2.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17895) Consume wtp patch build (update to Luna SR1)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17895?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17895: ---------------------------------------- I don't think it's worth updating the TP right now. Luna SR1 will be released on September 26th, 4 days before we release our Final target-platforms. I'm in favor of just waiting for Luna SR1 release. > Consume wtp patch build (update to Luna SR1) > -------------------------------------------- > > Key: JBIDE-17895 > URL: https://issues.jboss.org/browse/JBIDE-17895 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, server, target-platform, upstream > Affects Versions: 4.2.0.Beta3 > Reporter: Rob Stryker > Assignee: Mickael Istria > Fix For: 4.2.0.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351 > The patch build currently lives at http://build.eclipse.org/webtools/committers/patches-R3.6.0-P/20140701141... > However, I'm not sure that's the ultimate location for the future. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17941) stop relying on snapshot for plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17941?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-17941. ------------------------------------ Resolution: Done Version 0.21.0 of our Tycho plugins was released, and parent pom and target-platform (main and discovery) are using them. > stop relying on snapshot for plugins > ------------------------------------ > > Key: JBIDE-17941 > URL: https://issues.jboss.org/browse/JBIDE-17941 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > while investigating why 0.19-snapshot is missing from http://repository.jboss.org/nexus/content/repositories/snapshots/org/jbos... I found that we seem to always use snapshot in our jbosstools parent pom for these plugins. > And we are now at 0.19 but there is only a 0.16 release. > these plugins should be released and we should depend on the released ones instead of snapshot. Snapshot version is fine for early development, but not for ever. > the only thing that we haven't found a way to make a real release of is the parent pom because of tycho/p2 limitations. But the rest should be releases. > Its worth nothing that any snapshot gets deleted after 90 days (https://community.jboss.org/wiki/MavenSnapshotRepository) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014