| Re: [jakartabatch-dev] Old Java Batch issues from java.net reopened in github eclipse-ee4j/batch-api |
The two big ticket changes I see are:
* Aligning Jakarta Batch to take better advantage of CDI.
* Add a Java configuration API as an alternative to XML.
My feeling is that both issues are relatively well understood but
have not really been discussed or analyzed in detail just yet. Is
that a fair take? I see the CDI alignment items come up a few
times in the issues but no mention of the Java configuration API
somehow. Is it worth it to make sure both of these items are
(more) prominently represented in the issues somehow?
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.
Hi,Some of you may have noticed that I opened a bunch of issues in the java batch project. These are all issues that were still open in bugzilla for the JSR-352 project. You can find all of them by searching for the former-bugzilla-issue label (thanks Scott). Or use this link:We've brought over the comments and discussion in a hopefully mostly readable format.Let the discussion (re)commence!(btw, Scott and I have kicked around the idea of putting some other labels on these to assign them to categories of some sort...if anybody has any good ideas for what would make useful categories :-)
_______________________________________________ jakartabatch-dev mailing list jakartabatch-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev