Fully reflect merge of pde.build in PDE's Oomph setup #71
Conversation
|
FYI, I had to commit this as well because the SDK configuration references the refactored project too. |
|
Thanks for taking care of that! |
|
BTW, with my recent changes to the aggregator setup, these things are visible now within projects:
Making it easier to notice and to change. |
|
That's handy! Until now I had to import them manually. What would be even more useful to test changes of the eclipse-sdk-prereqs.start would be if the content of that file would also be included into the activated modular target-platform if present. At the moment I manually added a 'target'-type target referring to that file (but interestingly that additional content stays even when I re-run the setup, which is good in my case). |
|
In the past such a thing was not possible , but now in principle, it could be composed though some people have trouble getting that to work and I don't have time to make such a thing work: https://www.eclipse.org/forums/index.php/mv/msg/1110731/1852217/#msg_1852217 It's currently a simple matter of switching the active target in the preferences (and then wait and wait for all the bundles that you already have downloaded to be downloaded yet again)... |
Since I have a relativly simple workaround for my problem, I'm fine at the moment. :)
Yep, I think we should consider to use the shared Bundle pool in PDE for the Target-Platform resolution, if one is available. |
This PR inlines the
PDE CoreProject and adds aPDE BuildWorking-Set.Furthermore it removes the 'core' element from ids.
Just like for the renaming of the project from PDE UI to PDE Core we have to provide a way to inform users that they have to update the Project-stream referenced in their workspace setup. Otherwise the setup is broken.
@merks can you please review this?