downstream-parent excludes a number of non-OSGi packages All of them can break catalogue loading.
Project: http://git-wip-us.apache.org/repos/asf/brooklyn-dist/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-dist/commit/f5c73391 Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-dist/tree/f5c73391 Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-dist/diff/f5c73391 Branch: refs/heads/master Commit: f5c7339158030c221de73b4203a655352fb008f4 Parents: 5e1c06b Author: Sam Corbett <[email protected]> Authored: Wed Dec 16 14:38:56 2015 +0000 Committer: Sam Corbett <[email protected]> Committed: Thu Dec 17 12:28:02 2015 +0000 ---------------------------------------------------------------------- usage/downstream-parent/pom.xml | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-dist/blob/f5c73391/usage/downstream-parent/pom.xml ---------------------------------------------------------------------- diff --git a/usage/downstream-parent/pom.xml b/usage/downstream-parent/pom.xml index c4d5a74..c1731fd 100644 --- a/usage/downstream-parent/pom.xml +++ b/usage/downstream-parent/pom.xml @@ -448,8 +448,29 @@ </supportedProjectTypes> <instructions> <!-- + Exclude packages used by Brooklyn that are not OSGi bundles. Including any + of the below may cause bundles to fail to load into the catalogue with + messages like "Unable to resolve 150.0: missing requirement [150.0] + osgi.wiring.package; (osgi.wiring.package=com.maxmind.geoip2)". + --> + <Import-Package> + !com.maxmind.geoip2.*, + !io.airlift.command.*, + !io.cloudsoft.winrm4j.*, + !javax.inject.*, + !org.apache.felix.framework.*, + !org.apache.http.*, + !org.jclouds.googlecomputeengine.*, + !org.osgi.jmx, + !org.python.*, + !org.reflections.*, + !org.w3c.tidy.*, + * + </Import-Package> + <!-- + Brooklyn-Feature prefix triggers inclusion of the project's metadata in the + server's features list. --> - <!-- Brooklyn-Feature prefix triggers inclusion of the project's metadata in the server's features list. --> <Brooklyn-Feature-Name>${project.name}</Brooklyn-Feature-Name> </instructions> </configuration>
