aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Watson <>
Subject Re: Planning to do an Aries Subsystems release soon
Date Mon, 22 Jun 2015 21:51:55 GMT
I'm applied the patch for 1307.  It was failing because the itests were 
not running against the latest.  To fix that I updated the itests pom.xml 
to refer to 2.0.1-SNAPSHOT of org.apache.aries.subsystem.core.  But I am 
confused how we got to version 2.0.1 for the subsystem.core bundle.  I 
would assume it would still be at version 2.0.0 given the discussion here.


From:   David Bosschaert <>
To:     "" <>
Date:   06/18/2015 06:56 AM
Subject:        Re: Planning to do an Aries Subsystems release soon

I just started to prepare the Subsystems release but am now seeing
that there is an open issue with a provided patch:

I'll look into applying the patch soon.

Are there any other open Subsystem issues that people are aware of
that we should apply a fix for before releasing subsystems?



On 16 June 2015 at 14:24, Jean-Baptiste Onofré <> wrote:
> For versioning, b looks better for me.
> Regards
> JB
> On 06/15/2015 10:18 PM, David Bosschaert wrote:
>> Hi all,
>> As the OSGi R6 Subsystems implementation is now merged into trunk I
>> was thinking of doing a subsystems release soon, possibly later this
>> week.
>> Previously we released the following artifacts:
>>    subsystem-api
>>    subsystem-core
>>    subsystem-obr
>>    subsystem-bundle
>> I don't think it makes sense to release subsystem-obr as OBR now
>> implements the Repository spec so this proprietary integration is not
>> needed any more. I would actually propose to remove this bundle.
>> On the subsystem-bundle (artifact ID org.apache.aries.subsystem). Does
>> anybody actually use this? It seems like this is the same as
>> subsystem-core and subsystem-api merged. I don't think there is a need
>> for this bundle, so I would propose to remove it too.
>> Final topic is the version number. Exported packages use semantic
>> versioning, no question about that but how will we version the
>> released bundles?
>> a) subsystem-api 1.2.0 and subsystem-core 1.3.0?
>> b) subsystem-api 2.0.0 and subsystem-core 2.0.0?
>> I guess b) is more in line with the recent discussion about bulk
>> releasing components?
>> Cheers,
>> David
> --
> Jean-Baptiste Onofré
> Talend -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message