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

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

Maven project dependency model is more coarse-grained compared to OSGi,
it is not possible to express Import-Package in maven model nor there is
support for dependencies with nested sub-entries.

Currently Tycho approximates Import-Package as dependency on each bundle
classpath entry, regardless if the entry provides requested package or
not. Tycho extracts nested jars to a temporary directory, but nested
directories are ignored with the warning you see.

Personally, I think current behaviour is good enough, given that Tycho
can't perfectly represent OSGi dependencies in Maven project model in
all cases, but if you feel strongly about improving current behaviour
please provide a quality patch and we'll consider it.

--
Regards,
Igor


On 11-09-28 1:34 PM, Eric Jain wrote:
> 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