Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » 3.4 installation as a target platform
3.4 installation as a target platform [message #587347] Thu, 18 December 2008 23:06
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3071
Registered: July 2009
Senior Member
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
dropins/ directory.

So my question is, what should be excluded from check-in when a Ganymede
installation is used as the target platform?

Previous Topic:Problem building plugin on ganymede with bundle-nativecode
Next Topic:Questions about incorporate two RCP applications
Goto Forum:

Current Time: Tue Aug 03 04:33:35 GMT 2021

Powered by FUDForum. Page generated in 0.02025 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top