You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Alasdair Nottingham (JIRA)" <ji...@apache.org> on 2011/05/13 20:23:47 UTC

[jira] [Resolved] (ARIES-600) Do not preveint import of own exported API

     [ https://issues.apache.org/jira/browse/ARIES-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alasdair Nottingham resolved ARIES-600.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4

This was fixed in revision r1083059 by ARIES-610

> Do not preveint import of own exported API
> ------------------------------------------
>
>                 Key: ARIES-600
>                 URL: https://issues.apache.org/jira/browse/ARIES-600
>             Project: Aries
>          Issue Type: Bug
>          Components: JNDI
>    Affects Versions: 0.3
>            Reporter: Felix Meschberger
>             Fix For: 0.4
>
>
> The JNDI API project currently is setup to create a bundle which is intended to not import its own exported API:
>         <aries.osgi.import>
>             !org.osgi.service.jndi*,
>             *
>         </aries.osgi.import>
> This is superfluous since the API is not referenced at all by the other API classes in this bundle. In fact BND emits a warning about this package not actually being used.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira