October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25024) Usage Analytics New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25024?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25024. ------------------------------ Resolution: Rejected > Usage Analytics New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25024 > URL: https://issues.jboss.org/browse/JBIDE-25024 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Usage Analytics JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Usage Analytics, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Usage Analytics by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25020 #comment Create N&N for Usage Analytics 4.5.1.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Usage Analytics for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25047) Connection wizard: correct advanced buttons to be equal in width

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25047?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25047. --------------------------------- UI is fixed. Closing. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.AM3 Build id: AM3-v20171003-0707-B1202 Build date: 20171003-0707 > Connection wizard: correct advanced buttons to be equal in width > ---------------------------------------------------------------- > > Key: JBIDE-25047 > URL: https://issues.jboss.org/browse/JBIDE-25047 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3, usability > Fix For: 4.5.1.AM3 > > Attachments: corrected-button-width.png, image-2017-09-18-11-44-28-929.png > > > # EXEC: open up connection wizard (either by trying to create a new or edit an existing connection > # EXEC: hit "Advanced" > Result > The buttons "Browse" and "Discover" have different width resulting in an ugly UI > !image-2017-09-18-11-44-28-929.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25021) CDI New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25021?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25021. ------------------------------ Resolution: Rejected > CDI New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25021 > URL: https://issues.jboss.org/browse/JBIDE-25021 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed CDI JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for CDI, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for CDI by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25020 #comment Create N&N for CDI 4.5.1.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for CDI for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25089) Server adapter wizard: oc version exception thrown when using latest 3.7.0.alpha.1

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25089?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25089. --------------------------------- Closing, error message is gone. Verified in: Red Hat JBoss Developer Studio Version: 11.1.0.AM3 Build id: AM3-v20171003-0707-B1202 Build date: 20171003-0707 > Server adapter wizard: oc version exception thrown when using latest 3.7.0.alpha.1 > ---------------------------------------------------------------------------------- > > Key: JBIDE-25089 > URL: https://issues.jboss.org/browse/JBIDE-25089 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Minor > Labels: oc_binary, server_adapter_wizard > Fix For: 4.5.1.AM3 > > > steps: > # ASSERT: use/configure the oc binary that you can download from https://github.com/openshift/origin/releases/download/v3.7.0-alpha.1/open... > # ASSERT: make sure that you have an openshift application running in OpenShift > # EXEC: in OpenShift explorer: select the service/dc/rc for your application and choose "Server adapter..." from the context menu > # ASSERT: server adapter wizard shows up > Result: > In Eclipse log you'll find the following: > {code} > java.lang.IllegalArgumentException: invalid version "3.7.0.alpha.1": invalid qualifier "alpha.1" > at org.osgi.framework.Version.validate(Version.java:205) > at org.osgi.framework.Version.<init>(Version.java:94) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.parseVersion(OCBinaryVersionValidator.java:109) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.parseVersion(OCBinaryVersionValidator.java:93) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.getVersion(OCBinaryVersionValidator.java:78) > at org.jboss.tools.openshift.internal.core.preferences.OCBinaryVersionValidator.isCompatibleForPublishing(OCBinaryVersionValidator.java:132) > at org.jboss.tools.openshift.internal.core.preferences.OCBinary.getStatus(OCBinary.java:137) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.<init>(ServerSettingsWizardPage.java:179) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.<init>(ServerSettingsWizardPage.java:169) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizard.<init>(ServerSettingsWizard.java:48) > at org.jboss.tools.openshift.internal.ui.handler.ServerAdapterHandler.createServer(ServerAdapterHandler.java:137) > at org.jboss.tools.openshift.internal.ui.handler.ServerAdapterHandler.openOrCreateServerAdapter(ServerAdapterHandler.java:127) > at org.jboss.tools.openshift.internal.ui.handler.ServerAdapterHandler.getOpenShiftServer(ServerAdapterHandler.java:106) > at org.jboss.tools.openshift.internal.ui.handler.ServerAdapterHandler.execute(ServerAdapterHandler.java:60) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92) > 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.invokeUsingClass(InjectorImpl.java:305) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239) > 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:487) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039) > 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} > Eclipse preferences will nevertheless recognize it partly correctly as 3.7.0 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24883) Python on windows slaves

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24883?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-24883. ------------------------------ > Python on windows slaves > ------------------------- > > Key: JBIDE-24883 > URL: https://issues.jboss.org/browse/JBIDE-24883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Labels: central-ci > Fix For: 4.5.1.AM2 > > > python installation needs to be scripted in mwqa-cloud-slaves to be installed automatically when provisioning from openstack. > Purpose: facilitate running cross-platform scripts (eg., for JDK detection & discovery). Will allow Nick to start porting .sh script to .py so they can be used on all OSes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24962) org.jboss.tools.jmx.jolokia includes a SNAPSHOT dependencies for 4.5.0.Final

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24962?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24962. --------------------------------- Jolokia no longer relies on the snapshot here: https://github.com/jbosstools/jbosstools-server/blob/master/jmx/plugins/o... Also, the exclusion is removed. Closing. > org.jboss.tools.jmx.jolokia includes a SNAPSHOT dependencies for 4.5.0.Final > ---------------------------------------------------------------------------- > > Key: JBIDE-24962 > URL: https://issues.jboss.org/browse/JBIDE-24962 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: jmx, jolokia > Fix For: 4.5.1.AM2 > > > The bundle org.jboss.tools.jmx.jolokia includes a jolokia client 1.3.7-SNAPSHOT for 4.5.0.Final > We have a check that would have prevented it, but don't know why it did not show up -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24379. --------------------------------- The job has green balls now so closing this JIRA. > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.5.0.Final > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png, javaee-tests-failing_latest_status_jul5_842am_build269.png, jst.ui.test.log > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25058) Add support for MacOS to cdk-scripts project, Update project's doc

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25058?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25058: ---------------------------------- Git Pull Request: https://github.com/odockal/cdk-scripts/pull/15, https://github.com/odockal/cdk-scripts/pull/16 (was: https://github.com/odockal/cdk-scripts/pull/15) > Add support for MacOS to cdk-scripts project, Update project's doc > ------------------------------------------------------------------ > > Key: JBIDE-25058 > URL: https://issues.jboss.org/browse/JBIDE-25058 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.1.AM3 > > > https://github.com/odockal/cdk-scripts/issues/8 > https://github.com/odockal/cdk-scripts/issues/10 > If there is a time, revise actual state of functionality, do another issues in project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24880) deprecate SOAP from jbosstools-webservices

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24880?page=com.atlassian.jira.plugi... ] Rastislav Wagner reassigned JBIDE-24880: ---------------------------------------- Assignee: Rastislav Wagner (was: Jeff MAURY) > deprecate SOAP from jbosstools-webservices > ------------------------------------------ > > Key: JBIDE-24880 > URL: https://issues.jboss.org/browse/JBIDE-24880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, webservices > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.5.x > > > [~psrna] suggests we deprecate the SOAP stuff in Webservices. > I'll let him explain which feature(s) are included in this suggestion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24880) deprecate SOAP from jbosstools-webservices

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24880?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-24880: ------------------------------------------ I already started separating SOAP and REST plugins. > deprecate SOAP from jbosstools-webservices > ------------------------------------------ > > Key: JBIDE-24880 > URL: https://issues.jboss.org/browse/JBIDE-24880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, webservices > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.5.x > > > [~psrna] suggests we deprecate the SOAP stuff in Webservices. > I'll let him explain which feature(s) are included in this suggestion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 2017