Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse IDE Webinar 2022-12"
| Line 11: | Line 11: | ||
Please sign-up for presenting a talk, along with the topic (duration 15 mins each) and a short abstract (2-5 lines) | Please sign-up for presenting a talk, along with the topic (duration 15 mins each) and a short abstract (2-5 lines) | ||
| − | 1. | + | 1. Spring Tools for Eclipse: What's New - Martin Lippert |
| − | + | The latest release of the Spring Tools for Eclipse 2022-12 include some new features around making it easier for developers to stay up-to-date with the versions of Spring Boot that they are using. The combination of validating Spring Boot versions against the latest available releases as well as providing quick fixes to upgrade to the latest versions are a powerful combination. Especially when it comes to more than just changing the parent pom dependency by automating updates to source code, property files, and language constructs. This is particularly interesting when jumping to the just released Spring Boot 3 version, which requires you to switch to Java 17 and the new Jakarta EE packages - all automated via the tooling. | |
2. <Topic> - <Presenter> | 2. <Topic> - <Presenter> | ||
Revision as of 09:59, 15 December 2022
Eclipse IDE Webinars will be held to promote and create buzz around the Eclipse IDE and the latest 2022-12 (4.26) release.
Schedule
Date: January 25, 2023
Time: 3pm CET / 9am EST / 7.30pm IST
Duration: 60 mins
Topics
Please sign-up for presenting a talk, along with the topic (duration 15 mins each) and a short abstract (2-5 lines)
1. Spring Tools for Eclipse: What's New - Martin Lippert
The latest release of the Spring Tools for Eclipse 2022-12 include some new features around making it easier for developers to stay up-to-date with the versions of Spring Boot that they are using. The combination of validating Spring Boot versions against the latest available releases as well as providing quick fixes to upgrade to the latest versions are a powerful combination. Especially when it comes to more than just changing the parent pom dependency by automating updates to source code, property files, and language constructs. This is particularly interesting when jumping to the just released Spring Boot 3 version, which requires you to switch to Java 17 and the new Jakarta EE packages - all automated via the tooling.
2. <Topic> - <Presenter>
<Abstract>
3. <Topic> - <Presenter>
<Abstract>
4. <Topic> - <Presenter>
<Abstract>