| Summary: | How do we build CDT from a git repository | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | James Blackburn <jamesblackburn+eclipse> |
| Component: | cdt-releng | Assignee: | cdt-releng-inbox <cdt-releng-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Vivian Kong <vivkong> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, pwebster |
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 316208 | ||
|
Description
James Blackburn
It's pretty easy but requires changes to the CDT build scripts. PDE gives you a property to skip the fetch part of the build. You can then feed it a search path to find the plug-ins, etc, instead. So the idea is to check out the CDT from git and create the tag first then invoke the build.xml. Just found Bug 128846 has some comment on using custom search paths for PDE build. Yes, that's the one I was talking about. The work for this has been done in bug 289838. A git fetch factory which supports extracting plugins from a repository has been created. *** This bug has been marked as a duplicate of bug 289838 *** |