Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Odd behaviour with pomDependencies=consider and a features's dependencies

Hi Igor,

> Do you get build failure in the feature project or some other project
> that requires the feature? The latter is explained in [1]. The former
> will require small standalone reproducible test case.

yes, that might be it. In the same reactor, I have a eclipse-repository
that depends in the manifest-first feature, which in turn depends on the
POM first bundle.

That might also explain why the workaround (putting the dependency in
the parent POM) works: it's inherited by the eclipse-repository project
(and should really have been placed as a dependency in the
eclipse-repository project itself, even if that duplicates the
dependency information.)

Thanks a lot for your insights.


> [1]

Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

Back to the top