Community
Participate
Working Groups
Build Identifier: I20100520-1744 I am trying to create a RAP based Target Platform that contains EMF. I added EMF databinding in the "locations", but in "content" it does not show up and therefore creates build problems. Reproducible: Always Steps to Reproduce: I will attach the target file and some screenshots after the bug is created.
Created attachment 170840 [details] target description
Created attachment 170841 [details] screenshot that shows that EMF databinding is part of the target configuration
Created attachment 170842 [details] screenshot that shows that EMF databinding is not available in the target platform
This is currently a blocker for me, as I can not build the RAP version of our single sourced product. Any help how to fix this is highly appreciated. Thanks!
Created attachment 170882 [details] the resulting build errors
I believe that this was a bug in the EMF build or Buckminster. In any event, it should be fixed now. If you point at a more recent EMF repo you should be able to add EMF things to the target and actually get the bundles. In the mean time you may get away with adding the EMF RAP support feature to your target. That worked for me but I only needed ecore and a few low level things.
(In reply to comment #6) > I believe that this was a bug in the EMF build or Buckminster. The target platform provisioner assumes that all non-strict versions are requirements. This is an approximation at best and an undocumented limitation in the TP provisioner. The well documented convention that identifies requirements as non-greedy is not used. Until we have a unified and well documented interpretation of what a feature really is I would appreciate if the term "bug" was used more cautiously. Buckminster will allow several interpretations and we have now changed our defaults to be better aligned with the assumptions made by the TP provisioner.
(In reply to comment #6) > In any event, it should be fixed now. I just updated the TP by closing and reopening the target editor. It still shows the same behavior as before. So it is definitely not fixed for me :-(
Has anyone tried my attached target configuration to see if they can reproduce the problem?
I just upgraded to RC3 (complete new reinstall) and I still get the same problem.
I created a new target configuration from scratch and that works now. Why? Anyhow as this works now I am closing this weird bug as it works for me after RC3.
