Hi Nick, Eventually I'd like separate CBI builds for (a) RSE, consuming Platform/CDT/EMF as prerequisites, with a CVS Repository (b) TCF, consuming Platform/CDT/RSE/DD-DSF as prerequisites, with an SVN Repository.
Current status for (a) is that I have a "home-grown" builder, and created a new tm.releng project based on the Modeling build, which kinda succeeded but not quite completely - missing pieces include - automated running of tests - promote script - signing of single feature jar instead of separate ZIPs Some of the specialities of the RSE build include - relatively many ZIP packages to produce, I never got around understanding the Packager - dstore server runtime to produce separate from SDK Current status for (b) is that no automated builds at all exist for TCF yet, and no unittests exist either. A single downloadable SDK package would be a nice start, separating into thre SDK ZIPs later: - Core, - RSE-integration, - DD-DSF-integration. I guess it'll make sense to create 2 separate bugs for the RSE build and TCF build respectively since they are on CVS and SVN respectively. I'm watching the channels you mentioned. Cheers, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm > -----Original Message----- > From: Nick Boldt [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 05, 2008 8:09 PM > To: Oberhuber, Martin > Cc: Andrew Overholt; [EMAIL PROTECTED]; dash-dev@eclipse.org > Subject: Dash.commonbuilder - documentation, tracking > progress, and how to be a guinea pig > > > As a matter of fact, I'm very interested in being a guinea > > pig myself with the TM build :-) > > The whole TM? Or pieces of it, like RSE? Either is possible, > I'm just curious what flavour you prefer. There's the single > composite build (GEF includes Draw2D & Zest components, too), > and there's the multicomponent style (a la Modeling builds). > > > * Should Wayne continue working on the "Builder" wiki > > telling projects how to use PDE build themselves etc? > > Uh, sure, but maybe after we have a stable system for > tools.gef (one requirement; UI tests) and > technology.linuxtools (two requirements, including one which > is an archived Update site rather than a standard SDK zip; > uses SVN). Seems a little cart-before-horse at this stage. > > > Want me to file a bug against Dash.commonbuilder for > > TM as a reminder? > > If you'd like, sure. > > To be in the loop as bugs change, you can: > > * add yourself to https://dev.eclipse.org/mailman/listinfo/dash-dev > * watch bugs for [EMAIL PROTECTED] > * subscribe to > http://wiki.eclipse.org/index.php?title=Build_Workshop_3:_Buil d_Hard_With_A_Purpose/Report&action=watch > > Nick > _______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev