[JBoss JIRA] (JBIDE-22955) NoStackTrace below CordovaSimLaunchParametersUtil.getCordovaEngineLocation (thrown in WPLibraryResolver.detectVersion)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22955?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22955:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NoStackTrace below CordovaSimLaunchParametersUtil.getCordovaEngineLocation (thrown in WPLibraryResolver.detectVersion)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22955
> URL: https://issues.jboss.org/browse/JBIDE-22955
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Can not detect version. VERSION file C:\Users\dgates\.cordova\lib\wp8\cordova\3.6.0\VERSION is missing
> {noformat}
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.thym.wp.core.WPLibraryResolver.detectVersion(WPLibraryResolver.java:111)
> at org.eclipse.thym.core.engine.HybridMobileLibraryResolver.init(HybridMobileLibraryResolver.java:37)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:245)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchDir(CordovaEngineProvider.java:271)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.searchForRuntimes(CordovaEngineProvider.java:233)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.initEngineList(CordovaEngineProvider.java:83)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getAvailableEngines(CordovaEngineProvider.java:63)
> at org.eclipse.thym.core.engine.HybridMobileEngineManager.getActiveEngines(HybridMobileEngineManager.java:82)
> at org.eclipse.thym.core.HybridProject.getActiveEngines(HybridProject.java:163)
> at org.jboss.tools.cordovasim.eclipse.launch.CordovaSimLaunchParametersUtil.getCordovaEngineLocation(CordovaSimLaunchParametersUtil.java:204)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:79)
> at org.jboss.tools.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:25)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.10.0.v20150303-1130 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.eclipse.thym.core | 2.0.0.201603211426 | 2.0.0.201603211426 |
> | org.eclipse.thym.wp.core | 2.0.0.201603211426 | 2.0.0.201603211426 |
> | org.jboss.tools.cordovasim.eclipse | 3.7.1.Final-v20160331-0435-B86 | 3.7.1.Final-v20160331-0435-B86 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5723aff6e4b0a54983...] 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-22936) IOException below TextFormattingToolBar.createImage (thrown in UnixFileSystem.createFileExclusively)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22936?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22936:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> IOException below TextFormattingToolBar.createImage (thrown in UnixFileSystem.createFileExclusively)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22936
> URL: https://issues.jboss.org/browse/JBIDE-22936
> 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/bold.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.createImage(ImageDescriptor.java:224)
> at org.eclipse.jface.resource.ImageDescriptor.createImage(ImageDescriptor.java:202)
> at org.jboss.tools.vpe.editor.toolbar.format.TextFormattingToolBar.createImage(TextFormattingToolBar.java:216)
> at org.jboss.tools.vpe.editor.toolbar.format.TextFormattingToolBar.createImage(TextFormattingToolBar.java:212)
> at org.jboss.tools.vpe.editor.toolbar.format.TextFormattingToolBar.createItems(TextFormattingToolBar.java:143)
> at org.jboss.tools.vpe.editor.toolbar.SplitToolBar.createToolBarControl(SplitToolBar.java:66)
> at org.jboss.tools.vpe.editor.toolbar.VpeToolBarManager.addToolBar(VpeToolBarManager.java:78)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:572)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:813)
> 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-18525) Investigate how to do module deployment ordering properly with management api
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18525?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18525:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Investigate how to do module deployment ordering properly with management api
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18525
> URL: https://issues.jboss.org/browse/JBIDE-18525
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.CR2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
>
> This is a followup of JBIDE-18373 which was originally about deployment via management api not handling "mark as deployable" files properly. This was fixed, but there's still a problem of ordering. The use case here was a seam project deployed to EAP 6.3. There are three parts:
> 1. Seam project war
> 2. database driver jar
> 3. datasource xml
> When you click "Add and Remove..." on the server in server view, it will sometimes be deployed in the wrong order and fail to deploy.
> Specifically, when you click "Add All" in the dialog, it will not work, whereas if you click "Add" for each of the three resources, it will deploy alright.
> As Rob pointed out, it can get really tricky to guess the right ordering.
> See JBIDE-18373 for more details.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months