Bugzilla – Full Text Bug Listing
| Summary: | [tools] Make feature scanner available to those who want it | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Ian Bull <irbull> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | ahunter.eclipse, bugs.eclipse.org, david_williams, pascal, pwebster | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
There are now more powerful tools in b3 or cross-project bucket. |
Created attachment 170680 [details] feature scanner Some people have asked for the feature scanner. This needs lots of work (polish). Currently there are a few constants at the top of the file which describe 1. The repo to check 2. The local location to write the features to 3. The local output location to write the metadata too It simple prints to the console any IUs who's requirements don't match what the publisher would do. If this tool is something we want to integrate into our builds, then I can fix it up a bit.