I have to build an Eclipse-plugin with a Maven/Tycho which has dependencies to other 3rd parties. As embedding dependencies is not yet supported by Tycho, I split up projects into two as following:

  • A-thirdparty: project with a packaging 'bundle', built by maven-bundle-plugin, having 'Embed-Dependency' instruction, and exporting all packages which are required by a plug-in 'A'
  • A: project with a packaging 'eclipse-plugin', using tycho-maven-plugin, and Tycho's target-platform-configuration plug-in with pomDependencies set to consider.

When I build them separately (at first, thirdparty aggregator, then project A itself), everything works fine. However, if I aggregate both those projects (using multi-module POM), I get the following Maven ERROR:

Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from A 1.0.0.qualifier to package org.apache.axis2.transaction 0.0.0.", "Unable to satisfy dependency from A 1.0.0.qualifier to package org.apache.axis2.addressing.i18n 0.0.0.", ...

Why does building projects in aggregated fashion causes this error, and what kind of workaround could be possible if that's a Tycho bug?

Though, there's no error if I leave only one module in aggregation POM (independently which one).

EDIT

Cannot reproduce with a small, similar multi-module sample. Which means there's something about my POM hierarchy.

EDIT2

Was able to reproduce with a small, similar multi-module sample, after including same set of dependencies (couple of axis2 & axiom libs).

EDIT3: Minimalistic Example

Now I'm wondering if the problem is about missing all thirdparties required by thirdpar

maven tycho
Edit
Report