Hi all,
It's great to see such a page come up for the Jakarta EE community. I have some thoughts on what has been said here.
@Huseyin I can understand your reaction, but what kind of explicit features would you like to see for Jakarta EE in such an enriched UI? The fact that you only need one Jakarta EE maven dependency to access the whole Jakarta EE platform, kind of lowers the need for such an interface. I agree that in contrast to Quarkus and Spring, where you have component-based frameworks where you need to pick and choose your components.
@Sander Maven is still the standard way of building Jakarta EE applications. I have heard people say that Maven is too "limited" and too "rigid" for their applications. I'm genuinely curious as to what kind of applications people are developing where Maven as a build tool is "limiting". In this context, what features would Gradle bring to the table that would improve building Jakarta EE applications?
Hope this helps and I'm open to suggestions and discussion since I'm also a fan of improving the Jakarta EE ecosystem :)
Edwin
