Re: malformed bundle version number in deployment with Java 1.6
Re: malformed bundle version number in deployment with Java 1.6
- Subject: Re: malformed bundle version number in deployment with Java 1.6
- From: David Holt <email@hidden>
- Date: Thu, 06 Jun 2013 15:37:00 -0700
Hi Johann
Thanks for that. It turns out that it IS related to the java class.
JavaMonitor is starting the app in Java 1.5.
The command line is using Java 1.6
Does anyone know why there might be a discrepancy here?
On 2013-06-06, at 12:28 PM, Johann Werner <email@hidden> wrote:
> Hi David,
>
> I vaguely remember that that warning does not necessarily mean the Java version number of your jars is wrong but the cfBundleVersion of the framework is not parseable (I think its in the Info.plist file of the framework).
>
> jw
>
>
> Am 06.06.2013 um 21:04 schrieb David Holt <email@hidden>:
>
>> Hi all,
>>
>> Just when I thought I'd seen everything deployment could throw at me….
>>
>> I had an app giving me malformed version number errors for the App and Model framework. I discovered that there are some jars in Wonder that are version 50 so I thought I'd switch java versions on the server rather than try and fight Wonder.
>>
>> I switched the server Java version to Java 1.6
>>
>> I rebuilt the App and Model framework in eclipse with compiler settings set to 1.6. There are no errors on my development box when I run in eclipse.
>>
>> Now when I try to deploy the app with fully embedded frameworks I can start it on the command line (it still complains about malformed version numbers).
>>
>> I don't know why the app won't start in JavaMonitor and produces no log
>>
>> I have deleted the app and model framework and rebuilt everything.
>>
>> Have I missed something?
>>
>> thanks,
>> David
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden