|
How to change the Target Platform when developing a RCP App? -
03-12-2008, 08:33 AM
Hi,
let say i want as a developer to be on the latest and greatest like the latest integration build.
But i am developing a rcp application in eclipse that has to use 3.3. How do you do that? How can i say the target platform is:
c:\eclipse33
and that eclipse gets its classpath == plugins from that part?
So that i can use 3.4 but debug and build against 3.3?
I have the same kind of problem now with something else but related.
I am using DLTK project of eclipse. But i am improving that project (the javascript part) quite a lot. So i have quite a big patch now. That is not yet in the eclipse cvs.. I can build the jars of those plugins and commit it to somewhere. But how can my co-workers als use those plugins very easy?
They cant checkout from eclipse itself because those dont have my patches that they need.
Or they have constantly checkout my jars that i check in in our own svn and they have to copy those into there own eclipse platform. But this is a bit stupid because those projects dont make sense in there own platform (they dont use those plugins) And this is very cumbersom because they have to do that constantly (and those projects do change quite a lot by me)
The only thing i can think of now that i create a complete copy of all the plugin projects in our svn repository and i constantly also keep that up to date and they check that out in there workspace so they can use that.
But the best thing was that we just could say use that as a target platform..
Then a platform could be a svn project as a whole
and i update plugins in that one. And everybody checks that project out and set that project as the target platform..
Or is something as this already possible somehow?
|