mkoncek

I don't think there is currently any need for that. Logging as it is currently is fine for me. For you, it would be probably lots of garbage information. In...

What do you mean? What would you be missing? Currently i am only sending compiler complaints to the JRD nothing more from my side. Here is an example of what...

Well, that is one part of the problem, the other is that in the most verbose mode, (in my case) I will get my process OOM-killed before than the compilation...

I think the JRD window which shows error messages was not meant to be flooded and behaves suboptimally. The memory consumption will rise at least about 1 GB.

Proposed property.

I did test the `module-info.class` file myself and indeed running `javap module-info.class` returned the text representation of that file, so the file itself is probably ok. Something must be wrong...

> Turns out that the jar tool processes the package attribute of a module-info when placing it in a jar and removes all packages that are not contained. This breaks...

Do you have an idea why this problem manifests with JDK 21? I can only think of natural code changes to the `jar` tool. I don't see any other reason...

With the backported changes to modulemaker and byte-buddy I was able to bootstrap Maven. I am not sure if the fix in modulemake is "clean" or rather a workaround but...

Ah right, shade plugin, i don't really know what it does, we always remove it from our packages before our builds. All I know is it renames class/package names.