| 
  
  
     Will the existing JIRA issues be considered for the next release
      or do we have to make sure to re-engage? 
     
    On 7/16/2018 10:41 AM, Kevin Sutter
      wrote: 
     
    
      
      Hello Cheng, 
      We are interested in continuing
        with
        Java Batch in the Jakarta EE space.  I've been talking with our
        spec
        lead here at IBM and we're working through the details.
         Currently,
        Java Batch is maintained in github under Apache v2 license.
         Here's
        a pointer to the project's wiki:  https://github.com/WASdev/standards.jsr352.batch-spec/wiki. 
       
        --------------------------------------------------- 
        Kevin Sutter  
        STSM, MicroProfile and Java EE architect 
        e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter 
        phone: tl-553-3620 (office), 507-253-3620 (office)     
        LinkedIn: https://www.linkedin.com/in/kevinwsutter 
       
       
       
      From:      
         Cheng Fang
        <cfang@xxxxxxxxxx> 
      To:      
         jakarta.ee-community@xxxxxxxxxxx 
      Date:      
         07/15/2018 10:31 PM 
      Subject:    
           [jakarta.ee-community]
        Plan for Batch Spec (JSR 352) in Jakarta EE 
      Sent by:    
           jakarta.ee-community-bounces@xxxxxxxxxxx 
      
  
       
       
      Since the Batch Spec (JSR
            352) was first
        introduced in
        Java EE 7, it has been well received by the community and
        greatly helped
        standardize modern batch processing applications.  There was
        plan
        to include a next release of batch spec into Java EE 8, but
        unfortunately
        was left out.  Now under the new Jakarta EE umbrella, what is
        the
        plan for batch spec? 
       
      I would love to see continued
        support for
        batch spec in Jakarta EE, as well as further evolution of the
        spec to add
        more features.  Some important features (e.g., job definition
        inheritance,
        etc) had to be deferred to batch.next at the last minute of
        batch spec
        1.0.  So it would be nice to carry forward these deferred tasks. 
       
      What do you think about batch.next
        in Jakarta
        EE?  I appreciate your thoughts and comments. 
       
      Thank you, 
      Cheng_______________________________________________ 
          jakarta.ee-community mailing list 
          jakarta.ee-community@xxxxxxxxxxx 
          To change your delivery options, retrieve your password, or
          unsubscribe
          from this list, visit 
        https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community 
         
       
       
       
      
       
      _______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
 
     
     
  
 |