April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4237: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 12.x > > Attachments: CVE-report.png, Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4167) Provide progression when installing "Supplemental Runtimes"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4167?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4167: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Provide progression when installing "Supplemental Runtimes" > ----------------------------------------------------------- > > Key: JBDS-4167 > URL: https://issues.jboss.org/browse/JBDS-4167 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.2.0.AM3 > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 12.x > > Attachments: image-2016-11-08-09-38-19-198.png > > > it stays several seconds (perhaps several minutes) in this state: > !image-2016-11-08-09-38-19-198.png|thumbnail! > wondering if it is frozen or not -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4164) Project Examples don't work behind proxy

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4164?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4164: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Project Examples don't work behind proxy > ---------------------------------------- > > Key: JBDS-4164 > URL: https://issues.jboss.org/browse/JBDS-4164 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jbpm, project-examples, upstream > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Fix For: 12.x > > > Issue is reported on forum (see [forum reference|https://developer.jboss.org/message/964401#964401]). Examples does not work behind proxy with eclipse configured to use proxy in settings. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4105: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 12.x > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3917?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3917: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Verify target-platform PR by running compile/package (no tests) build for all modules > ------------------------------------------------------------------------------------- > > Key: JBDS-3917 > URL: https://issues.jboss.org/browse/JBDS-3917 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, target-platform > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 12.x > > > Would be good to have this as part of TP PR Verification build. > Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. > Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4515) Wrong text format/style on linux on installer/uninstaller

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4515?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4515: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Wrong text format/style on linux on installer/uninstaller > --------------------------------------------------------- > > Key: JBDS-4515 > URL: https://issues.jboss.org/browse/JBDS-4515 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 11.0.0.GA > Environment: Fedora > Reporter: Ondrej Dockal > Fix For: 12.x > > Attachments: installer_text_formatting.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4488) Very slow initial startup of devstudio RPM after installing from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4488?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4488: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Very slow initial startup of devstudio RPM after installing from Central > ------------------------------------------------------------------------ > > Key: JBDS-4488 > URL: https://issues.jboss.org/browse/JBDS-4488 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 11.0.0.AM2 > Environment: * rh-eclipse47 (http://download.eng.bos.redhat.com/rel-eng/DevTools-1.0-RHEL-7-Beta-1.0/c...) > * devstudio (https://devstudio.jboss.com/11/snapshots/builds/devstudio.rpm_master/2017...) > Reporter: Martin Coufal > Assignee: Jeff MAURY > Priority: Minor > Fix For: 12.x > > > Launching Eclipse after installation of any plugins from Devstudio (Red Hat Central) takes VERY long time (around 180s). This is regression bug, for more details, see [1]. > Note: Also, launching rh-eclipse47 with Devstudio takes about 90s. > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1392095 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4442) Central page does not work on Fedora 26 if package webkitgtk3 is not installed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4442?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4442: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Central page does not work on Fedora 26 if package webkitgtk3 is not installed > ------------------------------------------------------------------------------ > > 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: 12.x > > > 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.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4413) No help content in DevStudio 10.4.0 for CDK, Minishift

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4413?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4413: ----------------------------- Fix Version/s: 12.x (was: 11.x) > No help content in DevStudio 10.4.0 for CDK, Minishift > ------------------------------------------------------ > > Key: JBDS-4413 > URL: https://issues.jboss.org/browse/JBDS-4413 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: documentation > Affects Versions: 10.4.0.AM3 > Environment: DevStudio 10.4.0 GA on Win 10 Pro/64, installed via DevSuite 1.4 installer > Reporter: Robert Terzi > Fix For: 12.x > > > There is no relevant help text that can be easily found from within DevStudio to for CDK, minishift, container development kit. > Note: CDK yields a lot of hits for a different CDK (not red hat container development kit). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4343) Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*'

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4343?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4343: ----------------------------- Fix Version/s: 12.x (was: 11.x) > Installation hangs on 'Configuring toolingorg.eclipse.equinox.launcher.*' > ------------------------------------------------------------------------- > > Key: JBDS-4343 > URL: https://issues.jboss.org/browse/JBDS-4343 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.4.0.AM2 > Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: performance > Fix For: 12.x > > Attachments: install.png > > > The installer spends several minutes in this state: > !install.png|thumbnail! > Just for comparison > - AM1 installation takes total of about 2 minutes 15 seconds > - AM2 takes 5 minutes 40 seconds > There is no shortage of memory or disk I/O availability, the CPU is not topped off (even though AM2 eats up more CPU itself during this time). > DTRACE=true reveals nothing interesting really, this is what it says in the particular moment (notice how much time the operation takes): > {noformat} > Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64 > Preparing to commit the provisioning operation. > Committing the provisioning operation. > Operation completed in 289855 ms. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018