Thanks for the prompt fix!
On 30 Sep 2009, at 15:23, Mike Schrag wrote:
> fix committed ... you had a version format I wasn't expecting.
>
> On Sep 30, 2009, at 9:54 AM, Bill Michell wrote:
>
>> Yes, there is a pom.xml in that folder. Hmm. And there is the
>> culprit - a non-resolvable parent pom.
>>
>> So it looks like that framework *is* using maven... You learn
>> something every day. Thanks.
>>
>> On 30 Sep 2009, at 14:49, Mike Schrag wrote:
>>
>>> what about console?
>>>
>>> in the framework that's breaking, is there a pom.xml in that
>>> folder? in your build.properties, is there a version setting?
>>>
>>> On Sep 30, 2009, at 9:47 AM, Bill Michell wrote:
>>>
>>>> No error in the Error view nor in the workspace log file :-(
>>>>
>>>>
>>>>
>>>> On 30 Sep 2009, at 14:38, Mike Schrag wrote:
>>>>
>>>>> I'm guessing the build is throwing an exception coming up with
>>>>> your version string ... look in your Error View, in the console,
>>>>> and in the .log file in the .metadata folder of your workspace
>>>>> and see if there's an exception coming out of a getVersion
>>>>> method. Probably it will appear in Error View when you try to
>>>>> do a clean build of that project.
>>>>>
>>>>> ms
>>>>>
>>>>> On Sep 30, 2009, at 8:34 AM, Bill Michell wrote:
>>>>>
>>>>>>
>>>>>> On 30 Sep 2009, at 13:03, Mike Schrag wrote:
>>>>>>
>>>>>>>>> Digging further in, it looks like the Info.plist files are
>>>>>>>>> being truncated when the app and frameworks are built by
>>>>>>>>> 3.5.5990.
>>>>>>> are you maven or regular build? what do you mean the
>>>>>>> info.plist is truncated? can you provide an example? i've
>>>>>>> never seen anything like that on any of my builds ...
>>>>>>>
>>>>>>> ms
>>>>>>>
>>>>>>
>>>>>> Regular build, within Eclipse. Snow Leopard with all updates.
>>>>>>
>>>>>> Actually, checking again, it seems only one of my Info.plist
>>>>>> files (the ones from [ProjectRoot]/build/
>>>>>> [FrameworkName].framework/Resources.Info.plist) is truncated.
>>>>>>
>>>>>> The framework doesn't contain any java source - just lib jars.
>>>>>>
>>>>>> The Info.plist looks like this. [FrameworkName] edits are mine,
>>>>>> btw:
>>>>>>
>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>> <plist version="0.9">
>>>>>> <dict>
>>>>>> <key>NOTE</key>
>>>>>> <string>autogenerated</string>
>>>>>> <key>NSJavaPathClient</key>
>>>>>> <string>theTestFramework.jar</string>
>>>>>> <key>CFBundleIconFile</key>
>>>>>> <string>WOAfile.icns</string>
>>>>>> <key>CFBundleExecutable</key>
>>>>>> <string>[FrameworkName]</string>
>>>>>> <key>NSJavaRoot</key>
>>>>>> <string>Resources/Java</string>
>>>>>> <key>NSJavaRootClient</key>
>>>>>> <string>WebServerResources/Java</string>
>>>>>> <key>NSJavaNeeded</key>
>>>>>> <true/>
>>>>>> <key>CFBundleName</key>
>>>>>> <string></string>
>>>>>> <key>NSExecutable</key>
>>>>>> <string>[FrameworkName]</string>
>>>>>> <key>NSJavaPath</key>
>>>>>> <array>
>>>>>> <string>[FrameworkName].jar</string>
>>>>>> </array>
>>>>>> <key>CFBundleInfoDictionaryVersion</key>
>>>>>> <string>6.0</string>
>>>>>> <key>Has_WOComponents</key>
>>>>>> <true/>
>>>>>> <key>CFBundleSignature</key>
>>>>>> <string>webo</string>
>>>>>> <key>CFBundleShortVersionString</key>
>>>>>> <string>
>>>>>>
>>>>>>
>>>>>> And there it stops. Obviously, it isn't well-formed XML, so it
>>>>>> upsets the running app.
>>>>>>
>>>>>> It may not be this causing my problem, but it is the first
>>>>>> error that arises during application start-up, and doesn't
>>>>>> occur when built in Eclipse 3.4. And if I rebuild just that
>>>>>> framework in 3.4 then start up 3.5 without a rebuild, the App
>>>>>> runs exactly as it should, picking up the correct App name.
>>>>>>
>>>>>> --
>>>>>> Bill Michell
>>>>>> billmichel..mail.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Bill Michell
>>>> billmichel..mail.com
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> Bill Michell
>> billmichel..mail.com
>>
>>
>>
>>
>
>
-- Bill Michell billmichel..mail.com
This archive was generated by hypermail 2.0.0 : Wed Sep 30 2009 - 10:32:46 EDT