[JBoss JIRA] (JBIDE-22935) IOException below MozillaEditor.createVisualToolbar (thrown in UnixFileSystem.createFileExclusively)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22935?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22935:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> IOException below MozillaEditor.createVisualToolbar (thrown in UnixFileSystem.createFileExclusively)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22935
> URL: https://issues.jboss.org/browse/JBIDE-22935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to extract content: osgi.identity; osgi.identity="org.jboss.tools.vpe"; type="osgi.bundle"; version:Version="3.7.1.Final-v20160331-0327-B91"; singleton:="true": org/jboss/tools/vpe/editor/mozilla/icons/refresh.gif
> {noformat}
> java.io.IOException: Permissão negada
> at java.io.UnixFileSystem.createFileExclusively(UnixFileSystem.java:-2)
> at java.io.File.createTempFile(File.java:2024)
> at org.eclipse.osgi.storage.BundleInfo$Generation.storeContent(BundleInfo.java:280)
> at org.eclipse.osgi.storage.bundlefile.ZipBundleFile.getFile(ZipBundleFile.java:186)
> at org.eclipse.osgi.storage.bundlefile.ZipBundleEntry.getFileURL(ZipBundleEntry.java:109)
> at org.eclipse.osgi.storage.url.BundleURLConnection.getFileURL(BundleURLConnection.java:129)
> at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:34)
> at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
> at org.eclipse.jface.resource.FileImageDescriptor.getFilePath(FileImageDescriptor.java:209)
> at org.eclipse.jface.resource.FileImageDescriptor.createImage(FileImageDescriptor.java:162)
> 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.LocalResourceManager.allocate(LocalResourceManager.java:76)
> at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86)
> at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
> at org.eclipse.jface.action.ActionContributionItem.updateImages(ActionContributionItem.java:1057)
> at org.eclipse.jface.action.ActionContributionItem.update(ActionContributionItem.java:794)
> at org.eclipse.jface.action.ActionContributionItem.fill(ActionContributionItem.java:349)
> at org.eclipse.jface.action.ToolBarManager.update(ToolBarManager.java:343)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createVisualToolbar(MozillaEditor.java:514)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:812)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:283)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1102)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:511)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:363)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
> | org.eclipse.osgi | 3.10.102.v20160118-1700 | 3.10.102.v20160118-1700 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 |
> Operating Systems:
> | Linux | 3.13.0 | 3.13.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5762ca83e4b01c929b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22386:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Server Editor: Select different service takes too long
> ------------------------------------------------------
>
> Key: JBIDE-22386
> URL: https://issues.jboss.org/browse/JBIDE-22386
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3, server_editor
> Fix For: 4.6.x
>
>
> Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening.
> Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-15174) Improved work with datatools connection profiles for various projects using hibernate/jpa
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15174?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-15174:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Improved work with datatools connection profiles for various projects using hibernate/jpa
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-15174
> URL: https://issues.jboss.org/browse/JBIDE-15174
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Beta2
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.6.x
>
>
> When working with JPA projects or examples from Central it's necessary to create JPA connection profile. I assume I already have some kind of configuration - either hibernate configuration, or connection directly defined in persistence.xml or defined data source. Still hibernate tooling and eclipse.datatools is complaining that it needs to define connection profile. You have to create a connection configuration again for connection profile to have working tooling. It leads to multiple configurations or you have to reconfigure a project to use eclipse.datatools connection profiles.
> What I would like to see is some mechanism howto easily create connection profiles:
> * the seamless way would be some support for our examples to generate connection profiles when they are imported (or at least to help with that)
> * and some support for hibernate configuration, persistence.xml and ds when creating connection profiles.
> Both features might need some eclipse.datatools contributions. But currently these two worlds (hibernate/jpa tooling and datatools are not very well integrated each other).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23710:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Properites: Disable scaling on completed deployments
> ----------------------------------------------------
>
> Key: JBIDE-23710
> URL: https://issues.jboss.org/browse/JBIDE-23710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Labels: openshift_v3, properties
> Fix For: 4.6.x
>
>
> In web console, scaling completed deployments is disabled.
> In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
> Sometimes I also got this exception (but not allways):
> {noformat}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
> !MESSAGE Unable to scale wildfly-1
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-18101) API updates
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18101?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18101:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> API updates
> -----------
>
> Key: JBIDE-18101
> URL: https://issues.jboss.org/browse/JBIDE-18101
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.6.x
>
>
> Unify the JaxrsElement builders to provide the same methods:
> - buildTransient()
> - buildInMetamodel(JaxrsMetamodel)
> Also, simplify the JaxrsElement#update() method (code could be simpler, with less if/else blocks)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months