You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Francesco Mari <ma...@gmail.com> on 2016/11/01 09:16:34 UTC
Deprecate oak-segment and oak-tarmk-standby
Hi,
This is a heads up for the deprecation oak-segment and
oak-tarmk-standby. The new oak-segment-tar module is a replacement for
both of the aforementioned modules. If somebody is concerned about the
deprecation, please let me know.
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Francesco Mari <ma...@gmail.com>.
The other solution will be to keep oak-segment and oak-tarmk-standby
as deprecated modules in 1.6.x and remove them in 1.8.
2016-11-01 14:00 GMT+01:00 Francesco Mari <ma...@gmail.com>:
> 2016-11-01 12:56 GMT+01:00 Julian Reschke <ju...@gmx.de>:
>> On 2016-11-01 11:44, Francesco Mari wrote:
>>>
>>> Hi,
>>>
>>> 2016-11-01 11:38 GMT+01:00 Robert Munteanu <ro...@apache.org>:
>>>>
>>>> Hi Francesco,
>>>>
>>>> On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> This is a heads up for the deprecation oak-segment and
>>>>> oak-tarmk-standby. The new oak-segment-tar module is a replacement
>>>>> for
>>>>> both of the aforementioned modules. If somebody is concerned about
>>>>> the
>>>>> deprecation, please let me know.
>>>>
>>>>
>>>> A couple of 'outsider' questions:
>>>>
>>>> 1. What does the deprecation mean exactly?
>>>
>>>
>>> It means that we are marking every class in those modules as
>>> @Deprecated. These modules will have a 1.6 release, but will probably
>>> be removed from the reactor after that to exclude them from further
>>> releases.
>>> ...
>>
>>
>> That doesn't sound right to me.
>>
>> Either remove them *before* 1.6 is cut, or keep them in the 1.6 branch later
>> on.
>
> I think that we will need at least a 1.6 release for oak-run and
> oak-upgrade to correctly use the tooling for the migration.
>
>> Best regards, Julian
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Francesco Mari <ma...@gmail.com>.
2016-11-01 12:56 GMT+01:00 Julian Reschke <ju...@gmx.de>:
> On 2016-11-01 11:44, Francesco Mari wrote:
>>
>> Hi,
>>
>> 2016-11-01 11:38 GMT+01:00 Robert Munteanu <ro...@apache.org>:
>>>
>>> Hi Francesco,
>>>
>>> On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote:
>>>>
>>>> Hi,
>>>>
>>>> This is a heads up for the deprecation oak-segment and
>>>> oak-tarmk-standby. The new oak-segment-tar module is a replacement
>>>> for
>>>> both of the aforementioned modules. If somebody is concerned about
>>>> the
>>>> deprecation, please let me know.
>>>
>>>
>>> A couple of 'outsider' questions:
>>>
>>> 1. What does the deprecation mean exactly?
>>
>>
>> It means that we are marking every class in those modules as
>> @Deprecated. These modules will have a 1.6 release, but will probably
>> be removed from the reactor after that to exclude them from further
>> releases.
>> ...
>
>
> That doesn't sound right to me.
>
> Either remove them *before* 1.6 is cut, or keep them in the 1.6 branch later
> on.
I think that we will need at least a 1.6 release for oak-run and
oak-upgrade to correctly use the tooling for the migration.
> Best regards, Julian
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Julian Reschke <ju...@gmx.de>.
On 2016-11-01 11:44, Francesco Mari wrote:
> Hi,
>
> 2016-11-01 11:38 GMT+01:00 Robert Munteanu <ro...@apache.org>:
>> Hi Francesco,
>>
>> On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote:
>>> Hi,
>>>
>>> This is a heads up for the deprecation oak-segment and
>>> oak-tarmk-standby. The new oak-segment-tar module is a replacement
>>> for
>>> both of the aforementioned modules. If somebody is concerned about
>>> the
>>> deprecation, please let me know.
>>
>> A couple of 'outsider' questions:
>>
>> 1. What does the deprecation mean exactly?
>
> It means that we are marking every class in those modules as
> @Deprecated. These modules will have a 1.6 release, but will probably
> be removed from the reactor after that to exclude them from further
> releases.
> ...
That doesn't sound right to me.
Either remove them *before* 1.6 is cut, or keep them in the 1.6 branch
later on.
Best regards, Julian
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Julian Sedding <js...@gmail.com>.
+1 for the deprecations
Regards
Julian
On Tue, Nov 1, 2016 at 12:19 PM, Robert Munteanu <ro...@apache.org> wrote:
> Thanks Francesco and Michael, all clear now for me.
>
> Robert
>
> On Tue, 2016-11-01 at 11:47 +0100, Michael Dürig wrote:
>>
>> On 1.11.16 11:44 , Francesco Mari wrote:
>> > > 2. What is the migration strategy for deployments using oak-
>> > > segment?
>> >
>> > Just use oak-segment-tar instead of oak-segment and oak-tarmk-
>> > standby.
>> > It is almost a trivial replacement, except for some minor details
>> > that
>> > will be covered in the documentation.
>> >
>>
>> And migration is covered via oak-upgrade. That is, there is a one
>> time
>> migration effort involved on repositories created by oak-segment.
>>
>> Michael
>
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Robert Munteanu <ro...@apache.org>.
Thanks Francesco and Michael, all clear now for me.
Robert
On Tue, 2016-11-01 at 11:47 +0100, Michael D�rig wrote:
>
> On 1.11.16 11:44 , Francesco Mari wrote:
> > > 2. What is the migration strategy for deployments using oak-
> > > segment?
> >
> > Just use oak-segment-tar instead of oak-segment and oak-tarmk-
> > standby.
> > It is almost a trivial replacement, except for some minor details
> > that
> > will be covered in the documentation.
> >
>
> And migration is covered via oak-upgrade. That is, there is a one
> time�
> migration effort involved on repositories created by oak-segment.
>
> Michael
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Michael Dürig <md...@apache.org>.
On 1.11.16 11:44 , Francesco Mari wrote:
>> 2. What is the migration strategy for deployments using oak-segment?
> Just use oak-segment-tar instead of oak-segment and oak-tarmk-standby.
> It is almost a trivial replacement, except for some minor details that
> will be covered in the documentation.
>
And migration is covered via oak-upgrade. That is, there is a one time
migration effort involved on repositories created by oak-segment.
Michael
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Francesco Mari <ma...@gmail.com>.
Hi,
2016-11-01 11:38 GMT+01:00 Robert Munteanu <ro...@apache.org>:
> Hi Francesco,
>
> On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote:
>> Hi,
>>
>> This is a heads up for the deprecation oak-segment and
>> oak-tarmk-standby. The new oak-segment-tar module is a replacement
>> for
>> both of the aforementioned modules. If somebody is concerned about
>> the
>> deprecation, please let me know.
>
> A couple of 'outsider' questions:
>
> 1. What does the deprecation mean exactly?
It means that we are marking every class in those modules as
@Deprecated. These modules will have a 1.6 release, but will probably
be removed from the reactor after that to exclude them from further
releases.
> 2. What is the migration strategy for deployments using oak-segment?
Just use oak-segment-tar instead of oak-segment and oak-tarmk-standby.
It is almost a trivial replacement, except for some minor details that
will be covered in the documentation.
> THanks,
>
> Robert
Re: Deprecate oak-segment and oak-tarmk-standby
Posted by Robert Munteanu <ro...@apache.org>.
Hi Francesco,
On Tue, 2016-11-01 at 10:16 +0100, Francesco Mari wrote:
> Hi,
>
> This is a heads up for the deprecation oak-segment and
> oak-tarmk-standby. The new oak-segment-tar module is a replacement
> for
> both of the aforementioned modules. If somebody is concerned about
> the
> deprecation, please let me know.
A couple of 'outsider' questions:
1. What does the deprecation mean exactly?
2. What is the migration strategy for deployments using oak-segment?
THanks,
Robert