Hello, On version 4.2.0 of maven-bundle-plugin, I am having trouble generating a manifest which imports its own exports with the proper version range.
For example, suppose my bundle defines the following class
package com.example.osgi.dependee;
import org.osgi.framework.ServiceListener;
import com.example.osgi.dependency.InternalDependency;
public class Dependee {
private InternalDependency internalDependency;
private ServiceListener externalDependency;
}
and also defines com.example.osgi.dependency.InternalDependency (whose
implementation doesn’t matter here). With default configuration, the generated
manifest headers are
Export-Package:
com.example.osgi.dependee;version="1.0.0",
com.example.osgi.dependency;version="1.0.0"
Import-Package:
com.example.osgi.dependency,
org.osgi.framework;version="[1.9,2)"
Is there any way to either:
1) stop com.example.osgi.dependency from showing up in the imports, without
having to explicitly name it?
2) coerce maven-bundle-plugin into generating the expected version range of
[1.0,2)?
Example project is attached.
Thanks,
Colin P. Hill
Application Developer, Development and Integration Services
[email protected]<mailto:[email protected]> | pronouns: he or
they<http://pronoun.is/he?or=they/.../themself>
PJM Interconnection | 2750 Monroe Blvd. | Audubon, PA 19403
<<attachment: unversioned-self-imports.zip>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
