Joe, First and foremost, thank you so much for doing this work.
It's more than jars ending up in their respective modules. You then use the assembly plugin to gather them in src and bin zips and tars. The sources and resources need to move as well, each to their respective module. I don't think we want to end up with a half-way Maven build full of odd configurations of plugins because we've left the file layout in the Ant style (not that there is one). One of the benefits of Maven is "Configuration by exception" where you only need to configure a plugin if you want non-default behavior. Gary On Sun, Sep 3, 2023, 12:31 PM Joseph Kessselman <kesh...@alum.mit.edu> wrote: > It looks like what Maven wants, in order to separate serializer from > xalan, is to separate them into subfolders each having their own pom.xml > files, and then have a "parent" pom.xml at the top level which builds > those contained projects. > > This does leave the jarfiles in new locations, unless we postprocess to > copy them to where they've been in the past. (Then again, maven is > already outputting to target/ rather than build/, so this is not a new > issue.) > > Having to move things around is a bit annoying, in terms of minimizing > the changes introduced by the mvn cut-over; it would seem to prevent > having a single project that can be built both via the old ant build.xml > and the new maven pom.xml's, or that can be easily diff'd against prior > versions. I find myself unreasonably reluctant to do that. However, if a > better answer doesn't exist... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org > For additional commands, e-mail: dev-h...@xalan.apache.org > >
