Thanks to Snjezana for looking in to this and explaining what's going on.
The reason why bean-validator, version 4.0.0.Alpha3 is getting included
is because of hk2 dependency.
The hk2 artifact has a dependency on the older version of bean-validator
therefore the artfiact is included in the following packages:
glassfish-hk2 and glassfish-scripting (transitive dependency). The
package glassfish-nucleus includes the correct bean-validator version,
3.0-JBoss-4.0.0.Alpha3-b01. The non-IPS distribution uses "unzip" to
extract the packages. The first package that gets unzip takes
precedences and that happens to be glassfish-nucleus.
On the other hand, the IPS distribution uses pkg tool to install the
packages. The last package, glassfish-scripting take precedences thus
overriding the correct version of bean-validator artifact.
The fix is to correct the version for bean-validator in hk2.
Nandini, can you fix this?
Thanks,
Jane
Ed Burns wrote:
> Jane Young and I are working this issue. Nandini Extare brought to my
> attention that the weekly and promoted builds are including the wrong
> version of bean-validator.jar. The version they are including is
> <http://download.java.net/maven/2/org/glassfish/extras/bean-validator/4.0.0.Alpha3/bean-validator-4.0.0.Alpha3.jar>.
> The version they should be including is
> <http://download.java.net/maven/2/org/glassfish/bean-validator/3.0-JBoss-4.0.0.Alpha3-b01/bean-validator-3.0-JBoss-4.0.0.Alpha3-b01.jar>.
>
> To get around this, replace the modules/bean-validator.jar that you get
> in the promoted build with the correct one.
>
> Thanks, and we apologize for the inconvenience.
>
> Ed
>
>