14 Dec
2009
14 Dec
'09
10:39 a.m.
On Dec 14, 2009, at 10:33 AM, Anca Luca wrote:
Hi Vincent,
On 12/13/2009 11:35 AM, Vincent Massol wrote:
I think it's going to be hard to commit to remove the bridge
completely by 2.2 end. I'd love to do this though and if we succeed
I'm all for it. As I said in my email I'd like to push to the max for
the new model in 2.2 but I have no idea how far we will get.
One solution would be to use a branch but that would be a major PITA
since this code affects virtually everything else so merge will just
be impossible. Hence my strategy to commit small stuff at a time. This
also makes it much easier for everyone to participate to the new model.
Thanks
-Vincent
Hi,
New proposal:
Create a new xwiki-model and move "clean" classes from xwiki-bridge
into it. These are:
- *AttachmentName*
- *DocumentName*
Here's my +1
It's gonna be a bit uncomfortable for making annotations work on
both 2.1 &
higher but it's gonna be uncomfortable for someone at some point
anyway.
Normally +1
but is there any chance we could create this situation just once?
Right now I
see at least 2 cases: one now and one when the bridge will be
completely
replaced by the xwiki-model. Otherwise put, is there any chance we
could
postpone this? Thanks,
Anca
>
> Thanks
> -Vincent
>
> On Wed, Sep 2, 2009 at 1:12 PM, Thomas Mortagne
> <thomas.mortagne(a)xwiki.com> wrote:
>> On Wed, Aug 26, 2009 at 18:00, Vincent Massol<vincent(a)massol.net>
>> wrote:
>>> Hi,
>>>
>>> Since we have some final classes (final in the sense with a good
>>> architecture) in xwiki-bridge I'd like to rename it into xwiki-
>>> model
>>> so that we can start this model module.
>>>
>>> Note: We'd still have a org.xwiki.model.bridge package for the time
>>> being in that xwiki-model module.
>>>
>>> Here's my +1
>>
>> I would prefer to create a new xwiki-model with only the clean apis
>> instead of having clean and bridge in the same project.
>>
>>>
>>> Thanks
>>> -Vincent