I agree with a lot of what has been said towards keeping modello in use. There is really no existing drop-in alternative. The benefits of moving off Modello are mostly unknown until we actually do the work. And in the end it should be mostly internal refactoring.
However that work is a very large effort that is much better invested in the user facing improvements and new features. Manfred Robert Scholte wrote on 2021-06-02 11:54 (GMT -07:00): > The title suggest it should me moved completely from the Maven codebase, but I > think there's no alternative for Maven Core, as we need quite a huge set of > features. I don't think there's another tool that can keep the model, reader, > writers, mergers, validators and xsd in sync. If you want to replace it, start > with Maven core. If you succeed we can have another discussion otherwise we > will stick to Modello. We have enough committers that can maintain it. > > To me consistency is just as important, so it makes sense to have a preferred > library for reading/writing XML. As Maven Core already claims Modello, better > mark this as the preferred solution. > > Regarding Eclipse support, most likely Eclipse was the first IDE to support > Modello and it still does. If you open the pom you should see there are m2 > plugins available, including one for modello. Once installed and restarted, it > works as expected (just tested it). Like any IDE, in general you don't get all > the options but often pluguins are available. > > You rarely need to touch the mdo-files, but with the right documentation you > should be able to extend it. > But that is for any solution we would choose. We shouldn't maintain all Java > files and XSDs by hand, but generate it. And any generating tool will require > read that famous manual. > > Robert > On 2-6-2021 14:38:43, Gary Gregory <[email protected]> wrote: > On Wed, Jun 2, 2021 at 8:30 AM Jochen Wiedmann > wrote: >> >> On Wed, Jun 2, 2021 at 1:02 PM Elliotte Rusty Harold 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? > > Gary > >> >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
