modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar The jar name is not consistent with EAP jar files naming. It should contain substring "version-redhat-XY"
Assigning to Stuart since he added this jar with the unversioned filename.
I think we need to know: Stuart: - can it be renamed to follow -redhat-XX naming without any problem in integration == code doesn't contain hardcoded file name Paul: - is it built from sources when is EAP productized or is it downloaded from somewhere I really want to have it renamed with -redhat-XX convention to stay consistent with the rest of jar files in EAP zip. We need to know if that is possible without any impact.
Yes, it is built from sources with the resteasy project. The version downloaded during the build is the same as the other resteasy jars.
This jar is referenced directly from the integration code, which is why the version was removed to allow the code to work no matter what version is in use. I will have a look and see if it is easy to make it work with a version.
Upstream change is here: https://issues.jboss.org/browse/WFLY-3366 Note that there is a risk associated with this, as tests for this feature were never added to the EAP6 code base, instead there is a test that lives in an old Resteasy branch that is not run by default.
Hi Stuart, This change breaks the RPM case where the symlinks are unversioned (so that the destination can be upgraded). We can easily revert the change to build/build.xml when we prepare the ZIP for the RPMs but the name of the JAR is hardcoded in org/jboss/as/jaxrs/deployment/JaxrsSpringProcessor.java We'd need a small change there for it to look for the unversioned name if, for instance, the property resteasy.version is not set. We could remove from the RPM distro the file org/jboss/as/jaxrs/spring-version.properties to get that property unset. We cannot just do that now because a '-' will be added at the end always. Best regards, Fernando
A test as per https://bugzilla.redhat.com/show_bug.cgi?id=1090053#c5 should help guard against problems in the future
Verified with EAP 6.3.0.ER7.
https://github.com/jbossas/jboss-eap/pull/1428 does this better, moving back to MODIFIED for ER9 on Fernando's request
PR 1428 causes the regression in https://bugzilla.redhat.com/show_bug.cgi?id=1117245, for which https://github.com/jbossas/jboss-eap/pull/1504 has been created.
Postponed to ER10 due to regression found https://bugzilla.redhat.com/show_bug.cgi?id=1117245.
Verified in EAP 6.3.0.ER10.