[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26180 at 8/21/18 10:06 AM:
--------------------------------------------------------------
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
was (Author: nickboldt):
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
* reddeer 2.3
* m2e 1.9.1.something (ping Fred after M3 is done)
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e 1.9.1.something (ping Fred after M3 is done)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26180 at 8/21/18 10:05 AM:
--------------------------------------------------------------
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
* reddeer 2.3
* m2e 1.9.1.something (ping Fred after M3 is done)
was (Author: nickboldt):
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26309) Openshift.io Login does not work
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26309?page=com.atlassian.jira.plugi... ]
Josef Kopriva reassigned JBIDE-26309:
-------------------------------------
Assignee: Josef Kopriva
> Openshift.io Login does not work
> --------------------------------
>
> Key: JBIDE-26309
> URL: https://issues.jboss.org/browse/JBIDE-26309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Critical
> Labels: Regression
> Fix For: 4.9.0.AM2
>
>
> Steps:
> 1. Try to login to OpenShift.IO with button taskbar of devstudio.
> 2. An error dialog is shown.
> Error message in Error Log:
> {code:java}
> eclipse.buildId=12.9.0.AM2-v20180815-0130-B3168
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.equinox.registry
> Error
> Mon Aug 20 12:23:18 CEST 2018
> Plug-in org.jboss.tools.openshift.io.ui was unable to load class org.jboss.tools.openshift.io.internal.ui.DefaultLoginProvider.
> java.lang.ClassNotFoundException: org.jboss.tools.openshift.io.internal.ui.DefaultLoginProvider cannot be found by org.jboss.tools.openshift.io.ui_3.5.2.v20180807-2303
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:508)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60)
> at org.jboss.tools.openshift.io.core.LoginProvider.get(LoginProvider.java:32)
> at org.jboss.tools.openshift.io.core.AccountService.<init>(AccountService.java:38)
> at org.jboss.tools.openshift.io.core.AccountService.<clinit>(AccountService.java:36)
> at org.jboss.tools.openshift.internal.io.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.internal.io.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at org.jboss.tools.openshift.io.core.TokenProvider.getToken(TokenProvider.java:27)
> at org.jboss.tools.openshift.internal.io.ui.handler.GetTokenHandler.execute(GetTokenHandler.java:30)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:93)
> 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:317)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:251)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:161)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:153)
> 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:204)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> 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:5769)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1370)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5023)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4555)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1170)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1059)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:625)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:560)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
> 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:656)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1498)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1471)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26311:
---------------------------------------
This happens also with WildFly 12.
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26310:
---------------------------------------
Thank you!
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM2
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Martin Malina (JIRA)
Martin Malina created JBIDE-26311:
-------------------------------------
Summary: EAP 7.1 fails to stop when connected over ssh
Key: JBIDE-26311
URL: https://issues.jboss.org/browse/JBIDE-26311
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.9.0.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
Server Red Hat JBoss EAP 7.1 ssh failed to stop.
An exception stack trace is not available.
It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-26310.
---------------------------------
Cool! I looked at the test PR and the job and everything seems to be correct. Closing this issue.
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM2
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal resolved JBIDE-26310.
-----------------------------------
Resolution: Done
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM2
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month
[JBoss JIRA] (JBIDE-26310) Have jenkins PR check job set to jboss-stacks
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26310?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26310:
---------------------------------------
Trigger to github jboss-stacks PR added:
!Screenshot_20180821_103305.png|thumbnail!
Job results green, #18 triggered upon creating PR, #19 was triggered after "testPR" magic word inserted in github PR comment section:
!Screenshot_20180821_103625.png|thumbnail!
[~mmalina] Seems valid to me, would you verify this jira?
[~rob.stryker] thanks for adding bot.
> Have jenkins PR check job set to jboss-stacks
> ---------------------------------------------
>
> Key: JBIDE-26310
> URL: https://issues.jboss.org/browse/JBIDE-26310
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.9.0.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Fix For: 4.9.0.AM2
>
> Attachments: Screenshot_20180821_103305.png, Screenshot_20180821_103625.png
>
>
> Prepare PR check jenkins job to jboss-stacks repo.
> * configure jenkins job to run org.jboss.jdf.stack.test unit tests
> * assure that rhdevelopers-ci bot have rights to repo
> * verify job being run on new PR
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 1 month