Moin Ashley,
beta1 mixed up PB.project. Download beta2 when it's available, and
select "Update PB.project" from the context menu for all your projects.
That should solve your problem.
Ulrich
Am 02.08.2004 um 11:30 schrieb Ashley Aitken:
>
> On 02/08/2004, at 4:53 PM, Ulrich Köster wrote:
>>> On 02/08/2004, at 4:20 PM, Ulrich Köster wrote:
>>>>
>>>> I'll guess you've played with 'Organize Imports' in Eclipse. Am I
>>>> right?
>>>
>>> Not extensively. I think I might have tried it on one file (just to
>>> see what it does, hey I'm an Eclipse newbie) but I think I even
>>> undid that (I've currently left a lot of basic imports that aren't
>>> needed in the source).
>>>
>>> Would that confuse WOLips?
>>
>> No. It's a bug in WOBuilder. Search the WOLips help for "Organize
>> Imports".
>
> Sorry, if you are referring to WOBuilder not liking fully qualified
> imports (preferring .* imports) then that is not the problem. I have
> specifically set Eclipse to use .* imports and I am pretty sure that I
> don't use any.
>
>> Can I get a copy of the PB.project?
>
> Sure it is attached (and thank you for taking a look).
>
> Can I assume that because I have performed the PrivateFrameworks
> modification for WOLips that my projects are not using the
> ProjectName.xcode/project.pbxproj file?
>
> As with the bug I filed
> <http://objectstyle.org/jira/secure/ViewIssue.jspa?key=WOL-104> WOLips
> for this application doesn't seem to know about the EOModel in one of
> its frameworks (even though it is open in the workspace and everything
> compiles and runs ok).
>
> I'll also attach (the second file) the PB.project file for the
> framework.
>
> Cheers,
> Ashley.
>
> --
> Ashley Aitken
> Perth, Western Australia
> mrhatken at mac dot com.
>
> <PB.project>
> <PB.project>
>
>
>
This archive was generated by hypermail 2.0.0 : Sat Aug 07 2004 - 03:37:33 EDT