Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Moving p2 repos to archive

We should not encourage so much hand editing of artifacts.xml files. Especially changing the <mappings> element. No one should ever have to edit any repository files and doing so can break things in more ways than we want to know :) In principle, there should be a p2 API or ant script to do things to repos ... not editing xml files. So, if there's not, that's the thing to push on.

I think your move to archives should have worked more easily, simply by changing the child in your composite repo to point to the new location at the 'http://archives' location.

If that did not work for you, I suggest you open a cross-project bug, explain why that didn't work, and foster discussion there. Could p2 not "see" it at all? Did it let you select it for install, and then fail when it tried to fetch artifacts?

If moving a repository to archives takes more than copying and updating composite site, then I would encourage people not to do it. At least until someone develops a nice script to do it or some procedure that doesn't involve hand editing.

Thanks for pushing forward in this "new" area, and documenting your experiences.  But, as a general rule, I would recommend not updating "IT_Infrastructure_Doc" when you have lingering questions about it ... I think that page is supposed to be pretty firm, well accepted "how to" instructions. But do please continue documenting your experiences and advice! Some do that, sort of as a "first draft", on their own project's wiki, tell others about it as you have here, and if/when it evolves to become widely used or standard practice, then updating something like "IT_Infrastruce_Doc" would be great. But editing repository files is not widely accepted practice.

I will comment here on the p2.mirrorsURL attribute, though, since I've heard many people say they think it has to be changed (or, removed) when moving something to archives, but that should not be required. It would not help to "point to" archives if you move something to archives, as I think you found out,  but also it should not have to be removed, either. The reason is that it is simply giving hints to p2 about multiple locations to try when retrieve something (and any or all of them may fail). If something is on "archives", the downloads.php script should return "0" mirrors, in which case p2 "falls back" to getting it from the main artifacts repository it was told to in the first place. And, of course, if you are not seeing that, then sounds like some bugzilla entry somewhere is in order.

Hope that helps,

Thanks again! Keep pushing us forward!








From:        Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        06/11/2011 03:10 PM
Subject:        [cross-project-issues-dev] Moving p2 repos to archive
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Following the Final Daze doc I tried to move also p2 repos to
archive.eclipse.org, but found that my initial thinking that this,
too, would be transparent to users was just too  - well - naive.

After some experimentation I found a viable way to achieve the
desired transparence, which I scribbled into

 
http://wiki.eclipse.org/IT_Infrastructure_Doc#Move_files_to_archive.eclipse.org.3F

S.o. more knowledgable wrt p2 might want to check these:
- can the same be achieved just by the p2.mirrorsURL property (I couldn't)
- the replacements in artifacts.xml might be simplified by (re)defining a
   property?

HTH,
Stephan

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top