[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Using map files with Subversion
|
+1. Tycho + Maven = no map files needed. Just fetch your sources (or let
Hudson fetch 'em) and build.
Of course there are MANY ways to build osgi bundles. There's no "best"
solution, just different ways to accomplish the same goal; of course
each solution brings with it different strengths/weaknesses.
This spreadsheet (which is incomplete - especially the Tycho/Maven
columns) shows some of the things that the various technologies have in
common, and where they diverge:
http://spreadsheets.google.com/ccc?key=0AmGcQy-AtllqdDV3eUtCTEM0TU5UakVFbFAyWUhyZnc&hl=en
N
On 07/16/2010 01:07 PM, Jesse McConnell wrote:
Or use maven and join the civilized world...:)
cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Fri, Jul 16, 2010 at 11:59, Henrik Lindberg
<henrik.lindberg@xxxxxxxxxxxxxx> wrote:
Daniel,
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).
Regards
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx
On Jul 16, 2010, at 2:38 PM, Daniel Pastore wrote:
Hi Stephan,
sorry for the delay to reply. Let's see:
I thought it was used to specify different versions of plugins/features
to
look and checkout during the build process,
I'm not 100% sure whether we are saying the same, so let me rephrase:
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:
 feature@xxxxxxxxxxxxxxxxxxxxxxxxx=SVN,tags/v20070222,https://svn-pde-build...
 plugin@xxxxxxxxxxxxxxxxxxxxxxxxx=SVN,tags/v20070222,https://svn-pde-build...
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:
 http://dev.eclipse.org/viewcvs/index.cgi/trunk/releng/map/otdt.map?root=TOOLS_OBJECTTEAMS&view=log
(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,
Daniel Pastore
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
