Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Jakarta Starter 1.0.0 Released!


The high level roadmap for the project is outlined here: A UI is indeed part of the plan, but I don’t know if it’s the highest priority given how long the starter gap has persisted now and the fact that all of us on the project contribute on our personal time. Also, this is another reason for you to go beyond simply providing feedback and consider code contribution.

That said, I do suspect from our current velocity that the currently identified roadmap items should be done by the end of this year at the latest, even without additional contributors. Certainly simply providing feedback is also a contribution.

Gradle support is not on the roadmap yet, but we could consider it. I do suspect though that it is likely the lowest priority of the identified work items so far That said, it would be a worthy issue to enter: Folks could at least vote on it that way and we could better gauge interest.

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

From: <> on behalf of Jeyvison Nascimento <jeynoronha@xxxxxxxxx>
Sent: Friday, April 8, 2022 4:59 AM
To: Jakarta EE community discussions <>
Subject: Re: [] Jakarta Starter 1.0.0 Released!
Hi @Huseyin,

The first approach we took was indeed to create an api with a UI that would allow the user to select different Jakarta EE exemples and download the project. It didn't go very far, as you can see here, as it was getting a bit complex and didn't have much support, so we decided , for now, to fallback to a simpler version It is our plan to go back to it in the future. Any further input is very welcome :)

Em sex., 8 de abr. de 2022 às 08:43, Huseyin Akdogan <hakdogan75@xxxxxxxxx> escreveu:
@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.

Hi Edwin,

I approach the subject from the point of view of beginners. Considering those with no have command-line usage experience or habits for project generation, I think it would be helpful to even just offer the ability to download the generated project will increase adoption. Though dependencies other than base JakartaEE dependency will not be presented.

Apart from these, I think that the UI is very important at the most basic level when presenting a tool/technology in terms of reaching users.

I don't want to be a breaker and belittle the hard work but the page is rather primitive compared to its counterparts, has no charm, no allure; sorry :(( 

Sander <accountseclipse@xxxxxxxxxxx>, 8 Nis 2022 Cum, 10:38 tarihinde şunu yazdı:
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.

[1]OpenLiberty supports gradle which works for me.


_______________________________________________ mailing list
To unsubscribe from this list, visit

Hüseyin Akdoğan
Expert Software Consultant
_______________________________________________ mailing list
To unsubscribe from this list, visit

Jeyvison Nascimento

Back to the top