I do think we have something available for folks that really need it. Luis can comment.
To be transparent though, specification discussions typically often don’t have implementations right away. I think that’s the norm rather than the exception, certainly for Java EE if not Jakarta EE. On Mar 12, 2026, at 5:04 PM, lenny@xxxxxxxxxxxxx wrote:
Hi,
At this point, I think it’s would be very difficult to have any useful feedback without having running code available. IMHO the best way to do this is to have a publicly-accessible artifacts on an open nexus instance. On Mar 11, 2026, at 7:22 PM, Reza Rahman via agentic-ai-dev <agentic-ai-dev@xxxxxxxxxxx> wrote:
Hi folks,
Our next order of consensus is the current API proposal. The API actually contains detailed embedded Javadoc that defines quite a bit of the specification behavior already.
However, before starting the API review, it’s important that you actually review the broader context that is already available. So, can I kindly ask you to review the following over this week and next week?
Do you mind replying here with any follow up thoughts after you review the above? I’ll split into separate threads if necessary to keep discussion focused on specific areas. If everything looks good, especially from a v1 perspective, briefly indicating that is helpful as well. I know at least some folks are well familiar with the material already. After the discussion of the context winds down, I’ll attempt to start an actual API review thread hopefully followed by a vote to record committer consensus.
Onward!
Thanks, Reza _______________________________________________ agentic-ai-dev mailing list agentic-ai-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://accounts.eclipse.org
|