| Summary: | [prov] Tool to check the presence of a suitable version of bundles | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Pascal Rapicault <pascal> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | bokowski, douglas.pollock, elias, gunnar, jeff.myers, jeffmcaffer, lfrenzel, manahan, mlists, pombredanne, remy.suen |
| Version: | 3.4 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Pascal Rapicault
What? In english (or french) please... I have no clue what this involves. D. Yep that was a bit short, sorry. We need a tool that given a file containing plugins ids and their versions will see if the listed plug-ins are available in an eclipse install. For example the input file (probably generated by the build) would contain org.eclipse.pde.ui, 3.2.0.v20051215-1500 org.eclipse.jface, 3.2.0.I20051214-0010 org.eclipse.team.cvs.core, 3.2.0.I20051212-1600 ... So given that file and an eclipse install, the tool would tell if whether or not all the listed plug-ins are found. Why is this filed on a non-platform product? Because they are tools for committers. So JDT is a committer tool? So PDE is a committer tool? I agree that there are a PDE side to these bugs, but the idea in entering those bugs against the committer tools was to make the foundation aware of what was going on and giving it a chance to participate. So I will reassign them back to them for now until a discussion is initiated. So what is the mechanism I would use to determine if org.eclipse.pde.ui, 3.2.0.v20051215-1500 is in eclipse-SDK-3.1.2-linux-gtk.tar.gz ? Unzip, untar, look in the plugins directory, match a file called org.eclipse.pde.ui ... then what? Do you want this as a web application? As an RCP application? kajsdflkasj dfljkas dfkjasf afkasdfk afhsd D. the idea is that products/features/whatever would have a bill of materials that was itself secured (signed, downloaded from a secure place, ...). The BoM would list bundles, their versions, and their signature info (signer certificate). The warm fuzzy tool could then scan a *configuration* and determine if there were any differences. Adding helpwanted to the keywords, and sorting as LATER. Sorry, I don't know what to do with this. D. Moving to PDE Build I suspect you're more likely to get more help if the 'summary' is something slightly less abstract ... This is not an API thing. The intent is to validate that a particular configuration of Eclipse matches some level of expectations. Moving to the Provisioning work. Pascal: you should have known this bug report would come back to haunt you ;) In fact this is more of a "qualification" tool. awe man, I really wanted a "warm fuzzy" tool. The new summary is so boringly descriptive. Feel free to reopen if you want to work on this. |