Deploying Java apps on OpenShift E2E Lifecycle

on YouTube ↗15m

" summary

A VS Code extension pack bundles OpenShift Connector, a middleware adapter, Docker integration and the Java Debugger by Microsoft to go from code to running app without switching terminals. It starts WildFly/EAP locally, creates a component, builds a Maven tarball on save and pushes that artifact to an OpenShift cluster; logs and debug sessions stay inside the editor. The Java language support extension has 1.2M downloads, and the OpenShift Connector is live with OpenShift Connector and Java Debugger by Microsoft available.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 0:53Extension Pack
3. 1:18Why Do We Need an Extension Pack
4. 2:36What Is the Use Case To Have an Extension Pack
5. 4:29Open Shift Connector
6. 5:28Server Connector
7. 7:07Project Initializer
8. 8:39Debugger for Java
9. 8:52Maven Project Explorer
10. 11:31Create an Java Component

" related talks

• 33mDeveloping Java applications using Visual Studio CodeMartin Aeschlimann · Devoxx Belgium 2017
• 30mDeveloper Experience for OpenShift 4.x on AzureMohit Suman · DevConf.CZ 2020
• 31mDeveloping Java Apps using Visual Studio CodeGorkem Ercan, Fred Bricon · Devoxx US 2017
• 26mContainerize your Java Applications using Eclipse JKubeMarc Nuri · DevConf.CZ 2021
• 36mHacking Java and Spring Boot Applications with Visual Studio CodeJunyi Yi, Xiaokai He · Oracle Code One 2018
• 21mtalks about unlocking VSCode for JavaErik Weibust · Commit Your Code 2024
• 45mLive Coding: Spring Boot Applications with Visual Studio CodeSandra Ahlgrimm, Martin Lippert · JCON EUROPE 2024
• 01h 02mJava to Kubernetes for DummiesSun Tan · Devnexus 2023