Contributing to JSDT #3 : Build Targets on the bleeding edge
I’m not on the JSDT team, so this may not be exactly how they do it. But it works for me.
My code no longer compiles!
This morning, I updated all the code I previously checked out. And now my rhino.ui project has a compilation error in RhinoTabGroup:
After a little investigation, I determined that RhinoTabGroup is using a new 3.7 method in AbstractLaunchConfigurationTab. It has just been introduced. I’m building against Eclipse 3.6, so don’t have this method.
So if I want to keep my JSDT source code in sync with the latest, I’ll have to also keep up with any dependencies.
One idea to resolve this would be to download the latest milestone builds and put them in my build target. However, this change is very recent and is not in a milestone build yet.
Another idea is to check out the latest o.e.debug.ui project and any dependency projects (hopefully not too many).
Check out more projects
To add the eclipse CVS repo, copy this into the CVS Repositories View:
And check out org.eclipse.debug.ui and org.eclipse.debug.core projects
And the compilation issue is resolved.
Going forward, my build target and workspace projects will change often. I’ll need to actively modify these to keep things rolling along. I’ll be doing a combination of:
- Including other Eclipse projects in my workspace, on an as-needed basis. I’ll start getting a good sense of what these projects are as things break.
- Change my build target to move up to Milestone builds.