|Re: [jakarta.ee-community] Jakarta Starter 1.0.0 Released!|
@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.
Edwin Derks wrote (ao):
> @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?
I'm simply using gradle myself, have nothing against maven (if that is even possible ;-) ).
Having choice is good, and if Jakarta EE supports gradle it would be nice to offer it on the starter page.
OpenLiberty supports gradle which works for me.
jakarta.ee-community mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
Back to the top