More Conventions with Maven.next--airhacks.fm podcast
Subscribe to airhacks.fm podcast via: RSS iTunes
An airhacks.fm conversation with Robert Scholte (@rfscholte) and Sebastian Daschner (@DaschnerS) about:
"Convention over Configuration and Maven, strategies for the "default", dependency versions to "apache" maven plugins, maven default behaviours, configuration hierarchies, Maven and CI/CD like Jenkins, command line options, pom elements, pom properties, the Java EE-stic approach to Maven, upgrading or downgrading, Maven and Java 11+, Maven.next features, effective POMs, accessing default versions of the plugins, making Maven configuration as lean as Java EE, Configuration by Exception, listing the current default plugin versions, specifying the versions in POM and overriding them with CLI and system properties."See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home: airhacks.io.
I am a relatively new Maven user and sorting out plugin versions was one of the biggest early challenges.
I agree that adding Maven plugin versions to the manifest in the jar or war is probably the best solution.
Since I am using Eclipse IDE with it's own Maven plugin, the manifest file revealed to me that my jars and wars were built with JDK 11.0.2 as expected; however, the Eclipse Maven was still version 3.5.3 and not 3.6.0 as I had expected.
So I was able to fix my Eclipse setup.
Thank you all for this podcast. It is really great to know this particular issue is an important issue for the developers because understanding all the plugin versions and how they work was a real challenge for me as a relative newcomer to Maven.
Posted by Don on March 16, 2019 at 07:44 PM CET #