Re: Rewrite of JAR plugin ready for merge

Romain Manni-Bucau <[email protected]>
Newsgroups gmane.comp.jakarta.turbine.maven.devel
Message-ID <CACLE=7PzSbFBvOsOY3CopQoJ10X3A5f0a29w06=rSeDZwoxCVg@mail.gmail.com>
Le jeu. 27 août 2026 à 00:30, Martin Desruisseaux via dev <
[email protected]> a écrit :

> Le 26/08/2026 à 23:49, Romain Manni-Bucau a écrit :
>
> > not sure about the debugging
>
> When the build fails, or when Maven was run with the -X argument, the
> plugin generate a `jar.args` for allowing users to test from the command
> line as below:
>
>     jar @target/jar.args
>
> They can edit manually the `jar.args` file until the figured out what
> was causing the problem, then modify their pom.xml accordingly. This is
> made possible by the fact that the plugin now delegates to the jar tool,
> so the plugin can easily write down the arguments that it used.
>

This only helps cause it moved to jar, using a plain plugin as before
wouldn't mean much so not sure it helps and debugging is as easy in both
cases so just a feature from my window but I get your point now, thanks.


>
>
> > multimodules can be handled with previous code so not sure the issue
>
> I'm talking about Java modules, not Maven modules (now named
> "sub-projects"). Multi-modules as managed by javac, not Maven, has never
> been supported by Maven. The javac multi-module support has advantages
> impossible to reproduce with Maven, such has detecting broken references
> to dependents (not dependencies). They appear in qualified exports,
> qualified opens and Javadoc among others, and are related to the
> --hash-modules option mentioned previously.
>

Still you need to define how you do deploy that (can't be a single jar but
a subproject should stay a single jar) so you will need some maven work
there and yes it is already doable even if it looks hacky so I don't think
we should think we just need to wrap java tools but we should think maven
first there IMHO, the rush will just bring inconsistencies and miss the
target like the hsah module which should be usable inter maven
modules/subprojects to keep a clean deployment model and standardized IDE
support (while exception for mjar to have a few classes not in a module is
okish, it is less for modules which are full libs IMHO).


>
>      Martin
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.