Community
Participate
Working Groups
See bug 136146. When a JRE container is bound to an execution environment (new in 3.2), the 3.1.x tooling will not be able to correctly resolve a JRE. If a team uses mixed development environments (i.e. a mix of 3.1 and 3.2 clients) to develop the same Java project, there could be problems here. We can provide a fix to 3.1.x to allow the tooling to be compatible.
With the recent fix to bug 136146, the 3.2 EE format is compatible with 3.1 without changes to 3.1. However, we need to remove the transient EE formats that will not be supported in 3.2. We will only support formats of: seg 0: JRE_CONTAINER id seg 1: vm type id seg 2+: vm name / ee id
Moving to RC3. RC2 will support all formats.
Pinging Jeff for RC3 approval.
Moving to RC4.
Yes, +1 for RC3 but Darin has gratiously agreed to defer the actual removal to RC4 to smooth the transition for the teams who may have been a bit eager on the use of EEs. This code should be removed immediately after RC3. thanks for your patience Darin!
Risk: The risk of this fix is low. Any components that updated their classpath when the transient formats were in place will need to update their classpaths again. CC'ing Philippe for additional approval.
+1 for 3.2RC4
+1 again
Created attachment 40822 [details] patch
Please verify patch, Kevin.
patch looks good.
Fixed.
Please verify, Mike.
verified
