Re: [tycho-user] Spurious warnings when importing from a bundle with a B

["Sievers, Jan" <jan.sievers@xxxxxxx>]

This warning is about the maven compile classpath only.

That is the compile classpath which other non-OSGi aware maven plugins will see if you integrate them into your tycho build (findbugs, PMD, javadoc,...).
The maven compile classpath has no such thing as an OSGi package visibility concept, so it's an approximation.
And this approximation does not support nested dir classpath entries.

For the tycho JDT compiler, package-level imports are mapped to compiler package visibility rules.
That means all entries in Bundle-Classpath are put on the compiler classpath and then package visibilty rules are applied on top.
So even if conf/ is on the classpath, you won't be able to compile against packages you didn't import.

For details see https://issues.sonatype.org/browse/TYCHO-483 

Regards
Jan

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Eric Jain
Sent: Mittwoch, 28. September 2011 19:34
To: tycho-user
Subject: [tycho-user] Spurious warnings when importing from a bundle with a Bundle-ClassPath?

The bundle "bar" has a dir "conf/" in its Bundle-ClassPath. When a
bundle such as "foo" imports a package from "bar", Tycho 0.13.0
generates the following warning:

[INFO] Resolving target platform for project MavenProject:
foo:1.0.0-SNAPSHOT @ bundles/foo/pom.xml
[WARNING] Dependency from bundles/foo to nested classpath entry
bundles/bar/conf can not be represented in Maven model and will not be
visible to non-OSGi aware Maven plugins

I don't think bar's conf dir should be in foo's classpath, OSGi or not?
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user