Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs

Hi all I think Guillaume’s idea of defining that provisional, WIP, interim, temporary OSGi API commits be isolated and refer to a concrete OSGi Repository commit (URL ideally) makes sense to me. So that we can track back this source. In any case, OSGi API will always bei OSGi copyrighted and

Re: Implementation of unreleased spec and community

Hi all And we should also mention that quite a number of active community members actually working on those things are members (or employees of members) of the OSGi alliance and as such open to feedback received from the communities on the evolution of the specifications. As such, I think it

Re: Aries JAX-RS example dependencies with CDDL/GPL license

Hi David At least for javax.json, you will find AL2 licensed binaries from Apache Johnzon Regards Felix > Am 16.01.2017 um 12:09 schrieb David Bosschaert : > > Hi all, > > I was playing with Aries JAX-RS and noticed that when running the examples > as explained in

Re: [Proposal] Use release per subproject for blueprint

r humans. It would be great to apply semantic versioning here as well to some extent. Though not in a technically strict sense. Still no change, no version IMHO is a good thing. Regards Felix > > Christian > > > > 2017-01-03 14:04 GMT+01:00 Felix Meschberger <fmesc...@adobe.com>

Re: [Proposal] Use release per subproject for blueprint

Hi Christian On a high level I disagree and would suggest to continue releasing individual bundles. Plus: don’t blindly update dependency versions just because there is a new release. I think the „plus“ is actually key here: With OSGi applications are bound late at the time of deployment

Re: Votes missing for [VOTE] Release Apache Mina SSHD 1.2.0

Wrong list ? ;-) Regards Felix > Am 21.03.2016 um 08:43 schrieb Guillaume Nodet : > > We're still missing a few binding votes... > > 2016-03-09 11:30 GMT+01:00 Guillaume Nodet : > >> I've staged a release candidate for SSHD 1.2.0 >> >> Repository: >>

Version Plugin and Guava

Hi We are currently considering using Guava in our application. Guava, though is really problematic in OSGi for various reasons: One of them is that it does not export packages with individual versions according to OSGi-level semantic versioning. See Guava Issue 1682 [1]. Now there’s a guy

Re: Version Plugin and Guava

, can you paste the example line here? Thanks Emily On Mon, Sep 15, 2014 at 10:19 AM, Felix Meschberger fmesc...@adobe.com wrote: Hi We are currently considering using Guava in our application. Guava, though is really problematic in OSGi for various reasons: One of them is that it does

Re: Problem with maven-bundle-plugin

Hi Guillaume As I understand it the bundle plugin 3.5.0 (or whatever the next version may be) is around the corner — and I assume you tried the latest trunk build for ARIES-1192. How about just waiting another week ? Regards Felix Am 17.06.2014 um 10:10 schrieb Guillaume Nodet

Re: Welcome Tom Watson - our newest Aries committer

Hi Tom Congratulations and pleased to meet you here as well ;-) Regards Felix Am 09.06.2014 um 22:41 schrieb Jeremy Hughes hugh...@apache.org: The Aries PMC has voted in Tom Watson as committer, who you may know as Eclipse Equinox Project co-lead. Congratulations Tom, thanks for your

Re: [VOTE] Transaction manager 1.1 and jdbc 2.0

Hi Daniel Do you have references to the issues fixed, actually ? I cannot find the transaction-manager-1.1.0 or transaction-jdbc-2.0.0 version labels in JIRA. Thanks. Felix Am 17.12.2013 um 22:30 schrieb Daniel Kulp dk...@apache.org: This is a vote to release updates for the transaction

Re: Initial JMX page for Aries Documentation

Hi I have written something about the white board. Regards Felix Am 27.05.2013 um 15:56 schrieb David Bosschaert: Answering my own question, I found the information I needed here: http://aries.apache.org/development/maintainingthewebpages.html For the screen shot, I simply added it to the

Re: [VOTE] JMX 1.1.0 bundles

+1 (non-binding) Regards Felix Am 23.01.2013 um 12:33 schrieb Daniel Kulp: This is a vote to release all the new JMX 1.1.0 based bundles which updates the JMX stuff to the 1.1.0 spec. Tags: jmx-api: http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx.api-1.1.0/ jmx-core:

Re: Moving JMX-Next from the sandbox back into the main trunk

+1 (non binding). Thanks and Regards Felix Am 12.11.2012 um 13:05 schrieb David Bosschaert: Hi all, The JMX-Next code in Aries (in the sandbox/jmx-next) code base is done now (as far as I can see) and I think it's ready to move back into the main codebase. JMX-Next implements the

Re: [VOTE] Release blueprint-core, jmx-core, transaction-manager and jpa-container-context 1.0.1

+1 (non-binding) Regards Felix Am 25.09.2012 um 17:35 schrieb Guillaume Nodet: I've uploaded 4 bug fix bundles. * blueprint-core 1.0.1 : https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310981version=12322492 * jmx-core 1.0.1 :

Re: [VOTE] Release transaction-jms and transaction-jdbc 1.0.0

+1 (non-binding) Regards Felix Am 25.09.2012 um 17:46 schrieb Guillaume Nodet: I've staged two new modules for release. The first one, transaction-jms is a JMS connection factory with auto-enlistment and recovery for use with the Aries transaction-manager. The second one, transaction-jdbc,

Re: [VOTE] Apache Aries JMX, JNDI, JPA, and Quiesce API bundles release candidate

+1 (non-binding) Thanks for cutting these releases. The verfiy scrip passes. Regards Felix Am 27.06.2012 um 19:22 schrieb Holly Cummins: Hi all, This is a re-post of a vote which googlemail has helpfully threaded in with other emails, completely hiding it. :( I've staged a release

Re: Verifying releases - exciting new script

Thanks alot ! Works perfectly on my Mac box, too. One minor nitpick, though: I think the script should not wget and import the keys from dist/aries/KEYS. I prefer to import them manually myself from a different source ... Regards Felix Am 28.06.2012 um 15:00 schrieb Jeremy Hughes: On 26

Re: Verifying releases - exciting new script

Hi, Am 28.06.2012 um 16:09 schrieb Jeremy Hughes: On 28 June 2012 14:09, Felix Meschberger fmesc...@adobe.com wrote: Thanks alot ! Works perfectly on my Mac box, too. One minor nitpick, though: I think the script should not wget and import the keys from dist/aries/KEYS. I prefer

Version Check Plugin

Hi, I have a few questions/suggestions for the version check plugin: * How about adding the ability to break the build instead of just creating missing packageinfo ? For example: - break on missing export package version - break on wrong version increment * How about a release ? I

Re: Repository Layout

Hi I think Andreas brings a few important things on the table. Let me discuss a few from my POV (and also with my background from Felix and Sling). In the same manner ARIES/branches could create any folder combination liked containing the required projects as svn:externals instead of real

Re: [DISCUSS] Logging for Aries modules

Hi, Am 01.02.2012 um 14:53 schrieb David Bosschaert: My issue with it is that it brings in 2 dependencies: the SLF4J api and an SLF4J implementation bundle. In the context where I want to use the JNDI component there is already a log subsystem in place, which can be reached through the OSGi

Re: Aries JNDI dependencies

Hi, Am 16.01.2012 um 09:22 schrieb David Bosschaert: Hi all, I'm looking at the dependencies of the Aries jndi-bundle component, roughly they are: the javax JNDI API the OSGi JNDI API aries-util aries-proxy aries-blueprint slf4j I'm wondering about the last two: aries-blueprint

[jira] [Resolved] (ARIES-782) AbstractCompendiumHandler uses ServiceTracker.getTrackingCount in the wrong way

[ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved ARIES-782. - Resolution: Fixed Fix Version/s: 0.4 Applied the patch in Rev. 1227542

[jira] [Created] (ARIES-806) Align Bundle-Name of the JMX Whiteboard bundle with other JMX bundles

: Improvement Components: JMX Affects Versions: 0.3 Reporter: Felix Meschberger Assignee: Felix Meschberger The JMX Whiteboard bundle's Bundle-Name currently is Apache Aries Whiteboard support for JMX DynamicMBean services which does not align with other JMX

[jira] [Resolved] (ARIES-806) Align Bundle-Name of the JMX Whiteboard bundle with other JMX bundles

[ https://issues.apache.org/jira/browse/ARIES-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved ARIES-806. - Resolution: Fixed Fix Version/s: 0.4 Fixed in Rev. 1227545 Align

Re: Aries jmx-bundle and uses clause computation

Hi, Am 03.01.2012 um 18:44 schrieb Alasdair Nottingham: Hi, I bet it is because the spec says it needs to look exactly like that, with those uses clauses. Where would that be mentioned. I quickly scanned the spec and could not find such a thing. Also, I would not remember having seen it

Re: [jira] [Resolved] (ARIES-786) Ability to control the list of woven classes using system properties

Hi, Am 25.11.2011 um 12:52 schrieb Alasdair Nottingham: Rather than rely on system properties wouldn't it be better to use ConfigAdmin for this kind of configuration? That way we aren't trying to use JVM singleton configuration for a dynamic modular environment? Looking at the code it seems

Re: OSGi 4.3 capability parser

Hi, Yo might want to look into the Felix Framework code ... Regards Felix Am 18.11.2011 um 18:16 schrieb David Bosschaert: Hi all, Does Aries contain a utility class yet to parse OSGi 4.3 Provide-Capability/Require-Capability headers yet? Like for instance to parse this one (from core

[jira] [Created] (ARIES-782) AbstractCompendiumHandler uses ServiceTracker.getTrackingCount in the wrong way

Issue Type: Bug Components: JMX Affects Versions: 0.3 Reporter: Felix Meschberger The AbstractCompendiumHandler.addingService calls the ServiceTracker.getTrackingCount() to obviously check the number of services registered under the same name. Of course

[jira] [Updated] (ARIES-782) AbstractCompendiumHandler uses ServiceTracker.getTrackingCount in the wrong way

[ https://issues.apache.org/jira/browse/ARIES-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-782: Attachment: ARIES-782.patch Proposed patch: Use trackedId field instead

Re: board report

Hi, Thanks for reporting back from the IRC channel since not everybody sitting on this mailing list is also sitting on the IRC channel. That's why there is a saying in the ASF that if it wasn't on the mailing list, it didn't happen ;-) Regards Felix Am 27.10.2011 um 17:00 schrieb David

Re: board report

Felix Meschberger wrote: Hi, Thanks for reporting back from the IRC channel since not everybody sitting on this mailing list is also sitting on the IRC channel. That's why there is a saying in the ASF that if it wasn't on the mailing list, it didn't happen ;-) Would people want that channel

Re: Welcome to Felix Meschberger

Hi, Thanks for the warm welcome and thanks for inviting me. For those who happen to not know me ;-), let me quickly quickly introduce myself. I work at Adobe caring for most of the things around the application framework (together with Bertrand Delacretaz and Carsten Ziegeler). In this role I

Re: JMX whiteboard project

Hi Alasdair, Am Donnerstag, den 07.07.2011, 22:25 +0100 schrieb Alasdair Nottingham: On 5 July 2011 13:15, Felix Meschberger fmesc...@adobe.com wrote: Hi, Am Dienstag, den 05.07.2011, 12:50 +0100 schrieb Alasdair Nottingham: Hi, This is amazing timing. I've hit exactly

Re: JMX whiteboard project

Hi Alasdair, Am Donnerstag, den 07.07.2011, 22:21 +0100 schrieb Alasdair Nottingham: Hi, In case you missed it I have committed and resolved 700, 701, 702. Yes, I saw it. Thanks a lot. Regards Felix On 6 July 2011 06:57, Felix Meschberger fmesc...@adobe.com wrote: Hi Thanks

Re: JMX whiteboard project

Hi, Am Freitag, den 08.07.2011, 09:50 +0100 schrieb Alasdair Nottingham: On 8 July 2011 08:24, Felix Meschberger fmesc...@adobe.com wrote: Hi Alasdair, Am Donnerstag, den 07.07.2011, 22:25 +0100 schrieb Alasdair Nottingham: On 5 July 2011 13:15, Felix Meschberger fmesc...@adobe.com

Re: JMX whiteboard project

) (instead of (jmx.objectname=*)) as the filter and inspect the objectClass for the MBean interface. This would be closer to my original code ;-) Regards Felix Thanks Alasdair On 5 July 2011 08:03, Felix Meschberger fmesc...@adobe.com wrote: Hi, I think I missed a problematic point

[jira] [Created] (ARIES-702) [Whiteboard] Use introspection to find the MBean interface

Components: JMX Affects Versions: 0.3 Reporter: Felix Meschberger The JMX Spec states that standard MBeans must implement an interface whose name is derived from the implementation class by appending the MBean suffix and the interface must be located in the same package

[jira] [Updated] (ARIES-701) [Whiteboard] Use IdentityHashMapObject,MBeanHolder to map registered services to MBeanHolders

[ https://issues.apache.org/jira/browse/ARIES-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-701: Attachment: (was: ARIES-701.patch) [Whiteboard] Use IdentityHashMapObject,MBeanHolder

[jira] [Updated] (ARIES-701) [Whiteboard] Use IdentityHashMapObject,MBeanHolder to map registered services to MBeanHolders

[ https://issues.apache.org/jira/browse/ARIES-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-701: Attachment: ARIES-701.patch Simple Patch [Whiteboard] Use IdentityHashMapObject

[jira] [Updated] (ARIES-701) [Whiteboard] Use IdentityHashMapObject,MBeanHolder to map registered services to MBeanHolders

[ https://issues.apache.org/jira/browse/ARIES-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-701: Comment: was deleted (was: Simple Patch) [Whiteboard] Use IdentityHashMapObject

[jira] [Updated] (ARIES-701) [Whiteboard] Use IdentityHashMapObject,MBeanHolder to map registered services to MBeanHolders

[ https://issues.apache.org/jira/browse/ARIES-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-701: Attachment: ARIES-701.patch Simple Patch [Whiteboard] Use IdentityHashMapObject

[jira] [Updated] (ARIES-702) [Whiteboard] Use introspection to find the MBean interface

[ https://issues.apache.org/jira/browse/ARIES-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-702: Attachment: ARIES-702.patch Proposed patch using a new service filter (jmx.objectname

[jira] [Updated] (ARIES-702) [Whiteboard] Use introspection to find the MBean interface

[ https://issues.apache.org/jira/browse/ARIES-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-702: Attachment: ARIES-702-2.patch Patch against Rev. 1143254 dependend on having ARIES-701

Re: JMX whiteboard project

doesn't work for me though. I think that is because it is a patch on 700, not 701. Alasdair On 5 July 2011 13:44, Felix Meschberger fmesc...@adobe.com wrote: Hi I have created ARIES-701 [1] and ARIES-702 [2] showing where this all might lead to.. Regards Felix [1] https

Re: JMX whiteboard project

Hi, Am Montag, den 27.06.2011, 20:45 +0100 schrieb Alasdair Nottingham: On 27 June 2011 20:19, Felix Meschberger fmesc...@gmail.com wrote: Hi, Am Montag, den 27.06.2011, 20:07 +0100 schrieb Alasdair Nottingham: Hi, I've been looking at the way the whiteboard implementation

Re: semantic version packages and bundles

Hi, Am Mittwoch, den 06.04.2011, 21:51 +0100 schrieb Emily Jiang: Am I right to say that we don't need to change the package or bundle version on the trunk even if we change apis, as the versions will be updated when we do a release? I am about to commiting some api changes and would like to

Re: semantic version packages and bundles

or not. On the other hands: version numbers are cheap ;-) So its probably better to increase too often than failing to increase ... Regards Felix Regards Emily On Thu, Apr 7, 2011 at 7:55 AM, Felix Meschberger fmesc...@gmail.comwrote: Hi, Am Mittwoch, den 06.04.2011, 21:51 +0100 schrieb

Re: [DISCUSS] Version Policy

Hi, Am Mittwoch, den 16.03.2011, 20:23 + schrieb zoe slattery: On 16/03/2011 19:28, Felix Meschberger wrote: Hi, Am Mittwoch, den 16.03.2011, 16:49 + schrieb Jeremy Hughes: On 16 March 2011 11:22, Felix Meschbergerfmesc...@gmail.com wrote: Hi, Good thing ! Some

Re: [DISCUSS] Version Policy

Hi, Am Donnerstag, den 17.03.2011, 12:08 + schrieb zoe slattery: Hi Hold on: lets first clarify which version of a bundle/module you are talking of: * If it is the bundle/module's own version as specfied along with the bundle/module's groupId and artifactId. This

Re: [DISCUSS] Version Policy

Hi, Good thing ! Some remarks: Re. Bundles: A bundle should never exist as a non-SNAPSHOT version in the trunk (except during the short period of time during which Maven generates the version tag). As such immediately after a release the bundle version switches to x.y.(z+1)-SNAPSHOT. Re.

Re: [DISCUSS] Version Policy

Hi, Am Mittwoch, den 16.03.2011, 14:30 + schrieb zoe slattery: Hi Felix - thanks Re. Bundles: A bundle should never exist as a non-SNAPSHOT version in the trunk (except during the short period of time during which Maven generates the version tag). As such immediately after a release

Re: [DISCUSS] Version Policy

Hi, Am Mittwoch, den 16.03.2011, 16:49 + schrieb Jeremy Hughes: On 16 March 2011 11:22, Felix Meschberger fmesc...@gmail.com wrote: Hi, Good thing ! Some remarks: Re. Bundles: A bundle should never exist as a non-SNAPSHOT version in the trunk (except during the short period

JNDI Whiteboard Registration

Hi all, We have a problem to register OSGi services with JNDI (mostly in the java:comp context and its subcontexts) for supporting legacy applications moved to OSGi (but not fully converted). So my idea was to add whiteboard pattern registration support for JNDI: Each service registered with a

Re: JNDI Whiteboard Registration

wondering if you can provide more information. Alasdair On 10 March 2011 14:20, Felix Meschberger fmesc...@adobe.com wrote: Hi all, We have a problem to register OSGi services with JNDI (mostly in the java:comp context and its subcontexts) for supporting legacy applications moved to OSGi

Re: [Discussion] Provide an OBR repository generator

Hi, As Guillaume said: Apache Felix BundleRepository has the code and it is used by the Maven Bundle Plugin. If you want to create some command line tool, which I think is an excellent idea, you should really leverage what's there in the Apche Felix BundleRepository code. Because, and this is

Re: Logging

Manager Singletons on page 387. If the JNDI Implementation cannot set these singletons then it should log an error with the Log Service, if available. It can then not perform the following sections. Regards Felix Alasdair Nottingham On 7 Mar 2011, at 11:16, Felix Meschberger fmesc

OSGi JNDI API

Hi all, The JNDI API module still has the OSGi JNDI API sources in it. Shouldn't this be changed to re-export the classes from the official Enterprise library ? On a related matter: I don't think the import exclusion of the OSGi JNDI API package is not required in this pom.xml. Regards Felix

Re: Logging

Hi, Am Dienstag, den 08.03.2011, 10:36 + schrieb Alasdair Nottingham: On 8 March 2011 06:47, Felix Meschberger fmesc...@gmail.com wrote: Hi, Am Montag, den 07.03.2011, 23:24 + schrieb Alasdair Nottingham: Hi, It should use slf4j really, everything else does. Thanks, I am

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

Reporter: Felix Meschberger 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

Re: OSGi JNDI API

Hi, Am Dienstag, den 08.03.2011, 11:10 + schrieb Alasdair Nottingham: On 8 March 2011 10:59, Alasdair Nottingham n...@apache.org wrote: On 8 March 2011 10:52, Felix Meschberger fmesc...@gmail.com wrote: Hi, Am Dienstag, den 08.03.2011, 10:38 + schrieb Alasdair Nottingham: On 8

[jira] Updated: (ARIES-599) Consistently use SLF4J Logging

[ https://issues.apache.org/jira/browse/ARIES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated ARIES-599: Attachment: ARIES-599-2.patch Oops, sorry. Correct. Attached is a patch adding the slf4j

Logging

Hi all, I am looking at integrating Aries JNDI support into Apache Sling and looking at the JNDI Core BundleActivator [1] I noticed that Java platform logging is used. Is this by intent ? Do you do all your (Aries) logging to the Java platform logging ? If so, I would have some tasks to do in

Re: [DISCUSSION] Using packageinfo to set package versions

Hi, Am Sonntag, den 06.02.2011, 16:42 + schrieb zoe slattery: Hi Yes, each bundle has its own change log because each bundle release has its own Version identifier in JIRA. But we collect similar bundles into bigger compoinents. For example all scripting related bundles (api, core,

Re: [DISCUSSION] Using packageinfo to set package versions

Hi, Am Samstag, den 05.02.2011, 14:28 + schrieb zoe slattery: On 05/02/2011 12:38, Guillaume Nodet wrote: I think we may want to stick too much to semantic versioning. Is there a 'not' missing? Don't get me wrong, I agree with the compatibility rules semantic and we should

Re: [DISCUSSION] Using packageinfo to set package versions

Hi, Am Samstag, den 05.02.2011, 00:43 +0100 schrieb Guillaume Nodet: In fact I want it to be easy, the easier the better. If you change the code the version should increment. So why even bother with having to manually change the version ? I think it should be possible to have the

Re: [DISCUSS] Api for a monitoring real bundles states when used with extenders

Hi, Am Donnerstag, den 03.02.2011, 10:27 +0100 schrieb Guillaume Nodet: With the multiplicity of extenders, it becomes increasingly difficult to know when a bundle is actually started. Another problem is when you actually want to order bundles starting Are you sure you want to support order

Re: [DISCUSS] Api for a monitoring real bundles states when used with extenders

Hi, Am Donnerstag, den 03.02.2011, 11:24 +0100 schrieb Guillaume Nodet: On Thu, Feb 3, 2011 at 10:48, Felix Meschberger fmesc...@gmail.com wrote: Hi, Am Donnerstag, den 03.02.2011, 10:27 +0100 schrieb Guillaume Nodet: With the multiplicity of extenders, it becomes increasingly difficult

Re: [DISCUSS] Api for a monitoring real bundles states when used with extenders

Hi, Thanks a lot for your clarifications ! Am Donnerstag, den 03.02.2011, 13:37 +0100 schrieb Guillaume Nodet: But actually, the bundle is ready, when it's started. The services and components/beans/you-name-it may not available yet at that time, though. How about just defining a best

Re: [DISCUSS] Api for a monitoring real bundles states when used with extenders

Hi, Am Donnerstag, den 03.02.2011, 15:14 +0100 schrieb Guillaume Nodet: On Thu, Feb 3, 2011 at 14:30, Felix Meschberger fmesc...@gmail.com wrote: Hi, Thanks a lot for your clarifications ! Am Donnerstag, den 03.02.2011, 13:37 +0100 schrieb Guillaume Nodet: But actually

Re: [DISCUSS] ARIES-536

Hi, Am Donnerstag, den 03.02.2011, 16:29 +0100 schrieb Guillaume Nodet: I've committed a patch for ARIES-536 which I'm sure some people will disagree with. However: * I don't see anything in the blueprint spec that forbids such a behavior * this isn't enabled by default * that's how