I don't think tiles can be implemented just using a parser. The ModelParser SPI provides a way to read a file into an existing *file* model, but it does not handle parent hierarchy merging, profiles injection, property substitution, etc... All those things are done by the ModelBuilder which delegates to the default model reader or the ModelParser SPI.
For mixins (as I implemented a while ago in my POC), the model builder needs to be changed. That piece is particularly complex and hard to extend. Of course, it could be copied / enhanced, but the maintenance would be a nightmare. In addition, the ModelParser is currently used very early in the process and is not given a Session which could be used to actually download the tiles/mixins. I'll try to rewrite the POC on top of rc-3 asap. Le lun. 17 mars 2025 à 08:02, Christoph Läubrich <m...@laeubi-soft.de> a écrit : > >> And it just breaks all editors and IDE out there except the almost no > >> more used netbeans ;) > > > > Does it? > > At least m2e should work with tiles extension (basically with any > extension). > > > One option/alternative I had been contemplating was making the tiles > > plugin take the list of “tiles poms” and generate a realised/composed > > pom as a fixed parent. > > This is exactly like the modelreader in maven 4 (previous polyglot > extension) works, you can supply a file in an alternative format e.g. > assume its called pom.tiles but even an xml with a different namespace > should work and then you have to supply an (in memory) 'classic' model > to maven see here: > > > https://github.com/apache/maven/blob/master/compat/maven-model-builder/src/main/java/org/apache/maven/model/io/ModelReader.java > > in such a custom file format you can do whatever you want. > > Lets assume you do it that way and use an extended maven xsd for that it > would probably be easier to discuss how/if this could be part of maven > core as one can see what changes it really pulls in and what benefits it > brings. > > Am 16.03.25 um 22:44 schrieb Mark Derricutt: > > On 17 Mar 2025 at 3:04:31 AM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> And it just breaks all editors and IDE out there except the almost no > more > >> used netbeans ;) > >> > > > > Does it? I guess that depends on how you use your IDE. IntelliJ still > > resolves dependencies fine, and that’s all I care about— anything > > maven/build/release I do at the command line. > > > > If one were to use tiles to include dependencies (which are considered > > small and need to be enabled - I wish we’d never added support for that, > > though it can be handy), IDEs can get confused, especially those that > run a > > single instance of Maven for the lifetime of the IDE. However, I find > that > > sometimes this causes problems regardless of using tiles. > > > > One option/alternative I had been contemplating was making the tiles > plugin > > take the list of “tiles poms” and generate a realised/composed pom as a > > fixed parent. > > > > That would solve a bunch of things as it would just be > > > > a) generation of blended/decomposed XML > > b) a released parent pom in your nexus/local repository > > > > To work effectively with Maven, it may be beneficial to utilize its APIs > to > > modify and create an “effective parent” during the build process. > > > > Mark > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ------------------------ Guillaume Nodet
