Community
Participate
Working Groups
If a bundle fails to resolve and the unsatisfied constraint is a NativeCodeSpecification, then we end up reporting a misleading error message: Bundle org.eclipse.swt.carbon.macosx: Host plug-in Bundle-NativeCode_0.0.0 has not been found.
As part of this, we need to be able to ignore resolution errors that are caused by filters not matching if we aren't building for that platform.
Created attachment 142958 [details] patch Patch fixes logging around Bundle-NativeCode. Tom, can you look at BundleHelper.getFilter(BundleDescription) It creates a filter by combining the Eclipse-PlatformFilter with the Bundle-NativeCode selection-filters. It assumes each filter string is surrounded with '(' ')'. Once this is in, I will start looking at bug 284784 by replacing calls to BundleDescription.getPlatformFilter() with this getFilter.
(In reply to comment #2) > Tom, can you look at BundleHelper.getFilter(BundleDescription) > It creates a filter by combining the Eclipse-PlatformFilter with the > Bundle-NativeCode selection-filters. It assumes each filter string is > surrounded with '(' ')'. > This looks good. It is valid to assume each filter string is surrounded with '(' ')' > Once this is in, I will start looking at bug 284784 by replacing calls to > BundleDescription.getPlatformFilter() with this getFilter. > This patch seems to do part of this already. I guess that is just enough to get a good Bundle-NativeCode resolution errors?
(In reply to comment #3) > This patch seems to do part of this already. I guess that is just enough to > get a good Bundle-NativeCode resolution errors? > Yes, we don't report errors on bundles that were only unresolved because they didn't match one of the configs (os,ws,arch) that we are building. I have released this patch to 3.6 head