On branch edburns-msft-1410-arquillian-version Update arquillian version.

[edburns]

… See jakartaee/platform-tck#1410

modified: com.ibm.jbatch.tck.ann.proc/pom.xml
modified: com.ibm.jbatch.tck.ann/pom.xml
modified: com.ibm.jbatch.tck.appbean/pom.xml
modified: com.ibm.jbatch.tck.exec/pom.xml
modified: com.ibm.jbatch.tck.sigtest.exec/pom.xml
modified: com.ibm.jbatch.tck.spi/pom.xml
modified: com.ibm.jbatch.tck/pom.xml
modified: jakarta.batch.arquillian.exec-parent/pom.xml
modified: jakarta.batch.arquillian.exec/pom.xml
modified: jakarta.batch.arquillian.extension/pom.xml
modified: jakarta.batch.official.tck/pom.xml
modified: jakarta.batch.reporting/pom.xml
modified: jakarta.batch.tck.util/pom.xml
modified: pom.xml

[scottkurz]

Thanks for the PR.

The latest release is 2.1.5, so the 2.2.0-SNAPSHOT is I think fine to stay with.

[liweinan]

In addition, there may be more configuration changes that need to be done for the upgrade. Here are some PRs for reference:

• [RESTEASY-3518] Upgrade Arquillian Core to 1.9.1.Final, Arquillian Ja… by jamezp · Pull Request #4240 · resteasy/resteasy
• Upgrade Arquillian Core to 1.9.1.Final by liweinan · Pull Request #337 · resteasy/resteasy-spring

[scottkurz]

In addition, there may be more configuration changes that need to be done for the upgrade. Here are some PRs for reference:

I didn't see anything we obviously need from those PRs @liweinan. It looked mostly like POM imports. Feel free to suggest additional commits or changes but if it seems to work with the current PR, I'd guess we might be able to stop there.

[liweinan]

@scottkurz Okay!

We've met some dep chain problems during the work on the PRs pasted above(For example, some shrinkwrap poms were added after this upgrade). If all the tests are passed here there is no problem.

[scottkurz]

@edburns this change seems to work, I tested it.

I sent you a PR azure-javaee#1 if you want to merge it to revert the version update. Or I could just make the change.

Thanks