Marcono1234

That might indeed be a better solution. Can there be cases though were a parameter has a different default value, which is not set with `@Parameter(defaultValue = "...")`? For example,...

> doc should be aware of it somehow, either ensuring we inject the default for primitives in plugin.xml or let the doc handle it IMHO But how do you propose...

> The inline init case is not supposed to work But does it work currently, and are plugins relying on this? Because if Maven Plugin Plugin is changed to pick...

@rmannibucau, I had a look at this again, but I still don't see how Maven Plugin Plugin or similar could be enhanced to infer the default value. And suddenly determining...

@slachiewicz, would you mind merging these changes? These changes hopefully help users _now_ (respectively the next Shade Plugin release), whereas some general Maven Plugin Plugin changes (in case they are...

Not completely sure, but has this been resolved by #501? Though based on https://github.com/actions/setup-java/pull/501#discussion_r1803652563 I am not sure if those GraalVM versions 17/21/22 will always be available, or if they...

Should this be closed, given that #403 has been merged?

Maybe this really mostly affects Eclipse (where the user test class name does not seem to be shown), and not that much IntelliJ or Maven. So I could understand if...

> it was pretty common to decorate suites to capture the class names at each nested level for debuggability Thanks, yes that is what I was thinking of as workaround,...

There might be a misunderstanding here, `com.google.gson.annotations` is part of the regular Gson JAR. So bnd generates both an `Export-Package` and an `Import-Package` entry for it[^1]. And the `Export-Package` does...