I agree that dropping modello means using JAXB but it will likely be a transitive breaking change, ie drop xpp3 too and sadly XPP3 is part of the maven API and used a lot in extensions and mojo because it enables to programmatically handle the mojo configuration. I'd really be to move to an XSD first approach and generate the models (and implicitly readers/writers) with JAXB but it means keeping a bridge layer since I can't envision to break these usages which would make it really inconsistent. So overall even if I agree modello is not contribution friendly nor a friendly format, it is likely the least worse we can use as of today to make it smooth to end users in time IMHO.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le jeu. 3 juin 2021 à 07:27, Benjamin Marwell <[email protected]> a écrit : > > - For some time, JAXB has been bundled with the JRE. > > As of this writing, this still applies to Java 8. > > In Java 9, and 10, there's --add-modules=java.xml.bind. > > As of Java 11, it has been removed from the JDK. > > I'd consider that to be a migration problem. > > You can just include jaxb-api and jaxb-impl for any version of Java. > This will work and it won't even break Java 8. > > Am Mi., 2. Juni 2021 um 22:46 Uhr schrieb Jochen Wiedmann > <[email protected]>: > > > > On Wed, Jun 2, 2021 at 2:38 PM Gary Gregory <[email protected]> > wrote: > > > > > > On Wed, Jun 2, 2021 at 8:30 AM Jochen Wiedmann > > > <[email protected]> wrote: > > > > > > > > On Wed, Jun 2, 2021 at 1:02 PM Elliotte Rusty Harold < > [email protected]> wrote: > > > > > > > > > What do folks think about slowly moving away from Modello where > > > > > feasible to simplify the build? Does anyone find Modello a net > > > > > positive, especially in longterm maintenance, not just in initial > code > > > > > generation? > > > > > > > > To me, it sounds feasible to replace Modello with a Sax parser > > > > (reading), and a Sax > > > > event generator (writing), that take as input a bean class (either > > > > written manually, > > > > or generated by Modello, and do the serialization/deserialization. > > > > > > > > Would, most likely, not be a drop-in-replacement, but definitely a > medium-term > > > > solution. > > > > > > What about JAXB? > > > > In general, JAXB is an excellent technology. For use in Maven, I'd > > foresee a few gotchas: > > > > - For some time, JAXB has been bundled with the JRE. As of this > > writing, this still applies to Java 8. > > In Java 9, and 10, there's --add-modules=java.xml.bind. As of Java > > 11, it has > > been removed from the JDK. I wouldn't want to deal with that. > > - To use JAXB, one either needs to have an XSD, or rather specific > > annotations on the Java beans. > > I'd consider that to be a migration problem. > > > > Jochen > > > > > > -- > > > > Look, that's why there's rules, understand? So that you think before > > you break 'em. > > > > -- (Terry Pratchett, Thief of Time) > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
