[
https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-25504:
------------------------------------------
We decided to deploy to the dependency (-ies) to */deploments/BOOT-INF/classes* and live
with the possibility of possible name clashes where the dependency would overwrite the
main project.
[~jeffmaury] The current impl in the PR does exactly that. What's now unclear to me is
whether the wizard should configure the deployment assembly fully automatically. [~rawb]
thinks that this is a bad idea. We should at most (even not sure if we should) inform in
the wizard that there's a dependency to the main project in the workspace and that
configuring the deployment assembly is required for it to get deployed.
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)