Community
Participate
Working Groups
This seems to have just recently started to show up as unsigned jar. I assume a releng oversight? Or ... some reason? http://build.eclipse.org/indigo/simrel/reports/verifydiroutput/unsigned.txt
The jar you are pointing to is 2 years old (looking at the timestamp). So I am not sure where it is coming from and why it is included in this check/build. Can you give some background information on how/where this jar is included/used? gr. Martin
> Can you give some background information on how/where this jar is > included/used? I thought there was a FAQ on this already, but couldn't find one, so wrote one, using this case as an example. See http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#I_see_that_xyz_is_being_pulled_into_the_repository.2C_how_can_I_see_who_is_pulling_it_in.3F And, the result isn't happy for this case. :) But, your remarks sounded familiar ... I searched and found this bundle mentioned before, such as in bug 279369. I also logged on the build.eclipse.org shell and searched under /home/data/httpd/download.eclipse.org/modeling $ find ./ -name *org.eclipse.emf.teneo.hibernate.libraries* ./emf/teneo/downloads/drops/1.0.2/R200901081641/master/eclipse/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar ./emf/teneo/downloads/drops/1.0.2/R200901081641/master/eclipse/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar.pack.gz ./emf/updates/interim/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200907090915.jar.pack.gz ./emf/updates/interim/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200907090915.jar ./emf/updates/milestones_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar ./emf/updates/milestones_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200905051759.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200903191556.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200905051759.jar ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200903191556.jar ./emf/updates/releases_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar ./emf/updates/releases_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar.pack.gz This might be more "dangerous" than simply an unsigned jar. If this bundle is getting included because it satisfies so many "requirements", it might end up getting installed into someone's client IDE or runtime, and not sure it would be considered "supported" for that (even though, it does satisfy the requirements, so in theory, it should). Hope that helps.
Hmm, thanks for the faq, for me I just want to get rid of this plugin. Nobody is or should be using it... Where is it hosted? gr. Martin
(In reply to comment #3) > Hmm, thanks for the faq, for me I just want to get rid of this plugin. Nobody > is or should be using it... Where is it hosted? > > gr. Martin I also logged on the build.eclipse.org shell and searched under /home/data/httpd/download.eclipse.org/modeling $ find ./ -name *org.eclipse.emf.teneo.hibernate.libraries* ./emf/teneo/downloads/drops/1.0.2/R200901081641/master/eclipse/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar ./emf/teneo/downloads/drops/1.0.2/R200901081641/master/eclipse/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar.pack.gz ./emf/updates/interim/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200907090915.jar.pack.gz ./emf/updates/interim/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200907090915.jar ./emf/updates/milestones_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar ./emf/updates/milestones_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200905051759.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.0.v200806111928.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200903191556.jar.pack.gz ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200905051759.jar ./emf/updates/milestones_BAK/milestones/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200903191556.jar ./emf/updates/releases_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar ./emf/updates/releases_BAK/plugins/org.eclipse.emf.teneo.hibernate.libraries_1.0.1.v200901081641.jar.pack.gz
Okay I removed this plugin, it should not be there anymore
This caused an aggregation build failure: https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/indigo.runAggregator/670/console I'm not sure how you removed the bundle, but if you simple removed the file, then as far as the content metadata is concerned, it is still there ... that's part of the p2 contract ... so, it would still "find" it as a good match, and when tries to retrieve it, fails. If you just removed the file. If you did something else, then not sure what the problem is.
Hmm, just removed the file, I will get rid of the repository (it is too old and not used afaics). But why is indigo using this repository at all? It is years old. There are 2 other much newer repositories which should be used: http://download.eclipse.org/modeling/emf/teneo/updates/1.2.0/interim/ http://download.eclipse.org/modeling/emf/teneo/updates/1.1.2/interim/ Can this be changed (or can I change it)? gr. Martin
(In reply to comment #7) > But why is indigo using this repository at all? Which repository? Do you mean http://download.eclipse.org/modeling/emf/updates/interim/ If so, you can search the b3aggrcon files in org.eclipse.indigo.build to see it is being provided by emf-transaction.b3aggrcon ... so, you'd have to ask them "why being used". If you meant some other repo, you could track it down in a similar way.
Hmm, I created a bigger problem by removing these plugins... As I now understand that the repository has been invalidated. Do you know which files I should manually change to get rid of the references to these plugins? gr. Martin
(In reply to comment #9) > Hmm, I created a bigger problem by removing these plugins... As I now > understand that the repository has been invalidated. Do you know which files I > should manually change to get rid of the references to these plugins? > I do not, perhaps someone else does. I would recommend using "p2 APIs" (and/or tasks) rather than just removing files, or hand editing content.jar/xml files. One option is to work with the "emf release engineers" and have them recreate that "interim" repo (what ever that is) without your bundle. (And, since this has happened before, make sure it doesn't accidentally get included again, in future, however it keeps happening). There is a "p2 remove" task, for an example, see http://relengofthenerds.blogspot.com/2010/02/trim-your-builds-with-p2-repository.html but, to be honest, I've used that task before to remove pack.gz files (which is what the example is) and it worked well ... but, I have also tried using it to remove just one bundle and it did not work (don't recall what the problem was, but think in that old, vaguely recalled case I just ended up re-creating my repository).
Thanks. Btw, is the build failing because the plugin is not there anymore? Or because the repository is corrupted? In the first case the user of this plugin should solve it in my opinion, in the second case I should solve it. gr. Martin
(In reply to comment #11) > Thanks. > > Btw, is the build failing because the plugin is not there anymore? Or because > the repository is corrupted? > > In the first case the user of this plugin should solve it in my opinion, in the > second case I should solve it. > The second case. I do not think anyone is trying to use it directly. It is just that it "advertises" itself as satisfying a lot of package requirements so p2 picks it to supply those requirements. So, now, the repo still advertises that it is there, but it is not. If it was not there (and the repo correctly did not advertise it) then p2 would pick something else (or, more likely 3 or 4 separate bundles) to satisfy those requirements. In other words, the repo is invalid, now, so p2 can not succeed. Seems a good first step would be to restore the file, make the repo valid again, and then work on fixing the repo as a whole. At least, that's one approach. If you, or someone, knew how to recreate/fix the repo from scratch (without this problematic bundle) then that would work too.
I'm going to change title to be specific to the root problem, move to cross-project, and mark as blocking, since currently causing the aggregation build to fail.
(In reply to comment #13) > I'm going to change title to be specific to the root problem, move to > cross-project, and mark as blocking, since currently causing the aggregation > build to fail. The metadata have been updated to reflect removal of the JARs. Please confirm whether this fixes the problem with the aggregator.
That did it! Greatest thanks Kenn. I'll be able to sleep tonight after all.
Thanks Kenn for your help! gr. Martin
