Bugzilla – Full Text Bug Listing
| Summary: | Simple Configurator Manipulator missing from Equinox DL page | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | DJ Houghton <dj.houghton> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jeffmcaffer, john.arthorne, kim.moir, tjwatson |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | stalebug | ||
|
Description
DJ Houghton
I am not sure I like this direction. Eventually we will end up listing every individual bundle jar equinox produces. There is no clear line between what bundle jars we offer on the download page vs what we include in the all inclusive zip. I am thinking we may want to do away with all the individual downloads of the bundles and simply offer our repo and all inclusive zips instead. Jeff? Hmmm, certainly offering each individual bundle will be tedious. Originally the idea was to have "the service implementations" available so that OSGi folks could simply get the Equinox XXX service without having to get all of Equinox and figure out which bundle(s) was the right one. I dunno how many people actually go for the individual files though. In the absence of some sort of repo client, putting them on the downloads page is the only alternative. Its what Felix does http://felix.apache.org/site/downloads.cgi. If this can be automated then lets do it. Otherwise, what's the plan for how people discover the implementations we provide? You could also list each bundle within the equinox sdks as individual categories. That's what we did for pde api tooling ee fragments because we wanted to allow people to only download selected fragments, not the entire feature. This can be down by the use of a p2.inf. I'd like to encourage people to consume bundles from repos versus all the individual bundle downloads, I agree it's tedious :-) Another option is to use an XSLT to transform our repository into an HTML page. Then a user could navigate through the repository with a browser and download individual bundles: http://thegordian.blogspot.com/2010/05/what-exactly-is-inside-that-p2.html For many projects this doesn't make sense because it loses p2 metadata and encourages use of dropins, but for Equinox we have lots of bundles that can be used in simple non-p2 OSGi environments where they just want to grab the raw bundle. I like that idea. I can remove a lot of brittle template files and replace them with generated html from the repo + XSLT. I too like this. We should be able to filter out the goofy IUs that we don't need as well. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |