[VOTE] Felix framework and main 3.0.1 subproject releases
I would like to call a vote on the following subproject releases: framework 3.0.1 main 3.0.1 main.distribution 3.0.1 We solved the following issue in this release: ** Bug * [FELIX-2401] - NPE in org.apache.felix.framework.FilterImpl.DictionaryCapability.getAttribute(String) Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-052 You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 052 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments)
Re: Unable to download Felix
Looks like our download page is broken. Can somebody jump in and fix this? You can download stuff from http://www.apache.org/dist/felix/ for now. Sorry, we'll fix it. Thanks for reporting. regards, Karl On Mon, Jun 14, 2010 at 9:40 PM, Ken Gilmer wrote: > Hi, I'm just trying to download Felix from > http://felix.apache.org/site/downloads.cgi, but no matter what mirror I > select I get: > > > Page Not Found > > The page you were trying to reach could not be found. This could be because: > > - The page does not exist. > - The page exists, but you do not have permission to view it. > > > > For this URL: > > https://cwiki.apache.org/confluence/display/FELIX/[preferred]/felix/org.apache.felix.main.distribution-3.0.0.zip > > Halp! > > thx > -ken > -- Karl Pauls karlpa...@gmail.com
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878679#action_12878679 ] Guillaume Nodet commented on FELIX-2409: Splitting the jre exported packages sounds good to me. Wanna provide a patch that would do that ? > 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.
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ 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.
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878627#action_12878627 ] Guillaume Nodet commented on FELIX-2409: Let's give you a concrete example. if we just put in the patch you propose, you wouln't be able to deploy the JAX-WS api provided by http://www.springsource.com/repository/app/bundle/version/detail?name=com.springsource.com.sun.xml.ws&version=2.1.3 for example, because the package versioning won't work. So you'd have to deploy another bundle anyway. Then there's really no reason for exporting the one from the JRE in the first place, it will only fragment the space more. 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 Currently, we've mostly focused on the second way. We may want to reconsider that, but has to be discussed furtther i think. Btw, javax.annotation can easily be provided using the following bundle: http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-annotation_1.1_spec/1.0/geronimo-annotation_1.1_spec-1.0.jar or from inside karaf: mvn:org.apache.geronimo.specs/geronimo-annotation_1.1_spec/1.0 > 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.
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878615#action_12878615 ] Jean-Philippe CLEMENT commented on FELIX-2409: -- Ok, I'm not sure to have the full picture. But, why not relying on the jre, as it is the base API and what is provided by the jre API is expected to be usable. This would imply having Karaf config.properties with all jre packages set. Then it's up to the user to remove config.properties lines that does not match his needs. I guess it provides the same functionality... just a matter on what to expect by default, isn't it? > 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.
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878611#action_12878611 ] Guillaume Nodet commented on FELIX-2409: It's not for karaf internal needs. Let me try to explain. Let say you want to use JAX-WS, javax.scripting, SAAJ, or any specification that usually leverage META-INF/services discovery mechanism. Some of those specs are provided by JDK 1.6 and maybe some new specs will be provided by JDK 1.7 in the future. If you come from a Java SE environment, you're used to using those API. If you want to drop a new provider, you just add it to your classpath and it will be used. Now in an OSGI environment, things don't really work that way. The worst thing is that if we offer those APIs from the JRE, the user has *no way* to change the provider. So that 's the main problem i'd like to avoid. It's about making things work in OSGi ... That's why Karaf try to avoid exporing any package that can be provided by other means (such as javax.xml.ws, javax.scripting, javax.jws, javax.activation). All those can be provided by additional bundles. In addition, a common problem with those packages is that they aren't versioned, which can also cause problems if you have a bundle requiring a version > 0.0. Now, as I said, I think it's fair to tweak the configuration for you own environment. Last, when JDK 1.7 comes out, we'll have to check it and write a new config for it I suppose. > 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.
[jira] Updated: (FELIX-2306) ClassCastException in Wrapper.unwrap() when calling Resolver.add(x implements Resource)
[
https://issues.apache.org/jira/browse/FELIX-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated FELIX-2306:
---
Attachment: FELIX-2306.patch
Proposed patch for this issue. The patch code will attempt to covert osgi
Resource to felix Resource by copying the data. This might not work in all
cases but should in most.
> ClassCastException in Wrapper.unwrap() when calling Resolver.add(x implements
> Resource)
> ---
>
> Key: FELIX-2306
> URL: https://issues.apache.org/jira/browse/FELIX-2306
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
>Affects Versions: bundlerepository-1.6.0
> Environment: Windows 7, Java 6
>Reporter: Mark Nuttall
> Attachments: FELIX-2306.patch
>
>
> This looks like a regression from OBR 1.4.1 to 1.6. I have a resource class
> that implements org.osgi.service.obr.Resource. When I call
> Resolver.add(myResource) I
> get a ClassCastException:
> Caused by: java.lang.ClassCastException:my.resources.MyResource
> incompatible with
> org.apache.felix.bundlerepository.impl.wrapper.ResourceWrapper
>at
> org.apache.felix.bundlerepository.impl.wrapper.Wrapper.unwrap(Wrapper.java:59)
>at
> org.apache.felix.bundlerepository.impl.wrapper.ResolverWrapper.add(ResolverWrapper.java:40)
>at my.provisioning.impl.OBRProvisioner.resolve(OBRProvisioner.java:496)
> Looking at Wrapper.java:
>public static Resource unwrap(org.osgi.service.obr.Resource resource) {
>return ((ResourceWrapper) resource).resource;
>}
> I've passed in a class that implemented obr.Resource which this code is
> attempting to cast to ResourceWrapper: this fails. We got there via,
> // ResolverWrapper.java
> public void add(org.osgi.service.obr.Resource resource) {
>resolver.add(Wrapper.unwrap(resource));
>}
> At no time was my Resource wrapped before it was unwrapped.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878606#action_12878606 ] Jean-Philippe CLEMENT commented on FELIX-2409: -- "karaf is set up is that all applications can run independantly of being run on JDK 1.5 or 1.6" Well, in that case, why having two parts - one for jre-1.5 another for jre-1.6 - in the configuration file? ...what would happen for java 1.7 new features, will Karaf be blocked on java 1.5 forever? "it would fail because we currently rely on servicemix specs" So, if I understand correctly, karaf internal constraints interact with user setup. It would be great if Karaf could be as transparent as possible. Why not having two configurations: one for karaf internal needs and one for the user? > 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.
Re: [jira] Commented: (FELIX-2409) javax.annotation not exported
On Mon, Jun 14, 2010 at 15:48, Jean-Baptiste Onofré wrote: > Thanks for the update Bengt, > > but I'm a little bit surprised as we have two standard package set: one for > jre-1.5 and one for jre-1.6. > > I'd rather not export any spec than can be provided with a better osgi-enhanced version, such as the one we provide in ServiceMix. > Note that javax.transaction is exported with a mandatory attribute: > javax.transaction; javax.transaction.xa; partial=true;mandatory:=partial, \ > in both jre 1.5 and 1.6. > Right, but this is a hack required in order to have JTA work in OSGi. If you look at the content of the package in the JRE, it only provides a few classes, but those are used by JDBC. Also, if you look more closely, you should see a boot delegation to javax.transaction too. This is required in order to be able to deploy a javax.transaction package that people can use, while ensuring that the classes from the JRE will always be used, but that noone can wire on to the package provided by the JRE ... A bit complicated, but it seems to work ... As for javax.annotation and javax.annotation.processing, those two packages may be considered differently as javax.scripting. Is there any bundle other than the JRE that can provide those packages ? Are they really tied to the JRE so that if we use a different version, it won't work ? > > Regards > JB > > > On 06/14/2010 03:43 PM, Bengt Rodehav wrote: > >> I had the same problem a while back. I was informed that since Karaf also >> supports Java 1.5 (which doesnt have these packages), they should not by >> default be imported by Karaf. >> >> See the following: >> >> http://old.nabble.com/Karaf-1.4.0-and-ActiveMQ-5.3.1-td28191404.html >> >> /Bengt >> >> 2010/6/14 Jean-Baptiste Onofré (JIRA) >> >> >>>[ >>> >>> https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878569#action_12878569 >>> ] >>> >>> Jean-Baptiste Onofré commented on FELIX-2409: >>> - >>> >>> It sounds good for me. >>> >>> 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. >>> >>> >>> >> -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: [VOTE] webconsole-3.0.2, bundlerepository-1.6.4 and karaf-1.6.2
Yeah, I haven't released it in jira yet, so it will be done at this point. If anyone want to fix any of those issues in the coming 24/48 hours, I can wait before cutting a new release, else I'll reschedule those to the next release. On Mon, Jun 14, 2010 at 08:09, Carsten Ziegeler wrote: > Haven't looked at the artifact yet, but there are three open issues for > the webconsole 3.0.2 release. Not sure if they should have been fixed > before a release or not, but in any case they should be moved to another > release :) > > Regards > Carsten > > Guillaume Nodet wrote > > I would like to call a new vote on the following subproject releases: > > > > webconsole 3.0.2 > > bundlerepository 1.6.4 > > karaf 1.6.2 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-049/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 049 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 There's a problem (please provide specific comments) > > > > > -- > Carsten Ziegeler > cziege...@apache.org > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878594#action_12878594 ] Guillaume Nodet commented on FELIX-2409: It doesn't for me. Currently, the way karaf is set up is that all applications can run independantly of being run on JDK 1.5 or 1.6. If we do that for javax.annotation, we'd have to do that for javax.scripting for example, but in that case, it would fail because we currently rely on servicemix specs, which are enhanced for osgi, so this would break as soon as you use jdk 1.6. So i'd rather advise you to tweak the karaf config in order to suit your needs, if your target jre is jdk 1.6 only. > 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.
Re: [VOTE] webconsole-3.0.2, bundlerepository-1.6.4 and karaf-1.6.2
Haven't looked at the artifact yet, but there are three open issues for the webconsole 3.0.2 release. Not sure if they should have been fixed before a release or not, but in any case they should be moved to another release :) Regards Carsten Guillaume Nodet wrote > I would like to call a new vote on the following subproject releases: > > webconsole 3.0.2 > bundlerepository 1.6.4 > karaf 1.6.2 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-049/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 049 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 There's a problem (please provide specific comments) > -- Carsten Ziegeler cziege...@apache.org
Re: [jira] Commented: (FELIX-2409) javax.annotation not exported
Thanks for the update Bengt, but I'm a little bit surprised as we have two standard package set: one for jre-1.5 and one for jre-1.6. Note that javax.transaction is exported with a mandatory attribute: javax.transaction; javax.transaction.xa; partial=true;mandatory:=partial, \ in both jre 1.5 and 1.6. Regards JB On 06/14/2010 03:43 PM, Bengt Rodehav wrote: I had the same problem a while back. I was informed that since Karaf also supports Java 1.5 (which doesnt have these packages), they should not by default be imported by Karaf. See the following: http://old.nabble.com/Karaf-1.4.0-and-ActiveMQ-5.3.1-td28191404.html /Bengt 2010/6/14 Jean-Baptiste Onofré (JIRA) [ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878569#action_12878569] Jean-Baptiste Onofré commented on FELIX-2409: - It sounds good for me. 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.
[jira] Updated: (FELIX-2401) NPE in org.apache.felix.framework.FilterImpl.DictionaryCapability.getAttribute(String)
[
https://issues.apache.org/jira/browse/FELIX-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-2401:
---
Fix Version/s: framework-3.0.1
(was: framework-3.2.0)
> NPE in
> org.apache.felix.framework.FilterImpl.DictionaryCapability.getAttribute(String)
> --
>
> Key: FELIX-2401
> URL: https://issues.apache.org/jira/browse/FELIX-2401
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-3.0.0
>Reporter: Clement Escoffier
>Assignee: Richard S. Hall
> Fix For: framework-3.0.1
>
>
> The getAttribute method can throw an NPE if the key is not contained into in
> map (m_map)
> {code}
> if (m_dict != null)
> {
> if (m_map != null)
> {
> key = (String) m_map.get(name); <= returns null
> }
> value = m_dict.get(key); <= NPE here, because the comparator
> to null.toString()
> }
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (FELIX-2409) javax.annotation not exported
I had the same problem a while back. I was informed that since Karaf also supports Java 1.5 (which doesnt have these packages), they should not by default be imported by Karaf. See the following: http://old.nabble.com/Karaf-1.4.0-and-ActiveMQ-5.3.1-td28191404.html /Bengt 2010/6/14 Jean-Baptiste Onofré (JIRA) > >[ > https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878569#action_12878569] > > Jean-Baptiste Onofré commented on FELIX-2409: > - > > It sounds good for me. > > > 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. > >
[jira] Commented: (FELIX-2409) javax.annotation not exported
[ https://issues.apache.org/jira/browse/FELIX-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878569#action_12878569 ] Jean-Baptiste Onofré commented on FELIX-2409: - It sounds good for me. > 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.
[jira] Created: (FELIX-2409) javax.annotation not exported
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.
RE: Error with UPnP Base driver
Ok thanks a lot Stefano I ll try this. Kind regards, Charbel > Date: Fri, 11 Jun 2010 12:09:25 +0200 > From: le...@apache.org > Subject: Re: Error with UPnP Base driver > To: dev@felix.apache.org > > Dear Charbel, > > Sorry for the late answer, I really believe that is a problem related > from the wiring. Actually, the problem is not caused by bundle 20 and > 22 but to others bundle on your configuration. If you want to find the > source of the problem you should inspect the import/export tree for the > packages org.xml.sax and org.xml.sax > > Nevertheless, I believe that easier for you to force the wiring of the > org.w3c.dom and org.xml.sax packages of the "UPnP Base Driver" to the > framework bundle. > If you want to try this solution, you have to: > 1 - download the UPnP bundle sources > 2 - modify the pom.xml by replacing the content of the > tag > org.osgi.*, > javax.xml.parsers;bundle-symbolic-name=org.apache.felix.framework, > org.w3c.dom;bundle-symbolic-name=org.apache.felix.framework, > org.xml.sax;bundle-symbolic-name=org.apache.felix.framework > 3 - package the bundle with maven, by executing mvn install > 4 - replace the UPnP Base Driver bundle with the one just created, that > is located inside target folder > > As additional note, you should be aware that "inspect" command shows > only the actual wiring of the bundle which may be different from the > content of the Import/Export-Pacakge headers of the bundle you are > inspecting ( Richard would you mind to correct me if I'm wrong?) > > Ciao, > Stefano "Kismet" Lenzi > > On 02/06/2010 11.18, charbel el_kaed wrote: > > > > > > Hi Stefano, > > > > I inspected the packages and this is what I found. (The inspection result > > are below) > > > > Bundle 20 ONLY imports org.w3c.dom and org.xml.sax > > while Bundle 22 imports and exports org.xml.sax > > > > In your previous reply you mentioned the correct configuration as: > > I think that the correct configuration of bundle 20 and 22 are: > > - bundle 20 and 22 import and export the packages: org.w3c.dom and > > org.xml.sax > > - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax > > > > > > So I am not sure if it is correct. I am really new to this. > > I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page > > 52 > > > > -> inspect package c 20 > > org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports > > packages: > > -- > > org.jdom; version=0.0.0 > > org.jdom.adapters; version=0.0.0 > > org.jdom.filter; version=0.0.0 > > org.jdom.output; version=0.0.0 > > org.jdom.output.sax; version=0.0.0 > > org.jdom.output.stax; version=0.0.0 > > org.jdom.input.stax; version=0.0.0 > > > > -> inspect package r 20 > > org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports > > packages: > > -- > > javax.xml.stream; version=1.6.0 -> org.apache.felix.framework [0] > > org.xml.sax.ext; version=1.6.0 -> org.apache.felix.framework [0] > > org.w3c.dom; version=2.0.0 -> org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi > > [19] > > > > org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21] > > org.xml.sax.helpers; version=2.0.2 -> > > org.soa4d.forge.osgi.xml.sax.over.pull.bri > > dge.osgi [22] > > org.xquark.serialize; version=1.1.1 -> > > org.soa4d.forge.osgi.xml.xquare.serializi > > ng [23] > > > > # > > -> inspect package c 22 > > org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages: > > - > > org.xml.sax.ext; version=2.0.2 > > org.xml.sax.helpers; version=2.0.2 > > > > -> inspect package r 22 > > org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages: > > - > > org.xmlpull.v1; version=1.1.2 -> > > org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15] > > org.xml.sax; version=2.0.2 -> org.soa4d.forge.osgi.xml.sax2.api.osgi [21] > > > > > > Kind regards, > > Charbel. > > > > > > > > > >> Date: Tue, 1 Jun 2010 14:54:41 +0200 > >> From: le...@apache.org > >> Subject: Re: Error with UPnP Base driver > >> To: dev@felix.apache.org > >> > >> On 01/06/2010 1.58, charbel el_kaed wrote: > >>> > >>> Hi Stefano, > >>> > >>> Thanks for your reply. > >>> > >>> I can't actually touch those bundles. Is there another way to do so ? > >> > >> Have you checked if the hypothesis regarding the import/export headers > >> of bundle 20 and 22 are correct? If they aren't then the source of the > >> problem is somewhere else. > >> > >> If the hypothesis are correct then you can change the import-package > >> header of the "UPnP Base Driver" in order to force the loading of the > >> classes from the bundle 0 by means
[jira] Commented: (FELIX-2408) Karaf download link is not correct on the Felix download page
[ https://issues.apache.org/jira/browse/FELIX-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878548#action_12878548 ] Jean-Baptiste Onofré commented on FELIX-2408: - The karaf download link should look like: http://repo1.maven.org/maven2/org/apache/felix/karaf/apache-felix-karaf/1.6.0/apache-felix-karaf-1.6.0.tar.gz using maven repo or the equivalent using the apache download portal. > Karaf download link is not correct on the Felix download page > - > > Key: FELIX-2408 > URL: https://issues.apache.org/jira/browse/FELIX-2408 > Project: Felix > Issue Type: Bug > Components: Karaf >Reporter: Jean-Baptiste Onofré > > If you go on the Felix download page: > http://felix.apache.org/site/downloads.cgi > the karaf download link is: > https://cwiki.apache.org/confluence/display/FELIX/%5Bpreferred%5D/felix/apache-felix-karaf-1.6.0.tar.gz > whereas it should be: > http://felix.apache.org/site/downloads.cgi?Preferred=http%3A%2F%2Fmirror.ibcp.fr%2Fpub%2Fapache -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2408) Karaf download link is not correct on the Felix download page
Karaf download link is not correct on the Felix download page - Key: FELIX-2408 URL: https://issues.apache.org/jira/browse/FELIX-2408 Project: Felix Issue Type: Bug Components: Karaf Reporter: Jean-Baptiste Onofré If you go on the Felix download page: http://felix.apache.org/site/downloads.cgi the karaf download link is: https://cwiki.apache.org/confluence/display/FELIX/%5Bpreferred%5D/felix/apache-felix-karaf-1.6.0.tar.gz whereas it should be: http://felix.apache.org/site/downloads.cgi?Preferred=http%3A%2F%2Fmirror.ibcp.fr%2Fpub%2Fapache -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2141) Add features:info command
[
https://issues.apache.org/jira/browse/FELIX-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated FELIX-2141:
---
Summary: Add features:info command (was: Add features:desc, features:tree
commands)
Assignee: Guillaume Nodet (was: Chris Custine)
> Add features:info command
> -
>
> Key: FELIX-2141
> URL: https://issues.apache.org/jira/browse/FELIX-2141
> Project: Felix
> Issue Type: Improvement
> Components: Karaf
>Affects Versions: karaf-1.4.0
>Reporter: Łukasz Dywicki
>Assignee: Guillaume Nodet
> Fix For: karaf 1.8.0
>
> Attachments: desc_tree-commands.patch, info-command.patch
>
>
> Currently there is no way to check contents of the feature. It's also hard to
> determine what dependencies feature has.
> First command - describes feature using Feature instance. Command by default
> displays info about configuration (-c), dependencies (-d) and bundles (-b
> option) in feature.
> {code}
> ka...@root> features:desc payment-service
> Description of payment-service 1.0.0.SNAPSHOT feature
>
> Feature has no configuration.
> Feature dependens on:
> datasource 0.0.0
> dataaccess 0.0.0
> activemq-camel 0.0.0
> camel-jetty 0.0.0
> contract 0.0.0
> Feature contains followed bundles:
> mvn:org.code-house.esb.payment/engine/1.0.0.SNAPSHOT
> mvn:org.code-house.esb.payment/binding/1.0.0.SNAPSHOT
> mvn:org.code-house.esb.payment/persistence/1.0.0.SNAPSHOT
> {code}
> Second command displays features tree. If user will pass -b parameter feature
> bundles will be attached to tree.
> {code}
> ka...@root> features:tree payment-service
> payment-service 1.0.0.SNAPSHOT
> datasource 0.0.0
>activemq 0.0.0 *
>postgresql 8.3
>spring 2.5.6.SEC01
>commons-dbcp 0.0.0
> dataaccess 1.0.0.SNAPSHOT
>domain 1.0.0.SNAPSHOT
> persistence-api 1.0.0
>hibernate 0.0.0
> persistence-api 1.0.0
> activemq-camel 5.3.0-fuse-01-00
> camel-jetty 0.0.0 *
> contract 1.0.0.SNAPSHOT
> Tree contains 2 unresolved dependencies
> * means that node declares dependency but the dependant feature is not
> available.
> {code}
> {code}
> ka...@root> features:tree domain
> domain 1.0.0.SNAPSHOT
> persistence-api 1.0.0
> {code}
> {code}
> ka...@root> features:tree -b domain
> domain 1.0.0.SNAPSHOT
> + mvn:org.code-house/domain/1.0.0.SNAPSHOT
> + mvn:org.code-house.security/domain/1.0.0.SNAPSHOT
> \ mvn:org.code-house.shippingstock/domain/1.0.0.SNAPSHOT
> persistence-api 1.0.0
> \ mvn:javax.persistence/com.springsource.javax.persistence/1.0.0
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2407) Use docbook for Karaf's manual
Use docbook for Karaf's manual -- Key: FELIX-2407 URL: https://issues.apache.org/jira/browse/FELIX-2407 Project: Felix Issue Type: Task Components: Karaf Reporter: Guillaume Nodet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[CANCEL] [VOTE] webconsole-3.0.2, bundlerepository-1.6.4 and karaf-1.6.2
You're right. I'll recut a 3.1.0 release respin a vote. I hereby cancel this vote. On Mon, Jun 14, 2010 at 08:59, Felix Meschberger wrote: > Hi, > > On 14.06.2010 08:53, Felix Meschberger wrote: > > Hi, > > > > On 12.06.2010 08:43, Guillaume Nodet wrote: > >> I would like to call a new vote on the following subproject releases: > >> > >> webconsole 3.0.2 > > > > I have to admit, that this release vote comes a bit as a surprise: > > Hmpf, should have read my mails first. Sorry for that. Not much reason > for surprise, still I think the export version is a blocker to me > because it may create problems for importers down the road. > > Regards > Felix > > > there > > are still three open issues targeted at this release (this is not > > dramatic, though). > > > > The real problem is, that this release candidate has an extended > > exported API (compared to the webconsole 3.0.0 release) still exported > > as 3.0, which should really be 3.1. This IMHO is a blocker for this > release. > > > > Regards > > Felix > > > >> bundlerepository 1.6.4 > >> karaf 1.6.2 > >> > >> Staging repository: > >> https://repository.apache.org/content/repositories/orgapachefelix-049/ > >> > >> You can use this UNIX script to download the release and verify the > >> signatures: > >> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > >> > >> Usage: > >> sh check_staged_release.sh 049 /tmp/felix-staging > >> > >> Please vote to approve this release: > >> > >> [ ] +1 Approve the release > >> [ ] -1 There's a problem (please provide specific comments) > >> > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: [VOTE] webconsole-3.0.2, bundlerepository-1.6.4 and karaf-1.6.2
Hi, On 14.06.2010 08:53, Felix Meschberger wrote: > Hi, > > On 12.06.2010 08:43, Guillaume Nodet wrote: >> I would like to call a new vote on the following subproject releases: >> >> webconsole 3.0.2 > > I have to admit, that this release vote comes a bit as a surprise: Hmpf, should have read my mails first. Sorry for that. Not much reason for surprise, still I think the export version is a blocker to me because it may create problems for importers down the road. Regards Felix > there > are still three open issues targeted at this release (this is not > dramatic, though). > > The real problem is, that this release candidate has an extended > exported API (compared to the webconsole 3.0.0 release) still exported > as 3.0, which should really be 3.1. This IMHO is a blocker for this release. > > Regards > Felix > >> bundlerepository 1.6.4 >> karaf 1.6.2 >> >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachefelix-049/ >> >> You can use this UNIX script to download the release and verify the >> signatures: >> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh >> >> Usage: >> sh check_staged_release.sh 049 /tmp/felix-staging >> >> Please vote to approve this release: >> >> [ ] +1 Approve the release >> [ ] -1 There's a problem (please provide specific comments) >>
