[JBoss JIRA] (JBIDE-24991) Improve server port offset detection by inspecting configured system properties
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24991?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24991:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Improve server port offset detection by inspecting configured system properties
> -------------------------------------------------------------------------------
>
> Key: JBIDE-24991
> URL: https://issues.jboss.org/browse/JBIDE-24991
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Environment: JBDS11, WF10
> Reporter: Vsevolod Golovanov
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
>
> The default Wildfly standalone.xml config has port offset configured like this:
> {code}
> <socket-binding-group ... port-offset="${jboss.socket.binding.port-offset:0}">
> {code}
> With the way our configuration process is set up we don't change that. Instead we add a system property to the same config file:
> {code}
> <system-properties>
> <property name="jboss.socket.binding.port-offset" value="10"/>
> </system-properties>
> {code}
> The problem is JBoss Tools doesn't detect this currently. It could be improved to inspect the port-offset attribute and find the corresponding system property value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-21465) 'Disable some filters' option behaves strangely with 'Show installed'
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21465?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21465:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> 'Disable some filters' option behaves strangely with 'Show installed'
> ---------------------------------------------------------------------
>
> Key: JBIDE-21465
> URL: https://issues.jboss.org/browse/JBIDE-21465
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Priority: Minor
> Fix For: 4.6.x
>
> Attachments: filter.png, installed.png
>
>
> I've installed everything from central software/update -> now it says there is nothing to install and gives me an option to disable some filters. Clicking that produces the following dialog:
> !filter.png|thumbnail!
> The first strange part is, I actually need to uncheck the 'Show installed' checkbox in this dialog to show the installed plugins. It might be technically disabling the filter, but it looks weird.
> The second strange thing is, after 'disabling the filter' it shows the installed plugins, but the 'Show installed' checkbox is still unchecked.
> !installed.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22919) SWTException below NavigationUtil.navigateToVisual (thrown in WebBrowser$EvaluateFunction.function)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22919?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22919:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> SWTException below NavigationUtil.navigateToVisual (thrown in WebBrowser$EvaluateFunction.function)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22919
> URL: https://issues.jboss.org/browse/JBIDE-22919
> 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: Unhandled event loop exception
> {noformat}
> org.eclipse.swt.SWTException: Unable to get property 'outerHTML' of undefined or null reference
> at org.eclipse.swt.browser.WebBrowser$EvaluateFunction.function(WebBrowser.java:191)
> at org.eclipse.swt.browser.WebSite.Invoke(WebSite.java:774)
> at org.eclipse.swt.browser.WebSite$7.method6(WebSite.java:130)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119)
> at org.eclipse.swt.internal.ole.win32.COM.VtblCall(COM.java:-2)
> at org.eclipse.swt.internal.ole.win32.IDispatch.Invoke(IDispatch.java:64)
> at org.eclipse.swt.ole.win32.OleAutomation.invoke(OleAutomation.java:571)
> at org.eclipse.swt.ole.win32.OleAutomation.invoke(OleAutomation.java:534)
> at org.eclipse.swt.browser.IE.execute(IE.java:1205)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:435)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:394)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.vpe.preview.core.util.NavigationUtil.navigateToVisual(NavigationUtil.java:161)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$8.mouseUp(VpvEditor.java:424)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.jboss.tools.vpe.preview.core | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> | org.jboss.tools.vpe.preview.editor | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57439711e4b0138d62...] 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-18096) could not complete update project configuration - illegalargumentexception
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18096?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18096:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> could not complete update project configuration - illegalargumentexception
> --------------------------------------------------------------------------
>
> Key: JBIDE-18096
> URL: https://issues.jboss.org/browse/JBIDE-18096
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Labels: f2f2014
> Fix For: 4.6.x
>
>
> while trying to fix import of javaee-samples I bumped into this happening when running update project configuration.
> java.lang.IllegalArgumentException
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.removeProjectFacet(FacetedProjectWorkingCopy.java:876)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:309)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configure(WebProjectConfiguratorDelegate.java:150)
> at org.eclipse.m2e.wtp.AbstractProjectConfiguratorDelegate.configureProject(AbstractProjectConfiguratorDelegate.java:93)
> at org.eclipse.m2e.wtp.WTPProjectConfigurator.configure(WTPProjectConfigurator.java:70)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> It happened on ~100 projects so was quite invasive ;/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23647) UI freeze while trying to starting the forge runtime
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23647?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23647:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> UI freeze while trying to starting the forge runtime
> ----------------------------------------------------
>
> Key: JBIDE-23647
> URL: https://issues.jboss.org/browse/JBIDE-23647
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Fix For: 4.6.x
>
> Attachments: image-2016-12-14-18-17-34-950.png
>
>
> maybe caused to the fact that I'm in development mode, in this case we can transform it from bug to enhancement request.
> I hit Ctrl+4 and then the UI is blocked:
> !image-2016-12-14-18-17-34-950.png|thumbnail!
> I have this stack in logs
> {noformat}
> Dec 14, 2016 6:03:24 PM org.jboss.forge.furnace.impl.FurnaceImpl start
> SEVERE: Error occurred.
> java.lang.RuntimeException: Could not create Addon Directory [C:\Data\TP\org.fusesource.ide.targetplatform.target.repo-Neon-WithSAP\plugins\org.jboss.tools.forge.runtime_2.0.102.v20161124-1441.jar\addon-repository]
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:50)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository$1.call(AbstractFileSystemAddonRepository.java:42)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AbstractFileSystemAddonRepository.getRootDirectory(AbstractFileSystemAddonRepository.java:41)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:137)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$3.call(AddonRepositoryStateStrategyImpl.java:133)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.getRepositoryRegistryFile(AddonRepositoryStateStrategyImpl.java:132)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.access$000(AddonRepositoryStateStrategyImpl.java:39)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:224)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl$7.call(AddonRepositoryStateStrategyImpl.java:219)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryStateStrategyImpl.listAll(AddonRepositoryStateStrategyImpl.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listAll(AddonRepositoryImpl.java:146)
> at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listAll(ImmutableAddonRepository.java:81)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:92)
> at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:37)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:218)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:205)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:204)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:347)
> at org.jboss.forge.furnace.impl.FurnaceImpl$3.call(FurnaceImpl.java:329)
> at org.jboss.forge.furnace.impl.lock.LockManagerImpl.performLocked(LockManagerImpl.java:55)
> at org.jboss.forge.furnace.impl.FurnaceImpl.getAddonRegistry(FurnaceImpl.java:328)
> at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:224)
> at org.jboss.forge.furnace.impl.FurnaceImpl$1$1.run(FurnaceImpl.java:186)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20911:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> open local terminal with oc already logged in
> ---------------------------------------------
>
> Key: JBIDE-20911
> URL: https://issues.jboss.org/browse/JBIDE-20911
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Labels: oc_binary
> Fix For: 4.6.x
>
>
> it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin> --server=<serverurl>` executed at start.
> This would allow users to work with CLI whenever the UI does not have exactly the command needed by user.
> * This assumes users have oc in their path
> * might need different commands based on what OS (windows vs *nix)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months