[jbosstools-issues] [JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556264#comment-13556264 ] 

Andre Dietisheim edited comment on JBIDE-25504 at 4/4/18 5:54 PM:
------------------------------------------------------------------

[~rhuss] I get the spring-boot app restarting fine but fail to have it load classes that I'd expect to hot swap:
I run the camel spring-boot example as exploded jar. I have the camel spring-boot example classes deployed to **/deployments/BOOT-INF/classes. The dependency is present as a jar in **/deployments/BOOT-INF/lib**.  
I then try to hot swap the dependency by replacing the dependency jar with an exploded version (I tried both variants, adding an exploded folder with a different name or then replacing the jar with an exploded folder that has the same name). Spring-Boot then detects the change, restarts the whole app but wont use the new classes in the dependency. It still runs the classes that it had from the jar. 

I have the classpath pointing to the following:

{code}
    -cp /deployments/BOOT-INF/classes/:/deployments/BOOT-INF/lib/*:/deployments/BOOT-INF/lib/:/deployments
{code}

I also have the following file in /deployments/BOOT-INF/classes/META-INF/spring-devtools.properties where I try to push project B into the restart classloader

{code}
    restart.include.dependency=/dependency-.*
{code}

Do you have any idea what I a missing so that I can hot swap classes in the dependency?


was (Author: adietish):
[~rhuss] I get the spring-boot app restarting fine but fail to have it load classes that I'd expect to hot swap:
I run the camel spring-boot example as exploded jar. I am deploying the dependency as a jar to /deployments/BOOT-INF/lib as a jar initially.  
I then try to hot swap the dependency by replacing the dependency jar with an exploded version (I tried both variants, adding an exploded folder with a different name or then replacing the jar with an exploded folder that has the same name). Spring-Boot then detects the change, restarts the whole app but wont use the new classes in the dependency. It still runs the classes that it had from the jar. 

I have the classpath pointing to the following:

{code}
    -cp /deployments/BOOT-INF/classes/:/deployments/BOOT-INF/lib/*:/deployments/BOOT-INF/lib/:/deployments
{code}

I also have the following file in /deployments/BOOT-INF/classes/META-INF/spring-devtools.properties where I try to push project B into the restart classloader

{code}
    restart.include.dependency=/dependency-.*
{code}

Do you have any idea what I a missing so that I can hot swap classes in the dependency?

> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-25504
>                 URL: https://issues.jboss.org/browse/JBIDE-25504
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.5.2.AM2
>            Reporter: Jeff MAURY
>            Assignee: Andre Dietisheim
>              Labels: openshift, openshift_v3, server_adapter
>             Fix For: 4.5.3.Final
>
>         Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)