Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Repository Update Looping

> The particular jar surprises me here, because I thought we had disabled packing of nested jars in the platform build.

No. For those interested (or, who could help) see https://bugs.eclipse.org/bugs/show_bug.cgi?id=378200





From:        John Arthorne <arthorne.eclipse@xxxxxxxxx>
To:        P2 developer discussions <p2-dev@xxxxxxxxxxx>,
Date:        06/14/2012 10:45 PM
Subject:        Re: [p2-dev] Repository Update Looping
Sent by:        p2-dev-bounces@xxxxxxxxxxx




This looks like the following bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=361628

The particular jar surprises me here, because I thought we had disabled packing of nested jars in the platform build.

The fact you are on Windows is unrelated to the pack.gz file format. This is a compression format used by  Java on all platforms.

John

On Wed, Jun 13, 2012 at 9:46 AM, Joseph D Carroll Jr <jdsalingerjr@xxxxxxxxxxx> wrote:
I was following along in the m2e tutorial from EclipseCon ( https://github.com/jsievers/tycho-demo/tree/master/exercises ) and in exercise 1 it had me build the project using a p2 repository (step 14).  During the resolve process, it spent about 10 minutes (literally) trying to download a single document (org.eclipse.core.resources_3.8.0.v20120522-2034.jar.pack.gz).  It must have searched every mirror available, and switched mirrors every half second.  The attached document gives a short sample of the console output, in total the output would have been well over 100 pages but I was not able to capture all of it.

Does anyone know where I can find more information about this issue?  (how I can fix this issue?)
Is there a reason p2 would attempt to download a " *.pack.gz " when I am using Win7 64?  (is it thinking I am on a *nix system?)

This is certainly not the first time I have seen this and happens regularly when I install new updates.  This is just the first time I have been able to document the occurrence accurately.

Thanks,

JD




_______________________________________________
p2-dev mailing list

p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


Back to the top