Bug 347661

Description Nick Boldt 2011-05-30 11:05:37 EDT

Created attachment 196909 [details]
longer console error msg when mirroring using p2.mirror ant task

Steps to reproduce:

1. create mirrors of Eclipse, EMF, BIRT, WebTools, Orbit, etc. and place those mirrored p2 repos here:

http://download.jboss.org/jbosstools/updates/requirements/

2. composite those sites into a single site here:

http://download.jboss.org/jbosstools/updates/indigo/RC2/

3. point target platform at that site thus:

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/multiple.target

4. convert that .target file into a .p2mirror.xml script (see build.xml in same folder):

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/target-platform/multiple.target.p2mirror.xml

5. Run p2.mirror.xml script, and get this error:

    [exec] [p2.mirror] !MESSAGE Connection to memory:1306766825835/p2.index failed on unknown protocol: memory. Retry attempt 0 started
     [exec] [p2.mirror] !STACK 0
     [exec] [p2.mirror] java.net.MalformedURLException: unknown protocol: memory

(longer console error attached)

QUESTIONS:

Is this a problem in one of the source p2 repos on eclipse.org from which I mirrored? Never had this issue w/ M5, M6, or M7 - only discovered it this week pulling from RC2/RC3 bits.

If not an upstream problem, what does the error mean, and how can I resolve it? It doesn't seem to block the mirroring operation, but it worries me in that I've never seen anyone try to use "memory:" as an URL's protocol (in place of file: or http: or ftp:, that is).