Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <26439752.81121276535353129.JavaMail.jira@thor>
Date: Mon, 14 Jun 2010 13:09:13 -0400 (EDT)
From: "Jean-Philippe CLEMENT (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-2409) javax.annotation not exported
In-Reply-To: <33009800.77591276521552956.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878638#action_12878638 ] 

Jean-Philippe CLEMENT commented on FELIX-2409:
----------------------------------------------

"I guess the choice comes down to: 
  * export everything from the jre and let the user deal with nasty issues when / if they come up 
  * export a minimal set and force the user to either tweak the config (meaning they kinda have a good knowledge of osgi) or make them deploy the needed bundles"

Correct.

I don't know why the JAX api you mentioned would fail. I guess it is a manifest issue. I'm not too sure if this is up to Karaf - a shared framework - to fix user bundles issues ;)

Moreover, I would say, if I'm using the regular java api in a regular way, I'm expecting it to work also in Karaf... which is not the case (as it needs a little of configuration).

But that's true this is not a big deal. Maybe, if the "minimal export" case is still retained, I would suggest to move the export part in some external configuration files. For instance:
default.export.properties
jre16.export.properties
myadhoc.export.properties
...

where  config.properties would contain a reference to the used export file instead of "jre-X.Y" parts:
felix.export=default.export.properties

which could easily changed to:
felix.export=jre16.export.properties

and *.export.properties would contain ad'hoc exports:
 javax.accessibility, \
 javax.activity, \
 javax.crypto, \
 javax.crypto.interfaces, \
 javax.crypto.spec, \
 javax.imageio, \
 ...

What do you think?

> javax.annotation not exported
> -----------------------------
>
>                 Key: FELIX-2409
>                 URL: https://issues.apache.org/jira/browse/FELIX-2409
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>    Affects Versions: karaf 1.6.0
>         Environment: Windows / jre-1.6
>            Reporter: Jean-Philippe CLEMENT
>
> Karaf config.properties does not export "jre-1.6" javax.annotation and javax.annotation.processing standard packages.
> As they are part of the java 1.6 API it sounds normal to have them imported by default:
>  javax.annotation, \
>  javax.annotation.processing, \
> Would it be possible to fix this?
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.