15 Apr
2008
15 Apr
'08
12:01 p.m.
On Apr 15, 2008, at 11:51 AM, Jean-Vincent Drean wrote:
Sure that's fine with me to create a single module for now. Just not
sure how to name it then. xwiki-xmlrpc-model?
thanks
-Vincent
On Tue, Apr 15, 2008 at 11:23 AM, Vincent Massol
<vincent(a)massol.net> wrote:
They're all core modules and all produce jars. I don't think it
matters if the jar includes components or not.
I don't agree then, -1 from me. This definitely looks like something
that goes in the platform or I've missed something...
I have no idea what it means to have a directory at the same level as
platform and products. It would mean it's not platform related and
it's not a product either.
In the first place I've put a xwiki-xmlrpc module into
xwiki-platform-core (almost the same as your proposal bellow), what
bothered me was to have a library at same level as components, without
a clear differentiation. The only thing I propose to put in it (at least
for the moment) is
the
swizzle replacement Fabio wrote, a standalone library containing
both
xwiki xmlrpc model and client code (like swizzle).
I think I don't understand what you're proposing.
More specifically why do you want to introduce a xwiki-commons
directory? Why not
create:
xwiki-platform-core/xwiki-xmlrpc/
|_ xwiki-xmlrpc-model/
|_ xwiki-xmlrpc-client/
About splitting into model&client, we discussed that with Fabio and
since the client is only one java class we agreed that it was a bit
overkill to have a module for it. Wdyt ?