[xwiki-devs] my attempt at building a development curriki

[Paul Libbrecht]

Le 03-juin-08 à 10:23, Vincent Massol a écrit :
> The curriki project is a separate project from the xwiki products (XE,
> XEM, etc) and should actually have its own mailing list, SVN
> repository, etc (this will be done in the future when an admin can
> free up some time). I'm personally NOT a committer on it and I haven't
> participated on it except helping initially when someone had to
> volunteer to write its build. Since then I haven't touched it and I
> don't want to touch it since I'm not part of the project.

I this case, I think the devs at xwiki.org mailng-list is appropriate  
since it's a quite general question about building your own derivative  
of XWiki...

Please insist if you think curriki discussion is polluting the XWiki  
dev list, this can be easily set-up.
I was more under the impression that, as long as there's the curriki  
word in the subject, it is good practice to stay on devs at .

> FWIW we're using Maven2 for building XWiki Core, XE, XEM, XWiki Watch
> and XWS and we're not finding it blocking in any way. And no we don't
> have any manual step and it's all automated. So I'd assume the problem
> is not with Maven2 itself.

Except that you have already an amount of custom plugins made for that.

Basically, ant-scripting, as can be done with the ant-run plugin I  
just discovered, pumps into the huge wealth of those ant-tasks that  
have been realized.

Such things as a change-file-name is not very specific, but something  
that does not yet have a maven plugin but has an ant task (this is a  
factor 100) can take advantage of it.

really wishing curriki discussion to leave?

paul