October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23282) Upgrade Forge Runtime to 3.3.2.Final

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23282?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23282. --------------------------------- Verified in: Version: 10.2.0.AM2 Build id: AM2-v20161011-0458-B6186 Build date: 20161011-0458 > Upgrade Forge Runtime to 3.3.2.Final > ------------------------------------ > > Key: JBIDE-23282 > URL: https://issues.jboss.org/browse/JBIDE-23282 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.2.AM1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22673. --------------------------------- Since you report that it already helped you find a duplicate, I assume this is working. Closing. > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4105: ------------------------------------- Summary: 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 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 (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22347) NullPointerException in JdtUtils.resolveTypeArguments

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22347?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22347: ---------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.x) > NullPointerException in JdtUtils.resolveTypeArguments > ----------------------------------------------------- > > Key: JBIDE-22347 > URL: https://issues.jboss.org/browse/JBIDE-22347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: Failed to (re)build the JAX-RS metamodel for projet assist-web-war > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveTypeArguments(JdtUtils.java:1009) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.getProvidedKinds(JaxrsProvider.java:264) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.build(JaxrsProvider.java:210) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.build(JaxrsProvider.java:180) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.internalCreateElements(JaxrsElementFactory.java:147) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:75) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:628) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processProject(JaxrsMetamodel.java:506) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:70) > 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.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > 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/5720efc5e4b0a54983...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23165) application wizard: IllegalArgumentException in New OpenShift Application Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23165?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23165: ------------------------------------- Attachment: page-changing-new-wizard.ogv page-changing-context-menu.ogv > application wizard: IllegalArgumentException in New OpenShift Application Wizard > -------------------------------------------------------------------------------- > > Key: JBIDE-23165 > URL: https://issues.jboss.org/browse/JBIDE-23165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > OpenJDK 1.8 > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: error-verifying-user-credentials.png, oc3iare.gif, page-changing-context-menu.ogv, page-changing-new-wizard.ogv, Wrong-direction-screencast.webm > > > {code}java.lang.IllegalArgumentException: > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:47) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$ConnectionAdvancedPropertiesProvider.update(AdvancedConnectionEditor.java:191) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:370) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > 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:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.backPressed(WizardDialog.java:404) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:415) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > 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.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > 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:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23036. --------------------------------- > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4104) Include a version of CDK using OpenShift 3.3

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4104?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4104: --------------------------------------- For iPaas Fuse integration in Fuse Tooling, we require to have the OpenShift 3.3 version incorporated in Development Suite installer. The planned release date is in January. I created the request to include the OpenShift 3.3 in a CDK release (see [CDK-24] ) I created the request to support OpenShift 3.3 in JBDS. It should be only a matter of extensive testing. (see [JBDS-4098] ) Do you have an idea of the time required to include it after the new version of the CDK is released? > Include a version of CDK using OpenShift 3.3 > -------------------------------------------- > > Key: JBDS-4104 > URL: https://issues.jboss.org/browse/JBDS-4104 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Aurélien Pupier > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23133) Make sure magic file library is beta1 and published

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23133?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23133. --------------------------------- I vierified this in github log of jbosstools-base > Make sure magic file library is beta1 and published > --------------------------------------------------- > > Key: JBIDE-23133 > URL: https://issues.jboss.org/browse/JBIDE-23133 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common > Affects Versions: 4.4.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > The foundation.ui dependency on magic file should be beta1. This also means a beta1 build must be created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22610) generate email notifications when automatically fetching TP mirrors

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22610?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22610. --------------------------------- Closing. > generate email notifications when automatically fetching TP mirrors > ------------------------------------------------------------------- > > Key: JBIDE-22610 > URL: https://issues.jboss.org/browse/JBIDE-22610 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.2.AM1 > > > TODO: generate email notifications including links to... > * jenkins job, > * diff files, and > * associated JIRA(s), plus > * instructions for how to build the TP locally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4104) Include a version of CDK using OpenShift 3.3

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4104: ------------------------------------- Summary: Include a version of CDK using OpenShift 3.3 Key: JBDS-4104 URL: https://issues.jboss.org/browse/JBDS-4104 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Reporter: Aurélien Pupier -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016