Hi Mike,
Yes. If you rely on JARs instead of *.frameworks. :)
Every logic that relies on *.framework doesn't work for me (and probably
for all Maven users).
Cheers,
Henrique
On 19/05/10 13:16, Mike Schrag wrote:
> This should have been autodetected if your framework/app were linking
> against WOOgnl ... Is there a chance this frameworks in question weren't?
>
> ms
>
> On May 19, 2010, at 12:08 PM, David Holt wrote:
>
>>
>> On 2010-05-19, at 7:52 AM, Dev WO wrote:
>>
>>> Hello Amiel,
>>>
>>> I had the same "issues" and it happened to be a problem with the
>>> build.properties file of the project.
>>> Try creating a new project to see the format of that file and adjust
>>> the one of the project having issues. Restart Eclipse;)
>>>
>>> The actual lines that were creating issues were:
>>> component.inlineBindingPrefix=$
>>> component.inlineBindingSuffix=
>>
>> Instead of
>> component.inlineBindingPrefix=[
>> component.inlineBindingSuffix=]
>>
>> Thanks Xavier, that's been bugging me for days!
>>
>> David
>>
>>>
>>> Hope that helps,
>>>
>>> Xavier
>>>
>>>
>>>
>>>> Hi,
>>>>
>>>> I just installed eclipse 3.5.2 and latest wolips 3.5 stable and now
>>>> I got weird build errors.
>>>>
>>>> Errors:
>>>>
>>>> - 'list' must not be a constant
>>>> - 'item' may not be a constant when 'displayString' or 'value' is bound
>>>>
>>>> I am using WOGnl inline bindings and I'm pretty sure these aren't
>>>> coding errors and I do not get these errors in eclipse 3.4 and
>>>> corresponding wolips plugin.
>>>>
>>>> Anyone have an idea why? I am on windows if anyone cares.
>>>>
>>>> Thanks,
>>>> Amiel
>>>>
>>>>
>>>> --
>>>> socket error: unable to connect to 127.0.0.1
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed May 19 2010 - 17:34:05 UTC