Re: Multi-releases support in compiler plugin 4.0-beta-3

2025-03-24 Thread Romain Manni-Bucau
Hmm, I still think it is an abuse to think that, javadoc is a good example which, except the location, often override the rest of options. That said the point is more that if we go with generic groups of dependencies we should go with generic source sets and enable to attach them attributes, not a

Re: Multi-releases support in compiler plugin 4.0-beta-3

2025-03-24 Thread Romain Manni-Bucau
Hi Martin, Topic way older than this change - so really not blaming at all but this change makes it more obvious: any reason to move a plugin configuration from plugin to ? (concretely why do we go that way instead of dropping sources concept from build)? Romain Manni-Bucau @rmannibucau

Re: POC for improved DOT output for maven-dependency-plugin

2025-03-24 Thread Bear Giles
One of the benefits (to me) is that it makes mismatches in dependency versions stand out. I've been able to figure out how to rotate the graph yet keep it relatively (cough) narrow. There's still a few unwanted empty boxes but it now has nested groupIds. If you look carefully at the com.faster.jac

Re: Multi-releases support in compiler plugin 4.0-beta-3

2025-03-24 Thread Martin Desruisseaux
Le 2025-03-24 à 20 h 32, Romain Manni-Bucau a écrit : any reason to move a plugin configuration from plugin to ? (concretely why do we go that way instead of dropping sources concept from build)? Because that configuration is used by many plugins. The same information is needed by Javadoc pl

Multi-releases support in compiler plugin 4.0-beta-3

2025-03-24 Thread Martin Desruisseaux
Hello all A development branch of maven-compiler-plugin 4.0 can now support the property of the new element introduced in Maven 4. The creation of multi-release JAR files for non-modular projects should hopefully become easier (support for modular projects will be added later). Includes/excludes

Re: POC for improved DOT output for maven-dependency-plugin

2025-03-24 Thread Bear Giles
I should be clear - the glitch is the column of empty boxes above the root dependency. They should not appear. The grayed areas, with one exception, have the same groupId. If they also have the same version then the artifacts will be listed in a single stack. The 'type' is omitted if it's "jar", o

Re: POC for improved DOT output for maven-dependency-plugin

2025-03-24 Thread Elliotte Rusty Harold
I'm not sure I believe that the current dot layout is or should be a reliable part of the public API. if there's a better layout, use it. Unless maybe devs are somewhere consuming the .dot files themselves to understand the graph? I hope not, but you never know. On Mon, Mar 24, 2025 at 10:53 PM Be

Re: POC for improved DOT output for maven-dependency-plugin

2025-03-24 Thread Tomo Suzuki
That’s a beautiful diagram. Would you share the background you wanted to visualize it in that way? Did it get some tasks done? Regards, Tomo On Mon, Mar 24, 2025 at 19:02 Bear Giles wrote: > I should be clear - the glitch is the column of empty boxes above the root > dependency. They should not

Re: New Life Cycles Maven 4.0.0-rc3

2025-03-24 Thread Guillaume Nodet
Could you raise issues for the `all` phase not containing children subprojects, and eventually for a new `each` phase ? Le lun. 17 mars 2025 à 21:13, Karl Heinz Marbaise a écrit : > Hi, > > I'm trying to build a project with a number of subprojects.. > > I'm binding a plugin (just echoing) like