[jboss-jira] [JBoss JIRA] (WFLY-9314) Upgrade JBeret to 1.2.5.Final

[Cheng Fang (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460759#comment-13460759 ] 

Cheng Fang edited comment on WFLY-9314 at 9/8/17 7:44 AM:
----------------------------------------------------------

the best way to stay current is to use latest WildFly releases, which includes the latest stable jberet-core module.  If you want to drop in a more recent version of jberet-core into your WildFly installation, you are doing it at your own risk, and it may or may not work as expected, depending on the versions of WildFly and JBeret. There are some structural or spi changes in various versions of WildFly and JBeret that are incompatible with previous versions.

For developers, you can look at the commits between 2 JBeret versions and decide if a newer jberet-core may work.

https://github.com/jberet/jsr352/commits/1.2.x?before=53335ea19993adf220fd6d68f068106f77787751+35

For instance, JBeret 1.2.2 work spans from 6/26/2016 to 12/13/2016, and includes some api changes, so I don't think 1.2.2 will work with WildFly 10.1.

WildFly 11 currently contains jberet-core 1.2.4.Final, and replacing it with jberet-core 1.2.5.Final should just work as well.

Currently there is no plan to upgrade jberet-core in WildFly 11.


was (Author: cfang):
the best way to stay current is to use latest WildFly releases, which includes the latest stable jberet-core module.  If you want to drop in a more recent version of jberet-core into your WildFly installation, you are doing it at your own risk, and it may or may not work as expected, depending on the versions of WildFly and JBeret. There are some structural or spi changes in various versions of WildFly and JBeret that are incompatible with previous versions.

For developers, you can look at the commits between 2 JBeret versions and decide if a newer jberet-core may work.

https://github.com/jberet/jsr352/commits/1.2.x?before=53335ea19993adf220fd6d68f068106f77787751+35

For instance, JBeret 1.2.2 work spans from 6/26/2016 to 12/13/2016, and includes some api changes, so I don't think 1.2.2 will work with WildFly 10.1.

> Upgrade JBeret to 1.2.5.Final
> -----------------------------
>
>                 Key: WFLY-9314
>                 URL: https://issues.jboss.org/browse/WFLY-9314
>             Project: WildFly
>          Issue Type: Component Upgrade
>          Components: Batch
>            Reporter: Leandro Kersting de Freitas
>            Assignee: Cheng Fang
>             Fix For: 11.0.0.Final
>
>
> https://issues.jboss.org/projects/JBERET/versions/12335093



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)