Hi Lachlan,
I ran into this when I had my own EOJDBCPrototypes entity defined in
my table and one of my frameworks in turn had ERPrototypes added to
it's build path, even though I was _not_ using it. It got in there
when I created a new Wonder Framework and it was part of the default
setup.
It was less-than-intuitive because I wasn't sure where it was getting
the other model since ERPrototypes wasn't on the Application's build
path, just on one of the framework's.
Dave
On Oct 24, 2008, at 12:56 AM, Lachlan Deck wrote:
> Hi Mike,
>
> I've got two projects open in eclipse. The model for one project has
> been copied into the other (migration old project). When I double
> click on one model it complains that there a duplicate entities in
> the model group - and that this can be solved by creating an
> EOModelGroup file.
>
> So I create a default.eomodelgroup file and adjust to include only
> the one I want. Yet it still complains. So I close the other
> project. It still finds it (even after restarting eclipse).
>
> Any ideas? (WOLips 3.4.5523)
> Interestingly on my dev build of wolips this doesn't happen :-/
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Oct 24 2008 - 12:02:38 EDT