Le dim. 16 mars 2025 à 22:44, Mark Derricutt <m...@talios.com> a écrit :
> 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. > Yep, and I'm using idea but maven build doesn't just define dependencies. Concretely it means you have to use the command line to do anything, including running tests which is an impacting regression for end users. The fact the IDE parses surefire (and it is a simple example) breaks easily. It is the same for properties for ex. > > 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. > AFAIK it exists using extensions so if you have some concrete issues after v4 migration we can tackle them IMHO. Will be better than today but will not be worse. > > Mark > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree >
