[news.eclipse.tools.emf] Re: project dependency obstructs EMF .genmodel

[Nikolaj Berntsen <nberntsen@xxxxxxxxxxxx>]

> You need to add project B as a dependent project when creating Java project
> A. See Tutorial: Generating an Extended EMF Model at:
> http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E/emf-home/docs/slibmod/slibmod_main.html

Sorry, that important information was left out (despite proofreading it 
several times, ahh the easy of fooling oneself).

The EMF generation fails  when B is a dependent project. It does not 
fail when B is exported to a jar and copied to project A.

(If B was neither a dependent project nor exported to a jar, then I 
would get compile errors -  I usually see that before posting .-)


Cheers,
/\/ikolaj

> Frank.
>
>
> Nikolaj Berntsen wrote:
>
>
> > Dear Group,
> >
> > I just spent a long time comming to the following conclusion.
> >
> > If an eclipse project A (containing @model marked up interfaces) depends
> > on an eclipse java project B (e.g. providing foo.bar.Goo.java), then
> > generating an EMF model (Context-Menu-on-A->New->Other->Eclipse
> > Modelling Framework->EMF Models) fails to pick up the package in project
> > A (last part of the wizard). No errors, no debug on the console (I might
> > be able to increase verbosity somewhere).
> >
> > I project B is exported to a Jar and the jar is copied to project A,
> > then everything works.
> >
> > I am using eclipse 2.1.1 (and 3.0 M3) and EMF 1.1.1.
> >
> > (It might be migh memory, but sometimes it seems to work anyhow)
> >
> > Is this a bug or a feature?
> >
> > Cheers,
> > /\/ikolaj