On 2012-04-02, at 9:32 AM, Ted Archibald wrote:
> Well I think I got it cased now, I think it's because the app name had a period in the name, perhaps that freaks out the incremental builder.
>
> On Mon, Apr 2, 2012 at 9:34 AM, Ted Archibald <
email@hidden> wrote:
> The plot thickens...
>
> I'm not sure if this is a bug in wolips or what.
>
> But the symptoms are:
>
> -When you run the app you get an error like: Class 'Session' exists (interfacce org.jabsorb.client.Session) but is not a subclass of WOSession.
> -In the component validation, some (but not all components) will give: The class for 'X' is either missing or does not extend WOElement.
> -Bundleless builds do not work, but Bundle builds work fine.
>
> I discovered a bizarre fix... in the .project file for the app if you switch
>
> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>
>
> to
>
> <nature>org.objectstyle.wolips.incrementalframeworknature</nature>
>
>
> then everything works fine again. But that doesn't quite make sense to me. I downloaded the wolips source and I haven't a clue why this would or would not work.
>
>
> On Fri, Feb 17, 2012 at 5:06 PM, John Huss <
email@hidden> wrote:
> I think you should spend a few more weeks on this. That's the responsible thing to do.
>
>
> On Fri, Feb 17, 2012 at 2:06 PM, Ted Archibald <
email@hidden> wrote:
> Feels like I'm beating a dead horse:
>
> After trying many combinations of changes I finally found one change that helps. If I have wolips generate bundles, everything works perfectly. But I wonder how I can get bundleless builds to work again.
>
> If I have wolips generate bundles, clean the project then run, everything is back to normal. But if I go back to bundleless builds, then the issues come back.
>
>