|Buckminster builds don't include linked resources [message #632132]
||Mon, 11 October 2010 16:56
| Peter Woods
Registered: July 2009
I'm working on a large scale RCP project at the minute for one of my customers. They want me to improve the build process from using lots of custom Ant and Ivy scripts to something more intelligible. I've decided that Buckminster is the right tool for this job, and have created an appropriate R-Map to map out the project's resources, some C-Queries, etc. These all seem to work pretty well.|
The customer uses the ClearCase version control system, however. It's extremely slow to build from because the "bin/" folder in your project lives on a network drive with your other project resources. To work around this, they have set up an Eclipse linked resource that maps "eclipse_build_loc" to, say "D:\Temp\build" for build output. Then inside each plug-in you include the following in the ".project" file.
This maps the output "bin/" directory to live on your local disk instead of on the network.
Unfortunately when you do a Buckminster build of these plug-ins they don't include the compiled classes. I thought I was so close after mapping out all the dozens of search locations out!
Any suggestions on how to work around this? I've tried debugging the Buckminster process, but the codebase is too large for me to quickly find out what's going wrong. I'm not above patching my version of Buckminster, if necessary, until you guys can come up with a fix for this.
Sadly we can't just take out the linked resources stuff. Are things like a CSPEX to manually force the inclusion of the output directory sane?
A test plug-in that demonstrates this failure is downloadable from here.
Powered by FUDForum
. Page generated in 0.15713 seconds