[news.eclipse.tools.emf] Re: 3.4M4 + new EMF Project results in PDE Warn

[Ed Merks <merks@xxxxxxxxxx>]

Felix,

The build.properties won't exist until we generate the model.  And we 
only generate an execution environment setting if you choose 5.0 
compliance.  For all we know the generated code for the model would work 
with Java 1.3 otherwise.  I suppose we could generate it to be 1.4 just 
to make the PDE happier and as a user, you could change it.  Feel free 
to open a bugzilla for this second issue.  There's yet another new 
warning in M5 about Eclipse-LazyStart being replaced by 
Bundle-ActivationPolicy; that's the second time this one has changed.  
:-(  So I suppose we'll need to react to that as well, though that new 
thing probably only works for Eclipse 3.4...


Felix Dorner wrote:
> Hi, creating a new "Empty EMF Project" in Eclipse 3.4M4 + EMF 2.4 
> (from the 3.4 update site) gives two warnings of type "PDE Problem". 
> This does not happen when I create a new "Plug-in Project", so I think 
> it's EMF related:
>
> - build.properties does not exist
>
> - No required execution environment has been set MANIFEST.MF   
> allure.parser/META-INF    line 1   
>
>
> Comments?
> Felix