[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tycho-user] Unable to resolve eclipse plugin dependency using Tycho!
- From: Barrie Treloar <baerrach@xxxxxxxxx>
- Date: Thu, 19 Jul 2012 16:46:18 +0930
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=u/ejhHl9MjdrCAVf7K/d9SjqvNJtg4mwTVnNQylyH5M=; b=C4ADtSSR8LT+7kG3JTQZSjFigUGsOwLMg4VnBxnmM9h67EJSxxNN7RW34YDWi1NDaH iuG281eZ3trsOhvzroxA5nd3TCeVZFEfaeIMLS0yKeZTDq2Sdhglchv5bYvfwAqqpWOW nSx+8cMnQIVSsQm/I1Nez9byEwLWDuxwvdFhvZdreMGLXlWcbExzfcom6oh+pUqYjSC/ s1xDvi2uA2U44aK48KyfPHW0He7Sa6726izwUo3DN5EPC7vZpG3pdwb2H2mScztud02P /u0a5TFeDuoWoiGutd+OX/9lPDqfMlG5fgx2+K3fVthOWYn5vppocIzLv85Y+1sQTqV8 Pjag==
On Thu, Jul 19, 2012 at 3:57 PM, dip v <dipv2902@xxxxxxxxx> wrote:
> I am using Tycho for building eclipse plugins using maven. it works good
> when all required eclipse plugins are child modules for a project. But now
> if I install required plugins in local maven repository then its not able to
> locate it in maven repository.
> Does Tycho resolve dependencies from local maven repository? or am I doing
> something that is not supported by Tycho?
> I added all required eclipse plugins to local maven repository and mentioned
> its maven coordinates in parent POM. but it ignores <dependencies> section
> in parent pom. It gives error as:
> Bundle baseImplProject - Missing Constraint: Import-Package:
> com.sample.dependentProject; version="1.0.0"
> How to resolve eclipse plugin dependency using Tycho?
I"m still new at this, so my answer may not be correct.
Tycho doesn't use Maven dependencies to resolve your Eclipse dependencies.
Tycho will however use dependencies available in the same reactor
build of your project (i.e. modules as you discuss above). If you
don't want that then I think you need to use a target platform to
resolve Eclipse dependencies against.
Tycho uses Manifest first by default to resolve dependencies.
Since you are building Eclipse plugins I suspect that all your
dependencies are already OSGi compliant, so you should not need to use
You could also look at the demo projects to see how they do it.
I'm not building Eclipse Plugins, I'm building an RCP application.
So I have a target platform that only contains a subset of the plugins
that I actually need. Im also using Nexus to proxy the Eclipse P2
repositories to improve performance.