So why does 1.0.25 report a class version of 50 rather than 49? Grizzly
1.9 has built with this version for a while now.
On 7/6/11 8:33 PM, Jane Young wrote:
> The artifacts were changed to 1.6 about 9 months ago (9/25/2010) in
> version 1.0.48. See:
> http://java.net/projects/hk2/sources/svn/revision/1708
> So 3.1 release has auto-depends built with 1.6 class files.
>
>
> On 7/6/11 3:43 PM, Justin Lee wrote:
>> Until recently those jars in the repo were built with 1.5. Now
>> they're 1.6 class files. So *something* changed somewhere. Grizzly
>> 1.9 hudson jobs that have built fine against 1.0.25 now fail due to
>> class file format incompatibilities.
>>
>> On 7/6/11 6:20 PM, Jane Young wrote:
>>> This has nothing to do with the recent maven repo migration.
>>>
>>> We have always been integrating HK2 promotions that include bug fixes
>>> and enhancements to GlassFish workspace. The
>>> com.sun.enterprise:auto-depends artifact is built from HK2 workspace.
>>> The version 1.0.25 was referenced in GF workspace a year ago.
>>>
>>> See:
>>> http://java.net/projects/glassfish/sources/svn/revision/37816 <--- this
>>> revision is when 1.0.25 was integrated in GF workspace
>>> http://java.net/projects/glassfish/sources/svn/revision/38199 <-- in
>>> this revision 1.0.26 was integrated
>>>
>>>
>>>
>>>
>>>
>>> On 7/6/11 12:54 PM, Justin Lee wrote:
>>>> With the recent maven repo migrations and such, was
>>>> auto-depends:1.0.25 rebuilt and redeployed? Because it's now built
>>>> with 1.6 where it used to be built with 1.5 and it's causing failures
>>>> when building grizzly 1.9 (which is restricted to 1.5 only). Any
>>>> ideas?
>>>
>