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?


Do I understand correctly that you have two bundles expose the same package, which contains both java interface and implementation classes? This would explain why you want to control bundle selection at compile time. However, wouldn't it be better to move interface classes to a separate BundleD, and make both BundleA and BundleB provide implementation of interfaces from BundleD? Then there is no interface duplication and an appropriate implementation can be automatically selected at runtime.

Kind regards,
Mikhail Kalkov

Eclipse Developer | Purple Scout AB |
Kyrkogatan 20-22, SE-41110 Gothenburg, Sweden

On Mon, Mar 31, 2014 at 5:43 PM, Neil Corbet <neil.corbet@xxxxxxxxx> wrote:
Hello All,

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

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