Re: [WebConsole] breaking out localizations
+1 Carsten 2013/1/12 Felix Meschberger fmesc...@adobe.com: Hi, Ping ? Unless someone speaks up, I plan on applying the patch for FLEIX-3834 [1] sometime next week. Regards Felix [1] https://issues.apache.org/jira/browse/FELIX-3834 Am 31.12.2012 um 15:12 schrieb Felix Meschberger: Hi The Web Console currently embeds the english (default) labels as well as bulgarian, german, and russian translations. Other languages/translations may be added as fragments to the web console. To ease translation work and selection of supported languages, I suggest we also break out the existing translations into separate fragment bundles. Each fragment basically has the translation strings as well as the flag representing the language. I have created FELIX-3834 [1] with an attached patch explaining the changes. WDYT ? Regards Felix -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.2
Hi Arjun; Sorry to be late, here is my vote: I did the following: 1) I did a quick successful test: I defined some components using both declarative service and dependency manager; I also managed to have a circular dependency: ... and the plugin discovered the cycle ! 2) in the org.apache.felix.servicediagnostics.plugin-0.1.2.jar, the changelog is missing (but I think this does not block the release, isn't it ?) 3) the sample maven project does not seem to compile, and I had to manually download the required artifacts in order to do a test (org.apache.servicemix.bundles.scala-library-2.9.1_3.jar, etc ...). it would be nice if you could add in the README.txt the list of exact maven dependencies (scala, etc ...). Unless I missed something in the license/dependencies file, I think it's ok: +1 (binding) regards /Pierre On Fri, Jan 4, 2013 at 11:08 AM, Arjun Panday arjun.pan...@alcatel-lucent.com wrote: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. This new version features better integration with the webconsole architecture, proper handling of service properties and detection of circular dependencies between services across dependency frameworks. It's also lighter as it doesn't embed the scala library anymore. A sample launcher with the required dependencies can be found here: http://svn.apache.org/repos/**asf/felix/trunk/webconsole-** plugins/servicediagnostics/**run.shhttp://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh Changes from 0.1.1 to 0.2.0 --- ** Bug * [FELIX-3764] servicediagnostics plugin does not append the correct context path info to it's javascript files * [FELIX-3767] servicediagnostics plugin should properly handle service properties ** Improvement * complete rewrite * [FELIX-3768] servicediagnostics plugin should detect circular dependencies * doesn't embedd scala, json or jquery anymore ** Backward compatibility * broken: plugin API changed There are still some outstanding issues: https://issues.apache.org/**jira/browse/FELIX-3769https://issues.apache.org/jira/browse/FELIX-3769(I'll change to the new plugin directory structure when it's released) Staging repository: https://repository.apache.org/**content/repositories/**orgapachefelix-098/https://repository.apache.org/content/repositories/orgapachefelix-098/ https://repository.apache.org/**content/repositories/**orgapachefelix-093/https://repository.apache.org/content/repositories/orgapachefelix-093/(parent pom) You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/**asf/felix/trunk/check_staged_**release.shhttp://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/felix-staging Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun
Re: [jira] [Commented] (FELIX-3861) Set felix.webconsole.category on Web Console plugins
Hi Felix, I was trying to cut a release of the service diagnostics plugin and I see your issue 3861. I was waiting for the categorized webconsole to be released to use the feature. When do you plan to release the new webconsole? Should I postpone my release for this? Also what would be a suitable category? (my guess is OSGi, like the DS plugin) thanks, Arjun Le 21/01/2013 22:32, Felix Meschberger (JIRA) a écrit : [ https://issues.apache.org/jira/browse/FELIX-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559119#comment-13559119 ] Felix Meschberger commented on FELIX-3861: -- Defined category in gogo plugin in Rev. 1436628 and in the ds plugin in Rev. 1436630. Set felix.webconsole.category on Web Console plugins Key: FELIX-3861 URL: https://issues.apache.org/jira/browse/FELIX-3861 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-ds-plugin-1.0.0, webconsole-4.0.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-gogo-plugin-1.0.0, webconsole-ds-plugin-1.0.2, webconsole-4.0.2 The Web Console supports categories and our plugins in the webconsole-plugins folder should use them. The SimpleWebConsolePlugin should also use the getter methods to get the title, label, and optional category for registration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release ServiceDiagnostics Webconsole Plugin version 0.1.2
Ups, I missed this one as well... +1 Carsten 2013/1/22 Pierre De Rop pierre.de...@gmail.com: Hi Arjun; Sorry to be late, here is my vote: I did the following: 1) I did a quick successful test: I defined some components using both declarative service and dependency manager; I also managed to have a circular dependency: ... and the plugin discovered the cycle ! 2) in the org.apache.felix.servicediagnostics.plugin-0.1.2.jar, the changelog is missing (but I think this does not block the release, isn't it ?) 3) the sample maven project does not seem to compile, and I had to manually download the required artifacts in order to do a test (org.apache.servicemix.bundles.scala-library-2.9.1_3.jar, etc ...). it would be nice if you could add in the README.txt the list of exact maven dependencies (scala, etc ...). Unless I missed something in the license/dependencies file, I think it's ok: +1 (binding) regards /Pierre On Fri, Jan 4, 2013 at 11:08 AM, Arjun Panday arjun.pan...@alcatel-lucent.com wrote: Hi, I'd like to release a new version of the ServiceDiagnostics webconsole plugin. This new version features better integration with the webconsole architecture, proper handling of service properties and detection of circular dependencies between services across dependency frameworks. It's also lighter as it doesn't embed the scala library anymore. A sample launcher with the required dependencies can be found here: http://svn.apache.org/repos/**asf/felix/trunk/webconsole-** plugins/servicediagnostics/**run.shhttp://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/servicediagnostics/run.sh Changes from 0.1.1 to 0.2.0 --- ** Bug * [FELIX-3764] servicediagnostics plugin does not append the correct context path info to it's javascript files * [FELIX-3767] servicediagnostics plugin should properly handle service properties ** Improvement * complete rewrite * [FELIX-3768] servicediagnostics plugin should detect circular dependencies * doesn't embedd scala, json or jquery anymore ** Backward compatibility * broken: plugin API changed There are still some outstanding issues: https://issues.apache.org/**jira/browse/FELIX-3769https://issues.apache.org/jira/browse/FELIX-3769(I'll change to the new plugin directory structure when it's released) Staging repository: https://repository.apache.org/**content/repositories/**orgapachefelix-098/https://repository.apache.org/content/repositories/orgapachefelix-098/ https://repository.apache.org/**content/repositories/**orgapachefelix-093/https://repository.apache.org/content/repositories/orgapachefelix-093/(parent pom) You can usethis UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/**asf/felix/trunk/check_staged_**release.shhttp://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh Usage: sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/felix-staging Please vote to approvethis release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be openfor 72 hours. Best regards, Arjun -- Carsten Ziegeler cziege...@apache.org
[jira] [Created] (FELIX-3863) Generate DependencyManager Annotation MetaData In Project Folder
Pierre De Rop created FELIX-3863: Summary: Generate DependencyManager Annotation MetaData In Project Folder Key: FELIX-3863 URL: https://issues.apache.org/jira/browse/FELIX-3863 Project: Felix Issue Type: New Feature Components: Dependency Manager Affects Versions: dependencymanager-3.0.0 Reporter: Pierre De Rop Assignee: Pierre De Rop Priority: Minor This change request concerns the dependency manager maven annotation plugin and is related to the following old post in the user mailing list: http://www.mail-archive.com/users@felix.apache.org/msg11621.html Basically, the purpose of the change request is to allow the maven plugin to generate the dependencymanager annotation metadata files (META-INF/dependencymanager/*) not only in the bundle file but also in the maven project folder hierarchy, i.e., com.myannotation.project/com.myannotation.testbundle/META-INF/dependencymanager/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (FELIX-3863) Generate DependencyManager Annotation MetaData In Project Folder
[ https://issues.apache.org/jira/browse/FELIX-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-3863 started by Pierre De Rop. Generate DependencyManager Annotation MetaData In Project Folder Key: FELIX-3863 URL: https://issues.apache.org/jira/browse/FELIX-3863 Project: Felix Issue Type: New Feature Components: Dependency Manager Affects Versions: dependencymanager-3.0.0 Reporter: Pierre De Rop Assignee: Pierre De Rop Priority: Minor This change request concerns the dependency manager maven annotation plugin and is related to the following old post in the user mailing list: http://www.mail-archive.com/users@felix.apache.org/msg11621.html Basically, the purpose of the change request is to allow the maven plugin to generate the dependencymanager annotation metadata files (META-INF/dependencymanager/*) not only in the bundle file but also in the maven project folder hierarchy, i.e., com.myannotation.project/com.myannotation.testbundle/META-INF/dependencymanager/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3863) Generate DependencyManager Annotation MetaData In Project Folder
[ https://issues.apache.org/jira/browse/FELIX-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop resolved FELIX-3863. -- Resolution: Fixed Committed a patch in revision 1437070: Added support for a new optional parameter (generated-output-dir) in the dependencymanager annotation maven plugin, in order to specify a path (starting from the project base directory), and the maven plugin will then generate the extra descriptors files in that path. For example: plugin groupIdorg.apache.felix/groupId artifactIdorg.apache.felix.dependencymanager.annotation/artifactId version3.1.0-SNAPSHOT/version executions execution goals goalscan/goal /goals configuration logwarn/log generated-output-dir./generated-output-dir-- /configuration /execution /executions /plugin will generate all dependencymanager annotations metadata in the root directory (.) of the maven project. Generate DependencyManager Annotation MetaData In Project Folder Key: FELIX-3863 URL: https://issues.apache.org/jira/browse/FELIX-3863 Project: Felix Issue Type: New Feature Components: Dependency Manager Affects Versions: dependencymanager-3.0.0 Reporter: Pierre De Rop Assignee: Pierre De Rop Priority: Minor This change request concerns the dependency manager maven annotation plugin and is related to the following old post in the user mailing list: http://www.mail-archive.com/users@felix.apache.org/msg11621.html Basically, the purpose of the change request is to allow the maven plugin to generate the dependencymanager annotation metadata files (META-INF/dependencymanager/*) not only in the bundle file but also in the maven project folder hierarchy, i.e., com.myannotation.project/com.myannotation.testbundle/META-INF/dependencymanager/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3863) Generate DependencyManager Annotation MetaData In Project Folder
[ https://issues.apache.org/jira/browse/FELIX-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop closed FELIX-3863. closing this issue. Generate DependencyManager Annotation MetaData In Project Folder Key: FELIX-3863 URL: https://issues.apache.org/jira/browse/FELIX-3863 Project: Felix Issue Type: New Feature Components: Dependency Manager Affects Versions: dependencymanager-3.0.0 Reporter: Pierre De Rop Assignee: Pierre De Rop Priority: Minor This change request concerns the dependency manager maven annotation plugin and is related to the following old post in the user mailing list: http://www.mail-archive.com/users@felix.apache.org/msg11621.html Basically, the purpose of the change request is to allow the maven plugin to generate the dependencymanager annotation metadata files (META-INF/dependencymanager/*) not only in the bundle file but also in the maven project folder hierarchy, i.e., com.myannotation.project/com.myannotation.testbundle/META-INF/dependencymanager/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3852) InstallBundle throws ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String
[ https://issues.apache.org/jira/browse/FELIX-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560231#comment-13560231 ] Richard S. Hall commented on FELIX-3852: Yeah, I think that was the intent to begin with, so go ahead and commit your patch. InstallBundle throws ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String - Key: FELIX-3852 URL: https://issues.apache.org/jira/browse/FELIX-3852 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Sahoo Assignee: Sahoo Priority: Critical Fix For: framework-4.2.0 Attachments: Felix-3852.patch Caused by: org.osgi.framework.BundleException: Could not create bundle object. at org.apache.felix.framework.Felix.installBundle(Felix.java:2885) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138) at org.glassfish.extras.osgicontainer.OSGiDeployer.installBundle(OSGiDeployer.java:114) ... 47 more Caused by: java.lang.ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String at org.apache.felix.framework.util.StringMap.putAll(StringMap.java:89) at org.apache.felix.framework.util.StringMap.init(StringMap.java:43) at org.apache.felix.framework.cache.DirectoryRevision.getManifestHeader(DirectoryRevision.java:92) at org.apache.felix.framework.BundleImpl.createRevision(BundleImpl.java:1188) at org.apache.felix.framework.BundleImpl.init(BundleImpl.java:95) at org.apache.felix.framework.Felix.installBundle(Felix.java:2832) ... 50 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3845) Bundles with long Bundle-SymbolicName would fail to be installed
[ https://issues.apache.org/jira/browse/FELIX-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560239#comment-13560239 ] Richard S. Hall commented on FELIX-3845: Could you attach a simple example manifest that is failing? Thanks. Bundles with long Bundle-SymbolicName would fail to be installed Key: FELIX-3845 URL: https://issues.apache.org/jira/browse/FELIX-3845 Project: Felix Issue Type: Bug Reporter: Claus Ibsen Priority: Minor Fix For: framework-4.2.0 See fuse forum http://fusesource.com/forums/thread.jspa?threadID=4540tstart=0 The issue is that the person uses maven felix bundle plugin to bundle his project as an OSGi bundle. And if the name of the bundle becomes too long it gets wrapped in the MANIFEST.MF file and then Felix fails to install the bundle. More details in that link -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3852) InstallBundle throws ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String
[ https://issues.apache.org/jira/browse/FELIX-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahoo resolved FELIX-3852. -- Resolution: Fixed svn #1437269 InstallBundle throws ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String - Key: FELIX-3852 URL: https://issues.apache.org/jira/browse/FELIX-3852 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.2.0 Reporter: Sahoo Assignee: Sahoo Priority: Critical Fix For: framework-4.2.0 Attachments: Felix-3852.patch Caused by: org.osgi.framework.BundleException: Could not create bundle object. at org.apache.felix.framework.Felix.installBundle(Felix.java:2885) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138) at org.glassfish.extras.osgicontainer.OSGiDeployer.installBundle(OSGiDeployer.java:114) ... 47 more Caused by: java.lang.ClassCastException: java.util.jar.Attributes$Name cannot be cast to java.lang.String at org.apache.felix.framework.util.StringMap.putAll(StringMap.java:89) at org.apache.felix.framework.util.StringMap.init(StringMap.java:43) at org.apache.felix.framework.cache.DirectoryRevision.getManifestHeader(DirectoryRevision.java:92) at org.apache.felix.framework.BundleImpl.createRevision(BundleImpl.java:1188) at org.apache.felix.framework.BundleImpl.init(BundleImpl.java:95) at org.apache.felix.framework.Felix.installBundle(Felix.java:2832) ... 50 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
