30 Dec
2006
30 Dec
'06
7:17 p.m.
On Saturday 30 December 2006 05:59, jeremi joslin wrote:
On 12/27/06, Vincent Massol <vincent(a)massol.net>
wrote:
It makes sens to have it sync. But someone who just want the source
code of the core of xwiki does not want xwiki.org pages. We should try
to keep the core code as small as possible I think. And xwiki.org is
not all about the core, it's also about plugins, applications who have
there own lifecycle. I would prefer to have it somewhere else on the
repository, even if we tag it at the same time as the xwiki core.
In svn we have a unique revison number for all the repository, so it's
already sync.
What do you think?
Good question Jeremi.
How do I make and plug my XWiki initial pages to a customized instance of
XWiki?
Can this process be automated in some way that the user could point to her set
of initial pages?
-----Original Message-----
From: jeremi23(a)gmail.com [mailto:jeremi23@gmail.com] On Behalf Of
jeremi joslin
Sent: mercredi 27 décembre 2006 14:20
To: xwiki-dev(a)objectweb.org
Subject: Re: [xwiki-dev] [Proposal] Create wikis/ module in SVN
Hi,
it's a good idea to save xwiki.org on the svn. But i'm not sure it's a
good idea to put it in the same trunk as xwiki core. I would prefer to
have it somwhere else.
I would like to do it in 2 steps:
* step 1: create them in xwiki/xwiki/trunk.
* step 2: create some other place later on when we have our structure
cleaned up more.
One rationale now is to have the same release cycle for the site
(xwiki.org) as for the code so I think it makes sense, for now at least,
to have it in the same place as the code. From the point of view of the user, developing an
application on top of XWiki,
it would be nice to have some control over the initial
state of the database.
Is there some documentation on that topic?
As far as I understand an application can be packaged (exported from the dev
station) as a XAR file (spanning many spaces for example).
However, if the application needs a plugin or an additional radeox filter or
macro for example, then the code source needs to be modified and repackaged.
One requirement for any application I guess would be to make it easy to move
to an upgraded XWiki instance. XAR files are great help for that matter. But
when classes are added/modified from the source code, another solution is
needed (like a custom ant file based on the xwiki ant file).
But once an ant file is in place, it could be easy to customize the initial
state of the database as well?