Bugzilla – Full Text Bug Listing
| Summary: | non-Eclipse repositories ending up referenced in SimRel common repositories | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Cross-Project | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | milesparker |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
Miles, I assume the lwigl.org one is "yours" ... do you (or anyone else) know where the 'metascapeabm' one comes from? (In reply to comment #0) > http://lwjgl.org > http://metascapeabm.com These ere mine. The second is completely dross, the first is more complicated... > I'm not sure where these come from, but will make the following observations: > > A. I've not heard of any exceptions that are required, so suspect these are mistakes of one > type or another. ... So, one possible problem is a > build-time-only feature from AMP is making its way into the main repository, > instead of being used only at build-time. Yes, I was definitely aware of these issues, see: http://git.eclipse.org/c/amp/org.eclipse.amp.git/tree/releng/org.eclipse.amp.releng/releng/amp.rmap "<!-- NOTE: ***Not for inclusion in Eclipse provided builds. Provides support for externally hosted plugin dependencies.*** -->" > > C. As part of its aggregation, the b3 aggregator does go through all the > contributed features and extract all the referenced "update sites" mentioned in > feature.xml's and, well, aggregates them, in the content.jar/xml file for "ease > of use" by end-users. There are mechanisms to exclude some sites, by name, but > ... seems these "external" sites should not be in ordinarily installed features > anyway, so I think the first step is finding where these are being > "contributed" and fixing the original features. Yes, the inclusion was unintentional. I was not aware that aggregator includes referenced update sites. That's a bit confusing since it includes them, but then fails to resolve against them which seems the worst of both worlds.. :P It's a bit of a bummer, because it means that people installing the plugins even from another source will have to manually add the update site, but in practice that is probably what most people do anyway. I brought the general issue up on Modeling PMC, see: http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg01923.html http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg01925.html http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg01926.html I'm between a rock and a hard place, because without the 3D support a lot of the functionality is missing, but there aren't any OpenGL libraries that meet Eclipse standards. But what I'm *really* puzzled by is why this showed up in b3 now -- I don't include any of this stuff in the current build! So how is B3 aggregator somehow including a larger set of features than are specified for build target? I'm going to look at the required features and see where they're defined. I've removed the two sites mentioned from the url discovery element. seems fixed long ago (and for Juno, we do not include referenced repos ... though still true no feature should reference 'external' site. Yes, I did fix it last year. Note now that Wayne is reposting that gef3d is showing up on the aggregated repos. I can't figure out how that would have got there unless the aggregator is pulling stuff from the aggregated site that it hasn't been asked for... |
There a couple of non-Eclipse software repositories that end up in the list of repositories in common repo, for M4. You can see these in the content.xml file produced for /releases/indigo/201012170900. (There is, in total, 94 such references generated ... which doesn't seem good ... but ... but, the two this bug is about are http://lwjgl.org http://metascapeabm.com I'm not sure where these come from, but will make the following observations: A. This isn't "allowed". The common repo is only for eclipse projects. I've not heard of any exceptions that are required, so suspect these are mistakes of one type or another. B. I have heard about one of them, 'lwjgl.org' mentioned on cross-project list about build-time-only requirements for Amp. So, one possible problem is a build-time-only feature from AMP is making its way into the main repository, instead of being used only at build-time. C. As part of its aggregation, the b3 aggregator does go through all the contributed features and extract all the referenced "update sites" mentioned in feature.xml's and, well, aggregates them, in the content.jar/xml file for "ease of use" by end-users. There are mechanisms to exclude some sites, by name, but ... seems these "external" sites should not be in ordinarily installed features anyway, so I think the first step is finding where these are being "contributed" and fixing the original features.