Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Selective Compiling, is this possible?

Although not documented, it is possible to add extra constraints to help
Tycho dependency resolver choose from alternative providers of the same
capability. Try adding configuration like below to BundleC pom.xml file


This will tell Tycho to resolve BundleC dependencies as if it had
"Require-Bundle: BundleB" in addition to existing Import-Package, which
will give BundleB strong preference over BundleA.

Alternatively, you can filter BundleA from BundleC target platform as
explain in [1]



On 2014-03-31, 11:43, Neil Corbet wrote:
Hello All,

I have a scenario where I need to make sure one bundle compiles against

Here is my scenario:

BundleA exposes package **.  This bundle uses spring
to create mock objects against interfaces in said package. These mock
objects are exposed as services that a UnitTest bundle (
eclipse-test-plugin) uses strictly for unit testing a service
implementation bundle.

BundleB exposes the same package **. But these
interfaces extend spring data PagingAndSortingRepository, which the
mocking framework does not like.

BundleC imports *package*. I need this one to compile
against BundleB and not BundleA.

When I built my product and installed it, I kept getting an error when
using one of my services that a method was not found. It seems it was
compiling BundleC against BundleA's dao package and not the ones in
BundleB extending the spring data interfaces. BundleA is not in the
feature that defines my product.

Is there a way to use the maven tycho compiler plugin to  compile
against BundleB and not BundleA?



tycho-user mailing list

Back to the top