Markus KARG

If you feel uncomfortable with suppressed warnings, feel free to provide a PR that resolves the underlying problem.

> Thank you for your contribution! ❤️ > > Actually there is no issue #567, hence I would kindly ask you to refer to the actuall reported problem that your...

Feel free to contribute a PR including a test, but note that we must stay backwards compatible unless we move on to jCommander 2.x. OTOH I think we could safely...

@ekpdt Elan, still looking forward to receive your PR. Still working on it?

+1 for finer grained feature separation and more profiles collecting them for typical usage scenarios

I thnk profile solve one more developer problem: It is rather comfortable and safe. If you are a Jakarta EE charter, there are lots of APIs to understand, with possibly...

@bshannon Yes, docs and tutorials are a help. But on the other hand, it might be a good idea to have Java SE profiles to clearly separate the topics. When...

This sounds like if Java SE would be monolithic, but in fact it already _has_ profiles: https://www.oracle.com/technetwork/java/embedded/resources/tech/compact-profiles-overview-2157132.html.

Let's forget the word "profiles" and let's call these collections of APIs "profile modules" or something like that. Java SE has them, and we could use them in Jakarta EE....

@kazumura I completely do not understand this argument. Can you please explain it a bit more elaborate? In particular the stuff about branding and why we cannot compare SE and...