bndtools/bndtools — Issue #339: bndtools makes too many types visible to Eclipse compiler
Author: bjhargrave
Created: 2012-02-09 16:32:55+00:00
State: open
Labels: High

I have a project whose -buildpath does not include visibility to a type. For example:

-buildpath	= \
ee.j2se;	version=1.5, \
org.osgi.test.support; version=project , \
org.osgi.service.subsystem;	version=project , \
org.osgi.util.tracker;	version=project , \
${junit}

does not include visibility to the org.osgi.framework package. Yet the code in the project references types in the org.osgi.framework package and successfully compiles. However, when I build the same project from ant on the command line, it fails spectacularly since the compiler has no visibility to types in the org.osgi.framework package.

It seems that bndtools is incorrectly providing compiler visibility to types which are visible to dependent projects. Doing this breaks fidelity between eclipse and offline ant builds since I can commit changes which compile in eclipse yet fail during the offline build.