It might be downloading it from somewhere (using something like a http get task) and then using a system dependency to use it in Maven. Not sure this is the way its used in this particular place, but I think the subsystems subproject had certain Eclipse dependencies set up this way.
John Ross might be able to give more details... Cheers, David On 3 June 2014 20:37, Thomas Watson <[email protected]> wrote: > > With the latest from trunk I am no longer able to build because of a > reference to org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 > > Which repo is this supposed to exist? Here is the error. > > Failed to execute goal on project org.apache.aries.blueprint.itests: Could > not resolve dependencies for project > org.apache.aries.blueprint:org.apache.aries.blueprint.itests:jar:1.0.2-SNAPSHOT: > Could not find artifact > org.eclipse:org.eclipse.osgi:jar:3.8.2.v20130124-134944 in EclipseLink Repo > (http://download.eclipse.org/rt/eclipselink/maven.repo/) > > Tom
