|3.4 installation as a target platform [message #587347]
||Thu, 18 December 2008 23:06
| Eric Rizzo
Registered: July 2009
My team is in the habit of checking in our target platform into CVS so |
that we are all building against a known platform.
I've always just taken an Eclipse EPP package, unzipped it, added the
other required features and plugins, and then checked that in. This
worked well while we were building against Europa.
But it seems that p2 complicates things a bit. I've noticed that there
seems to be machine-specific stuff (ie, absolute paths) in the
configuration/ and p2/ directories of the target platform, especially
after I run it to pick up something new I've added (or removed) from the
So my question is, what should be excluded from check-in when a Ganymede
installation is used as the target platform?
Powered by FUDForum
. Page generated in 0.02025 seconds