Yes I guess so. Should I open an issue for an improvement?
Christian
Am 11.04.2012 17:20, schrieb Guillaume Nodet:
That's a non covered use case I'd say.
The plugin just adds the packages to the list of packages that needs to be
imported so I suppose the default naming rule is overridden in those cases.
On Wed, Apr 11, 2012 at 15:42, Christian Schneider
<[email protected]>wrote:
Hi all,
I have a bundle that is created using the maven-bundle-plugin. I also use
blueprint in the bundle.
I have an internal package named: org.apache.karaf.instance.**
core.internal
As the name implies I would like to not export or import this package. As
long as the package is not used in blueprint the defaults of the maven
bundle plugin work and it is treated as a private package.
The problem is that I define a bean in the blueprint.xml like:
<bean id="instanceService" class="org.apache.karaf.**
instance.core.internal.**InstanceServiceImpl">
</bean>
Then the bundle plugin creates an import for
"org.apache.karaf.instance.**core.internal".
Is this a bug?
Of course I can specify the package as private package but I would like to
go with the defaults in package naming and have a rather empty
configuration for the maven bundle plugin.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
users-unsubscribe@felix.**apache.org<[email protected]>
For additional commands, e-mail: [email protected]
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
