Hi David,
I don't think that is the case here. This is blueprint and the pom was
updated to simply refer to a new version of equinox. I suspect it built
locally because the developers local m2 cache likely has the version
configured manually. But shouldn't the aries build be setup to work
without manual configuration of the local m2 cache? Is there not an aries
maven repo we can use to place the dependencies we need such as equinox?
Tom
From: David Bosschaert <david.bosscha...@gmail.com>
To: "dev@aries.apache.org" <dev@aries.apache.org>
Date: 06/04/2014 01:49 AM
Subject: Re: Current build and org.eclipse.osgi version
3.8.2.v20130124-134944
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 <tjwat...@us.ibm.com> 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
