18 Jul
2008
18 Jul
'08
3:22 p.m.
Thank you Jean-Vicent for the info, it's very useful.
(I leave here my suggestion to add this sort of info somewhere, maybe at the
Community.Building page at dev.xwiki.org, when anybody happens to have time
for it ;-))
Thanks!
On Fri, Jul 18, 2008 at 3:02 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
On Fri, Jul 18, 2008 at 2:50 PM, Tiago Rinck Caveden
<caveden(a)gmail.com>
wrote:
--
Tiago Rinck Caveden
http://caveden.multiply.com
May I ask one more question? :P
Apparently the mvn clean on the root directory was not really cleaning
everything, since the build was getting an older version of the cfg file
from somewhere else.
The root pom.xml default profile (xe) doesn't reference
xwiki-platform-tools so you were always getting a config resources
tool from our repository (since yours wasn't built).
See : http://svn.xwiki.org/svnroot/xwiki/trunks/pom.xml
If you want to build everything including tools you have to do : mvn
install -Pall
So, how do you do in the development team? Is
there
another way to force a full rebuild or you simply build this particular
module in separate when you change configuration files (and for
everything
else maven does the work)?
We don't modify xwiki.cfg very often but, when we do it and commit it,
the continuous build push the new config resources tools on our maven
repo.
In your case I'd advice not to modify this tool but to make
modifications to xwiki-product-enterprise/web/pom.xml instead.
See :
http://svn.xwiki.org/svnroot/xwiki/xwiki-products/xwiki-enterprise/trunk/we…
You can use xwikiCfgAdditionalProperties to add anything you want to the
cfg.
--
Jean-Vincent Drean
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs