15 Apr
2005
15 Apr
'05
8:24 a.m.
Hi everyone,
(switching list)
I really don't understand what is the problem with the:
xwiki/
xwiki-plugins/
directory structure.
Do you put all your files in a single directory on your machine? I believe
not. I'm sure you're using folders.
xwiki/
plugin1/
plugin2/
...
pluginN/
will work well *only* if we have very few plugins (and I don't think that's
the plan! :-)).
In addition it's not balanced with the xwiki/ directory. We could also have
xwiki-core/, xwiki-plugin-manager/, xwiki-persistence/, etc at the top level
but we don't. Why? Because it's better organized to have them under xwiki/
as they all are about the xwiki engine proper. The same applies for the
plugins. They are all plugins.
Also there are other things than plugins. Imagine some other extensions or
other applications built on top of xwiki. Say an issue tracker for example.
It would then go in:
xwiki/
xwiki-plugins/
xwiki-tracker/
[...]
It would really be a mess to mix all the plugins at the top level with other
things.
I don't understand what's your issue with multiple level directories. I
guess you haven't seen a Maven directory structure yet too! ;-) Once and if
we migrate to Maven, I can tell you that the structure inside xwiki/ is
going to contain *lots* of directories! :-)
I hope I have convinced you a little more...
Thanks
-Vincent
-----Original Message-----
From: developers-bounces(a)xwiki.org [mailto:developers-bounces@xwiki.org]
On Behalf Of Luis Arias
Sent: jeudi 14 avril 2005 19:50
To: XWiki.org Developers Mailing List
Subject: Re: [VOTE] Moving some directories in SVN
Hi All,
+1 for this structure which seems real clean and extensible. Don't
like the two level hierarchy for the plugins Vincent proposed in his
later post too much.
Looking forward to participating in this community !
Luis.
On 4/14/05, Jiri Luzny <jiri.luzny(a)seznam.cz> wrote:
would
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
--
Luis Arias
http://www.xwiki.com
http://www.innover-entreprendre.net
+33 6 14 20 87 93 mobile
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
[REPOROOT]/
|_ xwiki/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin1/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin2/
|_ trunk/
|_ branches/
|_ tags/
[+1]
IMHO it's more flexible and at the root level I would also add other
tools that are not XWiki plugins like xwiki-scripts,
xwiki-eclipse-client etc.. in future.
PS: Ludovic, I'm still working on the email
notification thing. Hope to
get a working version ready this week.
cool, cannot wait for it! The simple email notification workaround
(http://www.xwiki.org/xwiki/bin/view/Dev/RecentChangesNewsletter) we
use at my company is quickly reaching its limits ;-)
Jiri.
On Wed, 13 Apr 2005 18:08:41 +0200, you wrote:
>Hi all,
>
>just read through the mails of the last days - this really seems to
>become a high traffic list now :-)
>
>On Wed, Apr 13, 2005 at 05:04:20PM +0200, Vincent Massol wrote:
>[..]
>> This is not right. I'd like to transform it into:
>>
>> [REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ [branchname]
>> |_ tags/
>> |_ [tagname]
>
>+1 for this one.
>
>> And then if we want want to add a xwiki-plugins project later on we >> have:
>>
>> [REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>> |_ xwiki-plugins/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>>
>> This follows the standard SVN directory structure defined in
>> http://tinyurl.com/4dhja.
>>
>> One reason is that the release lifecycle of xwiki/ and xwiki-plugins/
will
>> probably be different (you can release a
newer version of a plugin
even if
the core is not released again).
here I would vote for each plugin having it's own set of
trunk/branches/head directories. I think different plugins will have
different development cycles, and imho one would not want to branch all
plugins just because one plugin is undergoing major changes.
so I would suggest an architecture like this:
[REPOROOT]/
|_ xwiki/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin1/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin2/
|_ trunk/
|_ branches/
|_ tags/
Greetings,
Jens
PS: Ludovic, I'm still working on the email notification thing. Hope to
get a working version ready this week. 
15 Apr
15 Apr
9:33 a.m.
New subject: [xwiki-dev] RE: [VOTE] Moving some directories in SVN
It's true that in the beginning the multiple levels might look a little
weird, but I agree that long term it would better look if it was
something like that:
xwiki/
xwiki-plugins/
- emailnotification
- lucene
- calendar
- lotusnotes
- msexchange
- sap
- etc...
xwiki-apps/
- ...
- ...
xwiki-clients/
- eclipseclient
- xulclient
- ...
This is of course ambitious.. but there are early signs that plugins
will be something that will be growing quickly.
So I give my +1 to a multiple level organisation which allows each
module to have their own lifecycle..
Ludovic
Vincent Massol a écrit :
Hi everyone,
(switching list)
I really don't understand what is the problem with the:
xwiki/
xwiki-plugins/
directory structure.
Do you put all your files in a single directory on your machine? I believe
not. I'm sure you're using folders.
xwiki/
plugin1/
plugin2/
...
pluginN/
will work well *only* if we have very few plugins (and I don't think that's
the plan! :-)).
In addition it's not balanced with the xwiki/ directory. We could also have
xwiki-core/, xwiki-plugin-manager/, xwiki-persistence/, etc at the top level
but we don't. Why? Because it's better organized to have them under xwiki/
as they all are about the xwiki engine proper. The same applies for the
plugins. They are all plugins.
Also there are other things than plugins. Imagine some other extensions or
other applications built on top of xwiki. Say an issue tracker for example.
It would then go in:
xwiki/
xwiki-plugins/
xwiki-tracker/
[...]
It would really be a mess to mix all the plugins at the top level with other
things.
I don't understand what's your issue with multiple level directories. I
guess you haven't seen a Maven directory structure yet too! ;-) Once and if
we migrate to Maven, I can tell you that the structure inside xwiki/ is
going to contain *lots* of directories! :-)
I hope I have convinced you a little more...
Thanks
-Vincent
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
-----Original Message-----
From: developers-bounces(a)xwiki.org [mailto:developers-bounces@xwiki.org]
On Behalf Of Luis Arias
Sent: jeudi 14 avril 2005 19:50
To: XWiki.org Developers Mailing List
Subject: Re: [VOTE] Moving some directories in SVN
Hi All,
+1 for this structure which seems real clean and extensible. Don't
like the two level hierarchy for the plugins Vincent proposed in his
later post too much.
Looking forward to participating in this community !
Luis.
On 4/14/05, Jiri Luzny <jiri.luzny(a)seznam.cz> wrote:
would
--
Luis Arias
http://www.xwiki.com
http://www.innover-entreprendre.net
+33 6 14 20 87 93 mobile
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : 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
[REPOROOT]/
|_ xwiki/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin1/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin2/
|_ trunk/
|_ branches/
|_ tags/
[+1]
IMHO it's more flexible and at the root level I would also add other
tools that are not XWiki plugins like xwiki-scripts,
xwiki-eclipse-client etc.. in future.
PS: Ludovic, I'm still working on the email
notification thing. Hope to
get a working version ready this week.
cool, cannot wait for it! The simple email notification workaround
(http://www.xwiki.org/xwiki/bin/view/Dev/RecentChangesNewsletter) we
use at my company is quickly reaching its limits ;-)
Jiri.
On Wed, 13 Apr 2005 18:08:41 +0200, you wrote:
>Hi all,
>
>just read through the mails of the last days - this really seems to
>become a high traffic list now :-)
>
>On Wed, Apr 13, 2005 at 05:04:20PM +0200, Vincent Massol wrote:
>[..]
>
>
>>This is not right. I'd like to transform it into:
>>
>>[REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ [branchname]
>> |_ tags/
>> |_ [tagname]
>>
>>
>+1 for this one.
>
>
>
>>And then if we want want to add a xwiki-plugins project later on we
>>
>> >>have:
>>
>>[REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>> |_ xwiki-plugins/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>>
>>This follows the standard SVN directory structure defined in
>>http://tinyurl.com/4dhja.
>>
>>One reason is that the release lifecycle of xwiki/ and xwiki-plugins/
>>
>>
will
>>probably be different (you can release a
newer version of a plugin
>>
>>
even if
>the
core is not released again).
>
>
here I would vote for each plugin having it's own set of
trunk/branches/head directories. I think different plugins will have
different development cycles, and imho one would not want to branch all
plugins just because one plugin is undergoing major changes.
so I would suggest an architecture like this:
[REPOROOT]/
|_ xwiki/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin1/
|_ trunk/
|_ branches/
|_ tags/
|_ xwiki-plugin2/
|_ trunk/
|_ branches/
|_ tags/
Greetings,
Jens
PS: Ludovic, I'm still working on the email notification thing. Hope to
get a working version ready this week.
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
19 Apr
19 Apr
1:25 a.m.
New subject: [xwiki-dev] RE: [VOTE] Moving some directories in SVN
Hi list,
sorry for replying somewhat late, I'm quite busy atm.
The main point I wanted to make with my proposal was that each plugin
should get it's own release cycle and therefore it's own
trunk/tags/branches directories.
Being a fan of flat hierarchies I suggested the hierarchy with the
plugins at top level, but as long as each plugin gets it's own
trunk/tags/branches subdirs the approach below is absolutely fine with
me, too.
After all, one always can check out subtrees like
xwiki-plugins/calendar/trunk to a dir named xwiki-plugin-calendar,
creating a flat directory layout in the local filesystem.
Greetings,
Jens
On Fri, Apr 15, 2005 at 09:33:34AM +0200, Ludovic Dubost wrote:
It's true that in the beginning the multiple levels might look a little
weird, but I agree that long term it would better look if it was
something like that:
xwiki/
xwiki-plugins/
- emailnotification
- lucene
- calendar
- lotusnotes
- msexchange
- sap
- etc...
xwiki-apps/
- ...
- ...
xwiki-clients/
- eclipseclient
- xulclient
- ...
This is of course ambitious.. but there are early signs that plugins
will be something that will be growing quickly.
So I give my +1 to a multiple level organisation which allows each
module to have their own lifecycle..
Ludovic
Vincent Massol a écrit :
Hi everyone,
(switching list)
I really don't understand what is the problem with the:
xwiki/
xwiki-plugins/
directory structure.
Do you put all your files in a single directory on your machine? I believe
not. I'm sure you're using folders.
xwiki/
plugin1/
plugin2/
...
pluginN/
will work well *only* if we have very few plugins (and I don't think that's
the plan! :-)).
In addition it's not balanced with the xwiki/ directory. We could also have
xwiki-core/, xwiki-plugin-manager/, xwiki-persistence/, etc at the top
level
but we don't. Why? Because it's better organized to have them under xwiki/
as they all are about the xwiki engine proper. The same applies for the
plugins. They are all plugins.
Also there are other things than plugins. Imagine some other extensions or
other applications built on top of xwiki. Say an issue tracker for example.
It would then go in:
xwiki/
xwiki-plugins/
xwiki-tracker/
[...]
It would really be a mess to mix all the plugins at the top level with
other
things.
I don't understand what's your issue with multiple level directories. I
guess you haven't seen a Maven directory structure yet too! ;-) Once and if
we migrate to Maven, I can tell you that the structure inside xwiki/ is
going to contain *lots* of directories! :-)
I hope I have convinced you a little more...
Thanks
-Vincent
--
Ludovic Dubost
XPertNet: http://www.xpertnet.fr/
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost AIM: nvludo Yahoo: ludovic
-----Original Message-----
From: developers-bounces(a)xwiki.org [mailto:developers-bounces@xwiki.org]
On Behalf Of Luis Arias
Sent: jeudi 14 avril 2005 19:50
To: XWiki.org Developers Mailing List
Subject: Re: [VOTE] Moving some directories in SVN
Hi All,
+1 for this structure which seems real clean and extensible. Don't
like the two level hierarchy for the plugins Vincent proposed in his
later post too much.
Looking forward to participating in this community !
Luis.
On 4/14/05, Jiri Luzny <jiri.luzny(a)seznam.cz> wrote:
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : 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
>[REPOROOT]/
> |_ xwiki/
> |_ trunk/
> |_ branches/
> |_ tags/
> |_ xwiki-plugin1/
> |_ trunk/
> |_ branches/
> |_ tags/
> |_ xwiki-plugin2/
> |_ trunk/
> |_ branches/
> |_ tags/
>
>
[+1]
IMHO it's more flexible and at the root level I would also add other
tools that are not XWiki plugins like xwiki-scripts,
xwiki-eclipse-client etc.. in future.
>PS: Ludovic, I'm still working on the email notification thing. Hope to
>get a working version ready this week.
>
>
cool, cannot wait for it! The simple email notification workaround
(http://www.xwiki.org/xwiki/bin/view/Dev/RecentChangesNewsletter) we
use at my company is quickly reaching its limits ;-)
Jiri.
On Wed, 13 Apr 2005 18:08:41 +0200, you wrote:
>Hi all,
>
>just read through the mails of the last days - this really seems to
>become a high traffic list now :-)
>
>On Wed, Apr 13, 2005 at 05:04:20PM +0200, Vincent Massol wrote:
>[..]
>
>
>>This is not right. I'd like to transform it into:
>>
>>[REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ [branchname]
>> |_ tags/
>> |_ [tagname]
>>
>>
>+1 for this one.
>
>
>
>>And then if we want want to add a xwiki-plugins project later on we
>>
>>
would
>>have:
>>
>>[REPOROOT]/
>> |_ xwiki/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>> |_ xwiki-plugins/
>> |_ trunk/
>> |_ branches/
>> |_ tags/
>>
>>This follows the standard SVN directory structure defined in
>>http://tinyurl.com/4dhja.
>>
>>One reason is that the release lifecycle of xwiki/ and xwiki-plugins/
>>
>>
will
>>probably be different (you can release a
newer version of a plugin
>>
>>
even if
>>the core is not released again).
>>
>>
>here I would vote for each plugin having it's own set of
>trunk/branches/head directories. I think different plugins will have
>different development cycles, and imho one would not want to branch all
>plugins just because one plugin is undergoing major changes.
>
>so I would suggest an architecture like this:
>
>[REPOROOT]/
> |_ xwiki/
> |_ trunk/
> |_ branches/
> |_ tags/
> |_ xwiki-plugin1/
> |_ trunk/
> |_ branches/
> |_ tags/
> |_ xwiki-plugin2/
> |_ trunk/
> |_ branches/
> |_ tags/
>
>
>Greetings,
>Jens
>
>PS: Ludovic, I'm still working on the email notification thing. Hope to
>get a working version ready this week.
>
>
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
--
Luis Arias
http://www.xwiki.com
http://www.innover-entreprendre.net
+33 6 14 20 87 93 mobile
_______________________________________________
Developers mailing list
Developers(a)xwiki.org
http://www.xwiki.org/mailman/listinfo/developers
--
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
--
Jens Krämer
jk(a)jkraemer.net
7091
days inactive
7094
days old
2 comments
3 participants
participants (3)
-
Jens Kraemer -
Ludovic Dubost -
Vincent Massol