Re: [cross-project-issues-dev] Ready for our yearly final daze?

[Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>]

OK, I did a bit more research regarding p2.mirrorsURL and found:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=301237
  http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05671.html

Since these are fairly recent I conclude that p2.mirrorsURL is (still)
recommended. However, even David wrote in the bug:

  "You (P2 team) may want to consider providing a "spec" or "help
  document" for describing what the mirror URL should be. That's always been a
  bit unclear"

Still, all we have is *one* example by Kim and the comment that the publisher
will pick it up if the attribute is defined in site.xml. 
Hm? I thought site.xml has long gone with the old update manager??

Can anyone please explain in a few sentences:
- what happens if a repo does not define this attribute?
- how exactly should the value for this attribute be constructed?

It would be phantastic, if s.o. could actually give a hint on how to test
whether it works :)

TIA,
Stephan

On Wednesday, June 08, 2011 10:33:52 AM Stephan Herrmann wrote:
> How about:
> 
> "be sure its mirrorsURL is updated to reflect the new location of the
> artifacts (see "how to enable mirrors")."
> 
> Is using "mirrorsURL" a current concept, or is that a left-over from former
> times? I had the "impression" that using mirrors works out-of-the box
> without any help by special attributes in the  meta data?
> 
> If "mirrorsURL" is recommended as of today, could someone pls point to the
> documentation what exactly the value of the attribute should contain.
> (I've seen the linked example, but it leaves me puzzling why a reference to
> a directory has "formal=xml" if the metadata actually sit in jars??)
> 
> OTOH, I'd be much happier if I can avoid manually messing with our final
> meta data *after* everything has been tested.
> 
> thanks
> Stephan
> 
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev