Many thanks, Mike
On Jul 6, 2006, at 5:24 PM, Mike Schrag wrote:
> It's not hard, it's just tedious ... I unjar'ed everything and ran
> the file command on all the classes looking for 49.0 version numbers.
>
> So the build server was running:
>
> [echo] * java.home = /System/Library/Frameworks/
> JavaVM.framework/Versions/1.5.0/Home
> [echo] * build.compiler = javac1.4
>
> It was telling it to use 1.4, but it was building with a 1.5 VM. I
> would honestly expect this to work properly, but I'm going to set
> java.home to be 1.4 and force it to build with the 1.4 VM and
> libs. It's executing now. I'll check the woproject.jar when it's
> done and let everyone know when it's 1.4-clean.
>
> ms
>
> On Jul 6, 2006, at 5:15 PM, Pierre Frisch wrote:
>
>> Is there an easy way to test this? i.e. is there a way of checking
>> the ClassVersion of a build jar?
>>
>> Pierre
>>
>> On 6-Jul-06, at 1:14 PM, Ken Anderson wrote:
>>
>>> Mike,
>>>
>>> Considering my recent post - I think that is likely. I do not
>>> have 1.5 on my machine at all...
>>>
>>> Ken
>>>
>>> On Jul 6, 2006, at 1:04 PM, Mike Schrag wrote:
>>>
>>>> So if you're seeing a ClassVersionError launching inside
>>>> Eclipse, then there's a 99% chance that you are building your
>>>> app with 1.5, but your launch configuration is using a 1.4 VM to
>>>> run it with. If you're seeing it in deployment, then there's a
>>>> 99% chance that you built with 1.5 but your deployment
>>>> environment either 1) doesn't have 1.5, 2) has 1.5 but it isn't
>>>> the default, 3) you explicitly run it with 1.4 in your launch
>>>> script.
>>>>
>>>> When you mention that you can't even build wolips -- Can you
>>>> give some more info? What actually is failing (including the
>>>> name of the class it tried to load that gave you the
>>>> ClassVersionError). There are a couple prebuilt jars inside of
>>>> wolips, so it's possible one of those accidentally got built
>>>> with 1.5 along the way (for instance, I recently upgraded
>>>> cayenne to support EOModeler plugin).
>>>>
>>>> ms
>>>>
>>>> On Jul 6, 2006, at 12:27 PM, Pierre Frisch wrote:
>>>>
>>>>> I am a bit mystified. I installed eclipse 3.2 release with the
>>>>> latest WOLips and I am running Java 1.5 as the default jvm and
>>>>> I still see the errors. I cannot even build wolips which I
>>>>> could with eclipse 3.2RC7 and wolips 149 and jvm 1.5.
>>>>>
>>>>> Pierre
>>>>>
>>>>> On 6-Jul-06, at 7:57 AM, Mike Schrag wrote:
>>>>>
>>>>>> You're correct -- I misinterpreted what he was seeing ... One
>>>>>> less thing I need to do, that's nice :)
>>>>>>
>>>>>> ms
>>>>>>
>>>>>> On Jul 6, 2006, at 5:36 AM, Ulrich Köster wrote:
>>>>>>
>>>>>>> I thought mike is talking about "our" buildserver where we
>>>>>>> build the releases of woproject and wolips. woproject and
>>>>>>> wolips are build with ant for java 1.4.
>>>>>>>
>>>>>>> Mike has to do nothing because the buildscripts are fine. For
>>>>>>> instance Mike added some stuff lately that was 1.5 only. We
>>>>>>> recognized that immediately because the build failed.
>>>>>>>
>>>>>>> Marc has to adjust his build to make sure that it builds for
>>>>>>> 1.4.
>>>>>>>
>>>>>>> Please correct me if I'm wrong.
>>>>>>>
>>>>>>> Uli
>>>>>>> Am 06.07.2006 um 10:44 schrieb Anjo Krank:
>>>>>>>
>>>>>>>> This is not a solution for those that want to build on a
>>>>>>>> machine where 1.4 is the default, and as long as WO isn't
>>>>>>>> qualified for 1.5, there will be quite a few of those...
>>>>>>>>
>>>>>>>> Cheers, Anjo
>>>>>>>>
>>>>>>>> Am 06.07.2006 um 10:40 schrieb Ulrich Köster:
>>>>>>>>
>>>>>>>>> Moin Mike,
>>>>>>>>>
>>>>>>>>> no need to change anything on the buildserver. Marc
>>>>>>>>> switched to 1.5.
>>>>>>>>>
>>>>>>>>> Uli
>>>>>>>>> Am 06.07.2006 um 03:49 schrieb Mike Schrag:
>>>>>>>>>
>>>>>>>>>> The build server probably got updated to Java 1.5 which
>>>>>>>>>> would have changed the default VM mapping ... WOLips
>>>>>>>>>> should be 1.4 compliant for everything. I'll have to take
>>>>>>>>>> a look at it tomorrow morning and set the VM to 1.4
>>>>>>>>>> explicitly.
>>>>>>>>>>
>>>>>>>>>> ms
>>>>>>>>>>
>>>>>>>>>> On Jul 5, 2006, at 9:00 PM, Marc Respass wrote:
>>>>>>>>>>
>>>>>>>>>>> FWIW, I still have woproject from 2.0.0.115 and that
>>>>>>>>>>> works. I would like to know if there's a Java 5
>>>>>>>>>>> requirement and, if so, is it ok to stick with 2.0.0.115
>>>>>>>>>>> or is there a later version that runs in Java 1.4 that I
>>>>>>>>>>> should get?
>>>>>>>>>>>
>>>>>>>>>>> Thanks a lot
>>>>>>>>>>> Marc
>>>>>>>>>>>
>>>>>>>>>>> On Jul 5, 2006, at 8:55 PM, Marc Respass wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> Is there some Java 5 requirement going on? My server is
>>>>>>>>>>>> running Mac OS X 10.4.x and Java 1.4.2_09. I copied up
>>>>>>>>>>>> the latest woproject.jar and now when I compile I get
>>>>>>>>>>>> the following error
>>>>>>>>>>>>
>>>>>>>>>>>> java.lang.UnsupportedClassVersionError: gov/maine/oit/
>>>>>>>>>>>> mfasis/wo/Application (Unsupported major.minor version
>>>>>>>>>>>> 49.0)
>>>>>>>>>>>>
>>>>>>>>>>>> I modified ant to use Java 5 and it compiled fine but
>>>>>>>>>>>> now my app does run (same error) because I'm using Java 1.4
>>>>>>>>>>>>
>>>>>>>>>>>> Since WebObjects does no support Java 5, I am sticking
>>>>>>>>>>>> with 1.4 for deployment. My workstation runs Java 5 but
>>>>>>>>>>>> Eclipse compiles using 1.4.
>>>>>>>>>>>>
>>>>>>>>>>>> Marc
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Thu Jul 06 2006 - 17:27:42 EDT