July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22807: ---------------------------------- Steps to Reproduce: Machydra job for example: machydra job: jbds10-nightly.freemarker.ui.test. Otherwise: run integration tests with maven commands in command line and pass parameter test.installBase=existing/devstudio/path was:for example: machydra job: jbds10-nightly.freemarker.ui.test. > Could not install bundle. A bundle is already installed with the name xxx > ------------------------------------------------------------------------- > > Key: JBIDE-22807 > URL: https://issues.jboss.org/browse/JBIDE-22807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Environment: Fedora 24, x86_64 > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160720-1632-B5674 > OpenJDK Runtime Environment (build 1.8.0_92-b14) > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > > Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio) > Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message). > This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22807: ---------------------------------- Fix Version/s: 4.4.1.AM2 > Could not install bundle. A bundle is already installed with the name xxx > ------------------------------------------------------------------------- > > Key: JBIDE-22807 > URL: https://issues.jboss.org/browse/JBIDE-22807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Environment: Fedora 24, x86_64 > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160720-1632-B5674 > OpenJDK Runtime Environment (build 1.8.0_92-b14) > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > > Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio) > Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message). > This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22846) Incorrectly referenced artifact are not validated/reported in Source tab in batch editor.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22846?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22846. --------------------------------- Fix Version/s: 4.4.1.AM2 Resolution: Cannot Reproduce I could not reproduce this bug anymore, closing. > Incorrectly referenced artifact are not validated/reported in Source tab in batch editor. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22846 > URL: https://issues.jboss.org/browse/JBIDE-22846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160725-1821-B5680 > Build date: 20160725-1821 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: BatchNoValidationSourceTab.png > > > There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22382: ------------------------------------- [~crobson] the icon used in the attached screenshot was reverted to the shadowman when [~james.cobb] pointed out we couldn't use that branding in a product, right before the JBDS 10 release. So this is what we currently have: !http://content.screencast.com/users/fbricon/folders/Jing/media/0eaad79e-b968-48a4-8da8-9ce3baf52d26/00000446.png|width=650! > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21766) NPE when trying to generate mapping files on project with no console config

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21766?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-21766. ------------------------------- Resolution: Done > NPE when trying to generate mapping files on project with no console config > --------------------------------------------------------------------------- > > Key: JBIDE-21766 > URL: https://issues.jboss.org/browse/JBIDE-21766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.1.AM3 > > > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.getService(ConfigurationActor.java:127) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:134) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:117) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172) > at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1554) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1551) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:899) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1186) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3627: ------------------------------------------- Note - this issue is not about JBDS, this is about developer suite installer. I don't know the status of devstudio [~rob.stryker] can you give an update ? > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Catherine Robson commented on JBIDE-22382: ------------------------------------------ [~james.cobb] Can you take a look at this? There's a screenshot of how the developers icon is being used for Red Hat Central. Red Hat Central is a "landing page" for our version of Eclipse that gives developers news, access to quickstarts and other project starters, etc. My thought is we have two options: # Move this towards Red Hat Developers branding with name & with wording - see if we can associate it with the program completely since the content is the same content that we have on the site, and we're trying to drive Developers towards the site then with this mechanism as a entrypoint into what we have to offer Red Hat Developers. My preference is here. # Remove the Developers branding and move back to Shadowman, and keep it generic to Red Hat. > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- [~jeffmaury], thanks! works like a charm \o/ > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3853) Installer: use node-rcedit instead of resourceHacker

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-3853?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-3853. ------------------------------- Metadata of installer archives from build jobs seems fine, closing. > Installer: use node-rcedit instead of resourceHacker > ---------------------------------------------------- > > Key: JBDS-3853 > URL: https://issues.jboss.org/browse/JBDS-3853 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Jan Richter > Labels: havoc > Fix For: 10.1.0.AM2 > > > Installer's metadata and icon are changed by Gulp using Resource Hacker which requires that we manually pre-compile its configuration on every change in metadata (e.g. project version). > Change it to node-rcedit module (already used by electron-packager to do the same thing for binary inside self-extracting zip) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22821) foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22821?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22821: ------------------------------------- the resolved version is 4.4.1.AM2, as seen in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... So it *should* work. Anyways, we can still make the version parser smarter and try to resolve x.AM from x.AMy > foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22821 > URL: https://issues.jboss.org/browse/JBIDE-22821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.1.AM3 > > > foundation.core is version 1.3.1.AM1 so can't resolve from ide-config.props = 4.4.1.AM2 or 4.4.1.AM, either > [~fbricon] should the parser be able to resolve 4.4.1.AM so I can at least differentiate from 4.4.1 or 4.4.1.Final? > Meanwhille, need to figure out why foundation.core thinks it's AM1 and not AM2. jgit timestamps, maybe? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 July 2016