Community
Participate
Working Groups
I am using the following p2 repository URL in my target definition: http://download.eclipse.org/rt/eclipselink/updates When p2 tries to load the p2 metadata from this composite repository, it stops with the following error message: No repository found at http://download.eclipse.org/rt/eclipselink/updates/categories. An exception stack trace is not available. By looking into the composite repo I found that at least the .../categories is *not* an artifact repository. Maybe that is the problem?
I don't see the issue with Indigo GA, I'm trying again after updating to SR1. The categories dir is not an artifact repository. It only contains category metadata.
(In reply to comment #1) > I don't see the issue with Indigo GA, I'm trying again after updating to SR1. Maybe this only occurs if someone is using a target definition file. IMO the strategy by p2 when being used in the IDE is different, i.e. it downloads the metadata in a first step and only then starts to download the artifact.xml/jar files. > The categories dir is not an artifact repository. It only contains category > metadata. Sure, it's not an artifact repository, but compositeArtifacts.xml tells p2 that it is: <?xml version='1.0' encoding='UTF-8'?> <?compositeArtifactRepository version='1.0.0'?> <repository name='""EclipseLink Release Repository""' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> <properties size='1'> <property name='p2.timestamp' value='1267023743270'/> </properties> <children size='13'> <child location='categories'/> ...
Ok. Try it again... I've removed the 'categories' child from the compositeArtifacts.xml. The instructions for creating composite repos wasn't clear and either case worked in testing. This is the first time an issue has shown up. If it resolves your issue I'll update the process.
Modified CompositeP2 generation scripts on all active branches to not include the categories directory in the compositeArtifacts.xml. Awaiting confirmation this resolves the problem before merging.
Perhaps for clarity I should note that the compositeContents.xml remains unchanged and does include the "categories" directory (child). I have also verified (with Indigo SR1) that the modified compositeArtifacts.xml does not cause any problems accessing the repository from within the IDE using either "install new software" (not recommended), or when modifying the target platform.
(In reply to comment #5) > Perhaps for clarity I should note that the compositeContents.xml remains > unchanged and does include the "categories" directory (child). Yepp, no need to change this since .../categories contains a valid content.xml. I tried it once again and didn't see the error. From my point of view this bug can be closed but I am never sure whether p2 uses some caches that make this error invisible for the time being. Anyway, if it re-appears I would reopen the bug. Thanks for fixing this!
merged in 10176-10180 for 2.3, trunk, 2.2, 2.1 and 2.0 branches respectively.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
