dev@glassfish.java.net

Re: auto-depends artifact

From: Justin Lee <justin.d.lee_at_oracle.com>
Date: Thu, 07 Jul 2011 13:39:36 -0400

So why is it failing now? That's my question.

On 7/7/11 1:39 PM, Jane Young wrote:
> 1.0.25 artifact didn't get rebuilt/redeployed.
> See timestamp:
> http://download.java.net/maven/glassfish/com/sun/enterprise/auto-depends/1.0.25
>
> It maybe something else in Grizzly...
>
>
> On 7/7/11 10:35 AM, Justin Lee wrote:
>> Because we've been using 1.0.25 for months in the 1.9 build and it's
>> been working. but recently it's started dying because of those 1.6
>> class files in the jar.
>>
>> On 7/7/11 1:28 PM, Jane Young wrote:
>>> Only classes in org/glassfish/hk2/classmodel/reflect are built with
>>> version 50. It's been there since this package was introduced in
>>> auto-depends.jar
>>> See: http://java.net/projects/hk2/sources/svn/revision/1410
>>>
>>> Why is this an issue in 1.0.25 ?
>>>
>>>
>>>
>>>
>>> On 7/7/11 5:41 AM, Justin Lee wrote:
>>>> mkdir ad
>>>> cd ad
>>>> jar xf ~/.m2/repository/.../auto-depends.jar
>>>> find . -name *.class | xargs file | grep 1.6
>>>>
>>>> On 7/7/11 2:02 AM, Jane Young wrote:
>>>>> Downloaded auto-depends:1.0.25 from
>>>>> http://download.java.net/maven/glassfish/com/sun/enterprise/auto-depends/1.0.25/
>>>>> and ran javap:
>>>>>
>>>>> $ javap -verbose -classpath
>>>>> /export/GlassFish/auto-depends-1.0.25.jar
>>>>> org.jvnet.hk2.component.Habitat | grep "major version"
>>>>> * major version: 49*
>>>>>
>>>>>
>>>>>
>>>>> On 7/6/11 6:17 PM, Justin Lee wrote:
>>>>>> 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?
>>>>>>>>>
>>>>>>>
>>>>>
>>>
>