[JBoss JIRA] (JBIDE-22197) Icon in template Details of Local Template is not loaded for some templates file
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22197?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22197:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Icon in template Details of Local Template is not loaded for some templates file
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22197
> URL: https://issues.jboss.org/browse/JBIDE-22197
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.0.Alpha2
>
> Attachments: quickstart-template.json, screenshot-1.png
>
>
> {noformat}
> java.io.FileNotFoundException: /icons/apps/java.png
> at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:37)
> at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169)
> at java.net.URL.openConnection(Unknown Source)
> at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32)
> at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
> at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:219)
> at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283)
> at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:164)
> at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52)
> at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86)
> at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
> at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:214)
> at org.jboss.tools.openshift.internal.common.ui.ImageRepository.getImage(ImageRepository.java:85)
> at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:62)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.updateImage(TemplateDetailViews.java:106)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.onVisible(TemplateDetailViews.java:102)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:90)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:79)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews$1.handleValueChange(AbstractStackedDetailViews.java:73)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3747) Build failures with newest JSPM
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ]
Jan Richter edited comment on JBDS-3747 at 4/29/16 5:50 AM:
------------------------------------------------------------
There are 2 options for us here:
- remove JSPM entirely - trying it out now, not quite ready to use yet
- move to JSPM 0.17 once it is released if we fail to get everything working without it
was (Author: jrichter1):
There are 2 options for us here:
- remove JSPM entirely - trying it out now, not quite ready to use yet
- move to JSPM 0.17 once it is released
> Build failures with newest JSPM
> -------------------------------
>
> Key: JBDS-3747
> URL: https://issues.jboss.org/browse/JBDS-3747
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Minor
> Labels: havoc
> Fix For: 10.0.0.Alpha2
>
>
> The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22152:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3747) Build failures with newest JSPM
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3747:
-----------------------------------
There are 2 options for us here:
- remove JSPM entirely - trying it out now, not quite ready to use yet
- move to JSPM 0.17 once it is released
> Build failures with newest JSPM
> -------------------------------
>
> Key: JBDS-3747
> URL: https://issues.jboss.org/browse/JBDS-3747
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Minor
> Labels: havoc
> Fix For: 10.0.0.Alpha2
>
>
> The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3747) Build failures with newest JSPM
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3747:
------------------------------
Fix Version/s: 10.0.0.Alpha2
(was: 10.0.0.Alpha1)
> Build failures with newest JSPM
> -------------------------------
>
> Key: JBDS-3747
> URL: https://issues.jboss.org/browse/JBDS-3747
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Minor
> Labels: havoc
> Fix For: 10.0.0.Alpha2
>
>
> The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21054) Respond to API changes in launchbar
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21054?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21054.
---------------------------------
Launchbar seems to work, but it throws some NPEs when I deploy a project to WildFly using LaunchBar. Reported here: JBIDE-22272
Closing.
> Respond to API changes in launchbar
> -----------------------------------
>
> Key: JBIDE-21054
> URL: https://issues.jboss.org/browse/JBIDE-21054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> Neon is having substantial changes in launchbar.
> [2:40:18 PM] Doug Schaefer: They are here: https://git.eclipse.org/r/#/c/59603/2
> [2:40:38 PM] Doug Schaefer: Essentially removing IRemoteConnection and replacing it with ILaunchTarget.
> [2:40:48 PM] Rob Stryker: ......... {cough}
> [2:41:03 PM] Doug Schaefer: well, you asked for it ;)
> [2:42:04 PM] Doug Schaefer: An example of how to provide ILaunchTargets is here: https://git.eclipse.org/r/#/c/59604/
> Especially the Arduino stuff.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22272) NPE when using LaunchBar to run an app on WildFly
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22272?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22272:
---------------------------------------
It's actually more NPEs thrown at once, but all of them look the same.
> NPE when using LaunchBar to run an app on WildFly
> -------------------------------------------------
>
> Key: JBIDE-22272
> URL: https://issues.jboss.org/browse/JBIDE-22272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I tried to run jboss java ee web app from Central on WildFly 10 using launchbar. And it did work, but a NPE was thrown:
> {code}
> Plug-in: org.eclipse.debug.core
> An exception occurred during launch change notification.
> java.lang.NullPointerException
> at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:84)
> at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
> at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years