Hi Zhong,
Happy new Year (I'll come up with a longer email a little later).
You are welcome to help on the migration to maven 2. I know Vincent did
a first try when Maven was still alpha. I'll check with him to see if
there is anything usable from his work.
Indeed it would be great to create some submodules for each XWiki
module. This of course needs a little discussion to decide what you be a
module and what should be in the core.
I think a first split would be:
core
core-doc
core-objects
core-api
core-web
store-rcs
store-hibernate
render
render-radeox
render-velocity
render-groovy
user-xwiki
user-ldap
user-exo
plugin
plugin-core
plugin-packaging
plugin-fileupload
plugin-xyz
stats
pdf
xmlrpc (or webservice)
It might be a little too detailed. I think in the process of splitting
in modules we might want to use a container system.
We've been discussing OSGi with Mandriva and eXo is using
picocontainer.. It might be a good time to think about it more in details.
Indeed it will have some impact in the development. I suggest we do this
on a branch. The objective is to get out a new release with the wysiwyg
editor and the new skins, so this should be work for the next release
Ludovic
Zhong ZHENG a écrit :
Hi the XWiki Team,
I found in the mailing list archives that you are planning to use
maven to build xwiki. I am a committer to the apache pluto project,
which uses maven2. Thus i got some experience on maven 2. (Mr. Vincent
Massol must be a maven master, since he is on the maven team :) I
would like to help you migrate to maven.
I checked out the xwiki source from subversion, and am trying to
re-organize the project layout and create pom.xml files. Currently i
am still dealing with the dependencies. I would like to propose to
separate the xwiki project into small subprojects, and decouple the
APIs from the implementation (such as user api and different
implementations, plugin api and different plugin implementations,
etc.). That will make the source more clear and more readable.
I don't know how to help on this topic. Re-organizing the project
layout introduces too many modifications on the project, which may
have a lot of impacts on the current development, and it's difficult
to generate svndiff and create patches. I would like to know if it is
possible to apply for joining the dev team and create a new branch in
svn for the maven migration.
I am taking a look at the JCR spec currently, since I created a java
wiki engine project (
http://people.apache.org/~zheng/elsie/
<http://people.apache.org/%7Ezheng/elsie/> ) and am thinking of
refactoring it using JCR and apache jackrabbit. I found that you are
also planning to implement the xwiki repository using JCR. I would
like to help and contribute to this subproject too.
Best regards.
--
ZHENG Zhong
-
http://heavyz.blogspot.com/
-
http://people.apache.org/~zheng/ <http://people.apache.org/%7Ezheng/>
------------------------------------------------------------------------
--
You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws