14 Feb
2007
14 Feb
'07
11:19 p.m.
I think we should keep Curriki for multiple reasons:
1/ To have it's own OW2 project it might be needed to ask for it and
Curriki might not be considered something OW2 will want to see as a top
level project
2/ It's good for XWiki to host some of it's application.
3/ There are some more applications like that: Curriki is one,
Chronopolys is going to be another, the RSS Reader another.
4/ It would be a pain to have separate projects for this.
I like the idea of having a top directory which separated the XWiki Core
system from the XWiki based projects
I also think that there should still be a sandbox
xwiki/
|_ xwiki
|_ curriki
|_ chronopolys
|_ rssreader
|_ sandbox
|_ ...
Ludovic
Vincent Massol a écrit :
Hi ,
I'm continuing my search of a perfect SVN directory structure. Here's
my latest proposal which I'd like to share with you:
xwiki/
|_ xwiki-core/ (*) --> JAR, WAR
|_ xwiki-plugins/ --> JAR
|_ xwiki-applications/ (**) --> XAR
|_ xwiki-clients/
|_ xwiki-tools/
|_ xwiki-distributions/ (**) --> ZIP, TGZ, EXE
|_ xwiki-tests/ (**)
(*) renamed from xwiki/ in xwiki-core/. xwiki-core/ will in the future
contain the different components of the core, split into different
build modules.
(**) new directories
- xwiki-applications/: see previous email proposition on that.
- xwiki-distributions/: XWiki distributions. Will currently contain
only the standalone distribution (as tgz and exe) but will contain
other distribs in the future. Like the standalone distribution on
Tomcat with MySQL, like a J2ME distribution, etc.
- xwiki-tests/: functional tests. Depends on almost all other
artifacts (xwiki-core, plugins, applications, distributions). Do not
depend on xwiki-clients/
You may notice that I haven't put xwiki-extensions/ in there, which
was in my previous email for putting Curriki. After thinking this
through, I really think Curriki should not be in the XWiki SVN. I
believe we should create a new ObjectWeb project called Curriki or
XWiki Curriki and it should have its own SVN. This is because the
xwiki/ dir should really be about XWiki as the platform. In addition
SVN commit rights might be different, lifecycles and releases are
different, etc. If we decide that Curriki should stay then we'll need
to reorganize the full structure as:
xwiki/
|_ xwiki/
|_ xwiki-core/ (*) --> JAR, WAR
|_ xwiki-plugins/ --> JAR
|_ xwiki-applications/ (**) --> XAR
|_ xwiki-clients/
|_ xwiki-tools/
|_ xwiki-distributions/ (**) --> ZIP, TGZ, EXE
|_ xwiki-tests/ (**)
|_ curriki/
In the meantime (ie. while we debate this particular point) we can
move curriki in xwiki-extensions. But really if Curriki was part of
XWiki it should be split in xwiki-plugins/ (for curriki-specific
plugins), xwiki-applications/wikis/curriki (for the curriki XAR) and
xwiki-distributions/curriki (for the Curriki distributions). However I
don't think Curriki is part of the XWiki platform.
Last I'm not sure but I think we should probably merge xwiki-clients
and xwiki-tools but that can wait.
Thanks
-Vincent
___________________________________________________________________________Yahoo!
Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son
interface révolutionnaire.
http://fr.mail.yahoo.com
------------------------------------------------------------------------
--
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
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic