[JBoss JIRA] (JBIDE-25613) Implement fixes into AS itests
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25613?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25613:
---------------------------------------
[~rob.stryker] Tasks could look like:
1. Update list of servers to tests (JBIDE-25615).
2. Test servers to have them running without issues (all test suites should be without issues and errors): there are some issues with older Java for some servers.
3. Have stable job running full suite (weekly).
We will discuss who will fix it and assign it to him.
> Implement fixes into AS itests
> --------------------------------
>
> Key: JBIDE-25613
> URL: https://issues.jboss.org/browse/JBIDE-25613
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests, server
> Affects Versions: 4.5.2.Final
> Reporter: Ondrej Dockal
> Priority: Critical
>
> Server ui itests requires huge refactoring as there are missing parameters in pom.xml (runtimes.suite.scope), pretty old testsing configuration are used (jre6?), redudant static variables used for creating parametrized tests suite, etc...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25832) Credentials composite doesn't update if underlying model changes
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-25832:
-----------------------------------
Summary: Credentials composite doesn't update if underlying model changes
Key: JBIDE-25832
URL: https://issues.jboss.org/browse/JBIDE-25832
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: foundation, runtime-detection
Reporter: Rob Stryker
Credentials composite doesn't update if underlying model changes. Workflow for this is a bit complicated, but:
1) Start with a clean workspace
2) Open server view
3) Choose cdk 3.2+
4) Click "Download runtime..." (DO NOT add credentials before this!)
5) In the download runtime dialog, add the proper credentials
6) Complete the dl-rt wizard
7) Note the new server wizard is downloading the runtime and all widgets are frozen
8) The download completes, some fields get filled in
9) The credential combo does not get updated. They are disabled except for 'add'
10) If you try to add the same credentials again, it will tell you they already exist
11) You must cancel the wizard and start it over.
Also as part of this patch, we should change all dl-rt strings that reference jboss.org credentials, as they have been replaced with redhat.com credentials.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25829) Error when you cancel minishift location selection while creating cdk server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25829?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25829:
--------------------------------
Fix Version/s: 4.5.3.AM3
> Error when you cancel minishift location selection while creating cdk server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25829
> URL: https://issues.jboss.org/browse/JBIDE-25829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> I just noticed there is an error when you start the New Server dialog, select cdk 3.2+ and on the next page you first try to Browse for the minishift binary and then you change your mind and cancel that window.
> {code}
> Unhandled event loop exception
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.kickValidationJob(CDK3ServerWizardFragment.java:218)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.access$3(CDK3ServerWizardFragment.java:214)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment$3.widgetSelected(CDK3ServerWizardFragment.java:197)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4258)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4082)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:58)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> 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:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4258)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4082)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699)
> 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)
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25303:
------------------------------------------
[~jkopriva] with my latest patch which rsyncs with --no-perms you should not face the permission issues any more if you use the latest fabric8/s2i-java image.
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.3.AM3
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> ** -Dfabric8.generator.from=fabric8/s2i-java
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25831) circular dependency in hibernate builds?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25831?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25831:
-------------------------------
Description:
Somehow, the jbosstools-hibernate build is trying to download stuff from the /oxygen/staging/updates/core/4.5.3.AM2 site.
It should NOT be sourcing a site that contains hibernate plugins (and stuff downstream from hibernate) as this could cause an inadvertent circular dependency.
{code}
16:46:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
16:46:48 [ERROR] Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
16:46:48 [ERROR] Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM.... Premature end of Content-Length delimited message body (expected: 6775721; received: 5831379
16:46:48 [ERROR] -> [Help 1]
16:46:48 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
16:46:48 Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
16:46:48 Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM... --https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-hibernate_master/1766/console
was:
Somehow, the jbosstools-hibernate build is trying to download stuff from the /oxygen/staging/updates/core/4.5.3.AM2 site.
It should NOT be sourcing a site that contains hibernate plugins (and stuff downstream from hibernate) as this could cause an inadvertent circular dependency.
{code}
16:46:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
16:46:48 [ERROR] Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
16:46:48 [ERROR] Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM.... Premature end of Content-Length delimited message body (expected: 6775721; received: 5831379
16:46:48 [ERROR] -> [Help 1]
16:46:48 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
16:46:48 Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
16:46:48 Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM...
> circular dependency in hibernate builds?
> ----------------------------------------
>
> Key: JBIDE-25831
> URL: https://issues.jboss.org/browse/JBIDE-25831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, hibernate
> Affects Versions: 4.5.3.AM3
> Reporter: Nick Boldt
>
> Somehow, the jbosstools-hibernate build is trying to download stuff from the /oxygen/staging/updates/core/4.5.3.AM2 site.
> It should NOT be sourcing a site that contains hibernate plugins (and stuff downstream from hibernate) as this could cause an inadvertent circular dependency.
> {code}
> 16:46:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
> 16:46:48 [ERROR] Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
> 16:46:48 [ERROR] Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM.... Premature end of Content-Length delimited message body (expected: 6775721; received: 5831379
> 16:46:48 [ERROR] -> [Help 1]
> 16:46:48 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.hibernate.runtime.v_4_3: Execution attached-p2-metadata of goal org.eclipse.tycho:tycho-p2-plugin:1.1.0:p2-metadata failed: Error trying to download org.jboss.tools.hibernate.runtime.v_4_3 version 5.2.3.v20180203-1505 from http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2:
> 16:46:48 Download of osgi.bundle,org.jboss.tools.hibernate.runtime.v_4_3,5.2.3.v20180203-1505 failed on repository http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM2. Retrying. :
> 16:46:48 Unable to read repository at http://download.jboss.org/jbosstools/oxygen/staging/updates/core/4.5.3.AM... --https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-hibernate_master/1766/console
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25822) Support setup-cdk in Eclipse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25822:
-------------------------------------
Sprint: devex #146 March 2018
> Support setup-cdk in Eclipse
> ----------------------------
>
> Key: JBIDE-25822
> URL: https://issues.jboss.org/browse/JBIDE-25822
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> JBIDE-25753 added support for downloading cdk directly from the IDE. So that moves us closer for the user to be able to avoid CLI at all. But there is still one piece missing - running minishift cdk-setup after you download the binary - without that you still won't be able to run cdk.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months