[JBoss JIRA] (JBDS-4651) JDK9 Certification - cdi
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4651?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4651:
------------------------------------
All CDI tests and also almost all Deltaspike tests passed. Few Deltaspike tests failed because of unexpected warning in Problem view.
List of failed tests:
ValidationsInPreferenceTest.java:84) testConfigureProblemSeverity
ExceptionHandlerMethodsTest.java:120) testBeforeHandlerAdditionalParameters
ExceptionHandlerMethodsTest.java:120) testHandlerAdditionalParameters
I performed these tests by hand and finded out that it is not an real issue. In the future, I will have to update all resources/prj/**/pom.xml, maven-compiler-plugin have to be configured to use java 9. It will be also necessary to run tests against WildFly 11 which supports JDK9, but first of all
JBIDE-25578 must be fixed.
> JDK9 Certification - cdi
> ------------------------
>
> Key: JBDS-4651
> URL: https://issues.jboss.org/browse/JBDS-4651
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Pavol Srna
> Assignee: Lukáš Valach
> Fix For: 11.2.0.GA
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 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 updated JBIDE-25303:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1635, https://github.com/jbosstools/jbosstools-server/pull/553, https://github.com/jbosstools/jbosstools-central/pull/416 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1635, https://github.com/jbosstools/jbosstools-server/pull/553)
> 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.2.Final
>
> Attachments: fuse-on-openshift.zip, project-deployment-assembly.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.
> # 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, 2 months
[JBoss JIRA] (JBIDE-25111) Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25111?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25111:
------------------------------------------
merged into master.
> Explorer, Properties: allow intellingent "Delete Resource" (via label-matching?)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25111
> URL: https://issues.jboss.org/browse/JBIDE-25111
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.2.Final
>
> Attachments: 2018-01-10 at 19-59-40.mp4, filter-and-selected-resources.png
>
>
> OpenShift Online only allows you 1 project. Thus the usual approach to create a project per application and kill the project to remove all resources cannot be used in OpenShift online. We thus need a way to delete all resources that are related to an application. Ex. with a more powerful delete action that pops up a window with a filter-/query-parameter that would filter the list of available resources and then allow to delete all the visible (or selected ones)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months