June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24289) Update JBoss Tools features page

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24289?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24289: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Update JBoss Tools features page > -------------------------------- > > Key: JBIDE-24289 > URL: https://issues.jboss.org/browse/JBIDE-24289 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > > Once Fuse Tooling is in JBT, we'll have to update http://tools.jboss.org/features/index.html to reflect that fact. > See https://github.com/jbosstools/jbosstools-website/blob/master/features/apa... for source of the page to update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24285) Java coredump when starting jboss server from Eclipse

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24285?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24285: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Java coredump when starting jboss server from Eclipse > ----------------------------------------------------- > > Key: JBIDE-24285 > URL: https://issues.jboss.org/browse/JBIDE-24285 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Environment: Windows 7 > System memory 24GB - memory checked and no issues found. > JDK 1.8.0_121 x64 > JBoss EAP 6.4 > Eclipse Neon.3 with JBoss server support installed (Not full JBoss Developer Studio) > Reporter: Beirti O'Nunain > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: hs_err_pid53068.log, hs_err_pid58832.log > > > Intermittently, when starting a JBoss server from the "servers" view in Debug mode, the process coredumps shortly after starting the application. (3rd party application provided by Calypso) I've not seen this with non-jboss processes yet. > Problematic frame always points to jvm.dll (same frame 0x68637). Logs attached. > I've started the JBoss process with -Xcheck:jni but unfortunately the console is full of noise from > WARNING: JNI local refs: zu, exceeds capacity: zu > which causes the process to timeout on startup due to massively slowing down the startup. You can add this flag locally to see full logs > Have also tried bumping Xmx/Xms from 1g to 4g but still getting the same issue. This issue does not occur if I start the server in 'run' mode instead of 'debug'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24454) Configure jbosstools-server project to have test files recognize as such by Sonar

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24454?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24454: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Configure jbosstools-server project to have test files recognize as such by Sonar > --------------------------------------------------------------------------------- > > Key: JBIDE-24454 > URL: https://issues.jboss.org/browse/JBIDE-24454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.4.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > > it will avoid to have "Define and throw a dedicated exception instead of using a generic one." issues reported on test methods for which it is perfectly normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24318) Analyze watch replacement

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24318?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24318: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Analyze watch replacement > ------------------------- > > Key: JBIDE-24318 > URL: https://issues.jboss.org/browse/JBIDE-24318 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > > Analyze how the watch and watch manager can be implemented when switching to the fabric8 client -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24293: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Lot of blank lines written to terminal when starting the CDK server > ------------------------------------------------------------------- > > Key: JBIDE-24293 > URL: https://issues.jboss.org/browse/JBIDE-24293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: terminalOutputWhenStartingCDK.txt > > > Windows 10 > Version: 10.4.0.AM3 > Build id: AM3-v20170406-1058-B390 > Build date: 20170406-1058 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24480) Configure sonar for jbosstools-base

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24480?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24480: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Configure sonar for jbosstools-base > ----------------------------------- > > Key: JBIDE-24480 > URL: https://issues.jboss.org/browse/JBIDE-24480 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM2 > > > Configure PR builds + master daily builds with storing the results and test coverage -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4442) Central page is not working

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4442?page=com.atlassian.jira.plugin.... ] Josef Kopriva updated JBDS-4442: -------------------------------- Fix Version/s: 11.0.0.AM2 > Central page is not working > --------------------------- > > Key: JBDS-4442 > URL: https://issues.jboss.org/browse/JBDS-4442 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: central > Affects Versions: 11.0.0.AM1 > Environment: Fedora 26 Alpha > Red Hat JBoss Developer Studio > Version: 11.0.0.AM1 > Build id: AM1-v20170606-1759-B247 > Build date: 20170606-1759 > Reporter: Josef Kopriva > Assignee: Supriya Bharadwaj > Fix For: 11.0.0.AM2 > > > After fresh installation of F26 and Devstudio central shows error message > {code:java} > org.eclipse.swt.SWTException: An exception was raised in JavaScript > at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273) > at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324) > at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409) > at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663) > at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610) > at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175) > at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163) > at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480) > at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077) > at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614) > at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106) > at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) > 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:355) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 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:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955) > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:5434) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201) > 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:52) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60) > 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:173) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187) > at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261) > at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176) > at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117) > at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098) > at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437) > at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425) > at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4492) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4105) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 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.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24529) Some versions of N&N are inaccessible, e.g. 4.3.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24529?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24529: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Some versions of N&N are inaccessible, e.g. 4.3.0.Final > ------------------------------------------------------- > > Key: JBIDE-24529 > URL: https://issues.jboss.org/browse/JBIDE-24529 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Fix For: 4.5.0.Final > > > JBIDE-23779 reduced the amount of versions available at https://tools.jboss.org/documentation/whatsnew/ > which is fine. > But I noticed, that some versions are now inaccessible. > If you go to https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html you will see several versions in the left-hand menu. The oldest being 4.3.1.Final. Now what if I want to see 4.3.0.Final? I would try Previous Versions, but that's too old - that's an old page where the newest version is 4.2.0.Alpha2. > Currently the only way to find the 4.3.0.Final N&N is to go through the download page: > https://tools.jboss.org/downloads/jbosstools/mars/4.3.0.Final.html > And then click the What's New link there which will take you to > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Final.html > So I think we should make sure that pages such as https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html contain all the relevant versions in the left-hand menu. I assume it's a matter of a list in a config file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24491: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM2 > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24490) access.redhat.com in credentials prefpage shows drupal icon

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24490?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24490: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > access.redhat.com in credentials prefpage shows drupal icon > ----------------------------------------------------------- > > Key: JBIDE-24490 > URL: https://issues.jboss.org/browse/JBIDE-24490 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation, upstream > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > > This is an upstream issue, but their favicon.ico is a drupal image. On the website it's fine, but the url access.redhat.com/favicon.ico is wrong. This makes our tools load the wrong image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017