You may want to take a look at the Buckminster project (which is used by many projects at Eclipse to build).
Happy to answer questions and more on the buckminster newsgroup or on IRC #eclipse-b3 (open channel for all build related issues).
On Jul 16, 2010, at 2:38 PM, Daniel Pastore wrote:
sorry for the delay to reply. Let's see:
> I thought it was used to specify different versions of plugins/features toI'm not 100% sure whether we are saying the same, so let me rephrase:
> look and checkout during the build process,
The map file lets you select one specific version for each feature/plugin
included in the build.
Yes, that was what I meant. Thanks for your rephrase, it sounds much better than mine!
> but all map files I saw point to the same tag/version/revision.The example at http://wiki.eclipse.org/Subversive_PDE_Fetch contains:
meaning that this feature and its plugin are both checked out from the tag
"tags/v20070222". Of course, different plugins could be fetched from different
tags. If specifying a tag is not sufficient for your case, you might need the
"revision" keyword (which I haven't used - so I can't comment on that).
Alright, this is the exact example of what we said above.
A real world map file using SVN can be found here:
(you might want to compare a few different versions of this map),
but note, that in our case omitting the tag attribute works only because
we use the patch from https://bugs.eclipse.org/301045
Does any of this answer your question?
Yes, parts of it, but I still don't understand how is this map file will be used in the build process of my project.
When I checkout/update the code from SVN (either using PDE SVN or SVN Ant, i don't see a big difference for my use) I can choose from trunk or any branch or any tag or even any specific revision.
So what would be the utility of this map file? (I just see it being useful for the Eclipse build, where it points to specific versions of each project)
Thanks for your attention,
cross-project-issues-dev mailing list