Folks,
The high level roadmap for the project is outlined here:
https://github.com/eclipse-ee4j/starter#roadmap. 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:
https://github.com/eclipse-ee4j/starter/issues. Folks could at least vote on it that way and we could better gauge interest.
Cheers,
Reza RahmanJakarta 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.
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
https://github.com/eclipse-ee4j/starter/tree/archive, 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 :)
