5:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-25303 at 12/11/17 6:43 AM:
--------------------------------------------------------------------
[~jeffmaury] [~rob.stryker] [~aurelien.pupier]
* No. 1 aka DEV_MODE seems resolved, the image now has a label that advertises JAVA_DEBUG
to enable the "DEVMODE" which works.
* No. 2 aka deployment was agreed upon that we would not require any change in the
imported project but the server adapter would publish the approriate files to
<deployment-folder>/BOOT-INF/classes since BOOT-INF/classes is the structure
that's *ALWAYS* used by the springboot fat-jar packaging.
In regard of No 2 I noticed that if you set the publisher to publish to BOOT-INF/classes
everything, source and compilation units alike. Here's what's present in the local
deploy folder that then gets sent to the pod:
{code}
$ ls -l
total 56
-rw-r--r-- 1 adietish staff 11357 Dec 11 12:41 LICENSE.md
-rw-r--r-- 1 adietish staff 2267 Dec 11 12:41 README.md
drwxr-xr-x 6 adietish staff 192 Dec 11 12:41 classes
drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 configuration
-rw-r--r-- 1 adietish staff 906 Dec 11 12:41 devtools.sh
drwxr-xr-x 46 adietish staff 1472 Dec 11 12:41 lib
-rw-r--r-- 1 adietish staff 6343 Dec 11 12:41 pom.xml
drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 src
drwxr-xr-x 4 adietish staff 128 Dec 11 12:41 target
{code}
[~rob.stryker] Thoughts?
was (Author: adietish):
[~jeffmaury] [~rob.stryker] [~aurelien.pupier]
* No. 1 aka DEV_MODE seems resolved, the image now has a label that advertises JAVA_DEBUG
to enable the "DEVMODE" which works.
* No. 2 aka deployment was agreed upon that we would not require any change in the
imported project but the server adapter would publish the approriate files to
<deployment-folder>/BOOT-INF/classes since BOOT-INF/classes is the structure
that's *ALWAYS* used by the springboot fat-jar packaging.
In regard of No 2 I noticed that if you set the publisher to publish to BOOT-INF/classes
everything, source and compilation units alike. Here's what's present in the local
deploy folder that then gets sent to the pod:
{code}
ingboot-xml/deploy ls -l
total 56
-rw-r--r-- 1 adietish staff 11357 Dec 11 12:41 LICENSE.md
-rw-r--r-- 1 adietish staff 2267 Dec 11 12:41 README.md
drwxr-xr-x 6 adietish staff 192 Dec 11 12:41 classes
drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 configuration
-rw-r--r-- 1 adietish staff 906 Dec 11 12:41 devtools.sh
drwxr-xr-x 46 adietish staff 1472 Dec 11 12:41 lib
-rw-r--r-- 1 adietish staff 6343 Dec 11 12:41 pom.xml
drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 src
drwxr-xr-x 4 adietish staff 128 Dec 11 12:41 target
{code}
[~rob.stryker] Thoughts?
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.AM3
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)
3036
days inactive
3036
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Andre Dietisheim (JIRA)