You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2011/01/03 16:31:33 UTC
Remove SMX3 common sub-project
Hi,
Previously, ServiceMix 3 provided the components itself in the
common/servicemix-components sub-project:
http://svn.apache.org/repos/asf/servicemix/smx3/trunk/common/
This sub-project is deprecated as we now use the ServiceMix Components
shared by SMX3 and SMX4:
http://svn.apache.org/repos/asf/servicemix/components/trunk/
To simplify and speed up the SMX3 build, I propose to remove the SMX3
common subproject (and linked dependencies in the main SMX3 POM).
No objection ?
Regards
JB
Re: Remove SMX3 common sub-project
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It makes sense.
I'm updating ServiceMix 3 to align the dependencies set and let as it is
(ready for a new release in the same time as the ServiceMix 4.3.0 one).
Regards
JB
On 01/04/2011 11:12 AM, Gert Vanthienen wrote:
> Jean-Baptiste,
>
> Personally, I would avoid too many big changes on ServiceMix 3. I'd
> rather consider that a stable branch, where we just do bug fixing and
> update to newer versions of Camel and ActiveMQ, but I would prefer to
> focus on ServiceMix 4 for ongoing development. E.g. I agree the
> servicemix-lwcontainer component has been superseded by
> servicemix-bean, but we should probably tell new people to start using
> ServiceMix 4 anyway and existing users may still depend on it.
>
> Perhaps we should schedule a few more minor releases to pick up Camel
> 2.5 and Camel 2.6, with the matching CXF versions to support existing
> users, but I'm not sure we should go through the effort of upgrading
> ServiceMix 3.x to the next major release of Camel, CXF, ActiveMQ, ...
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> FuseSource
> Web: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On Mon, Jan 3, 2011 at 4:34 PM, Jean-Baptiste Onofré<jb...@nanthrax.net> wrote:
>> Around the same topic, I propose to remote the SMX3 deployables sub-project
>> (which only contains the servicemix-lwcontainer component).
>>
>> This service engine is quite deprecated and replaced by the servicemix-bean
>> one.
>>
>> WDYT ?
>>
>> Thanks
>> Regards
>> JB
>>
>> On 01/03/2011 04:31 PM, Jean-Baptiste Onofré wrote:
>>>
>>> Hi,
>>>
>>> Previously, ServiceMix 3 provided the components itself in the
>>> common/servicemix-components sub-project:
>>> http://svn.apache.org/repos/asf/servicemix/smx3/trunk/common/
>>>
>>> This sub-project is deprecated as we now use the ServiceMix Components
>>> shared by SMX3 and SMX4:
>>> http://svn.apache.org/repos/asf/servicemix/components/trunk/
>>>
>>> To simplify and speed up the SMX3 build, I propose to remove the SMX3
>>> common subproject (and linked dependencies in the main SMX3 POM).
>>>
>>> No objection ?
>>>
>>> Regards
>>> JB
>>
Re: Remove SMX3 common sub-project
Posted by Gert Vanthienen <ge...@gmail.com>.
Jean-Baptiste,
Personally, I would avoid too many big changes on ServiceMix 3. I'd
rather consider that a stable branch, where we just do bug fixing and
update to newer versions of Camel and ActiveMQ, but I would prefer to
focus on ServiceMix 4 for ongoing development. E.g. I agree the
servicemix-lwcontainer component has been superseded by
servicemix-bean, but we should probably tell new people to start using
ServiceMix 4 anyway and existing users may still depend on it.
Perhaps we should schedule a few more minor releases to pick up Camel
2.5 and Camel 2.6, with the matching CXF versions to support existing
users, but I'm not sure we should go through the effort of upgrading
ServiceMix 3.x to the next major release of Camel, CXF, ActiveMQ, ...
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, Jan 3, 2011 at 4:34 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Around the same topic, I propose to remote the SMX3 deployables sub-project
> (which only contains the servicemix-lwcontainer component).
>
> This service engine is quite deprecated and replaced by the servicemix-bean
> one.
>
> WDYT ?
>
> Thanks
> Regards
> JB
>
> On 01/03/2011 04:31 PM, Jean-Baptiste Onofré wrote:
>>
>> Hi,
>>
>> Previously, ServiceMix 3 provided the components itself in the
>> common/servicemix-components sub-project:
>> http://svn.apache.org/repos/asf/servicemix/smx3/trunk/common/
>>
>> This sub-project is deprecated as we now use the ServiceMix Components
>> shared by SMX3 and SMX4:
>> http://svn.apache.org/repos/asf/servicemix/components/trunk/
>>
>> To simplify and speed up the SMX3 build, I propose to remove the SMX3
>> common subproject (and linked dependencies in the main SMX3 POM).
>>
>> No objection ?
>>
>> Regards
>> JB
>
Re: Remove SMX3 common sub-project
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Around the same topic, I propose to remote the SMX3 deployables
sub-project (which only contains the servicemix-lwcontainer component).
This service engine is quite deprecated and replaced by the
servicemix-bean one.
WDYT ?
Thanks
Regards
JB
On 01/03/2011 04:31 PM, Jean-Baptiste Onofré wrote:
> Hi,
>
> Previously, ServiceMix 3 provided the components itself in the
> common/servicemix-components sub-project:
> http://svn.apache.org/repos/asf/servicemix/smx3/trunk/common/
>
> This sub-project is deprecated as we now use the ServiceMix Components
> shared by SMX3 and SMX4:
> http://svn.apache.org/repos/asf/servicemix/components/trunk/
>
> To simplify and speed up the SMX3 build, I propose to remove the SMX3
> common subproject (and linked dependencies in the main SMX3 POM).
>
> No objection ?
>
> Regards
> JB