There is also the possibility to add the missing bundle via extra dependency configuration, directly to the failing bundle:
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho.version}</version>
<configuration>
<dependency-resolution>
<extraRequirements>
<requirement>
<type>eclipse-plugin</type>
<id>org.eclipse.ui.ide</id>
<versionRange>0.0.0</versionRange>
</requirement>
</extraRequirements>
</dependency-resolution>
</configuration>
</plugin>
regards
Carsten
Von: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] Im Auftrag von Oberlies, Tobias
Gesendet: Freitag, 25. Januar 2013 10:38
An: Tycho user list
Betreff: Re: [tycho-user] Target resolution and Import-Package
So org.eclipse.ui.dialogs is a split package. In this case, the recommendation is to use Require-Bundle instead. OSGi can handle imports on split packages correctly, but p2 doesn’t [1], so the recommendation in the Eclipse context is to avoid them.
Regards
Tobias
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=360659
I try to build a plugin with the imported package "org.eclipse.ui.dialogs", but the build fails by stating:
Bundle plugin.b - Missing Constraint: Import-Package: org.eclipse.ui.dialogs; version="0.0.0"
My first reaction was to check if one of the plugins of my target platform export this package.
I find out that both "org.eclipse.ui.ide" and "org.eclipse.ui.workbench" do so.
In the build log i can read something like "RESOLVED org.eclipse.ui.workbench ...", but the resolution of "org.eclipse.ui.dialogs" still fails.
Any idea on how go around this ?
I attached a sample to this mail demonstrating the issue.
Thanks in advance for your help.