3 Jun
2008
3 Jun
'08
10:23 a.m.
Hi Paul,
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.
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.
Thanks
-Vincent
On Jun 3, 2008, at 10:03 AM, Paul Libbrecht wrote:
Le 03-juin-08 à 09:03, Vincent Massol a écrit :
In a perfect world I agree...
Untill then, something has to be done.
I searched ~/.m2/repository/com/google/gwt/ and there's not single
script in there.
I know ant is old-fashioned but please... a script there would have
made things very easy!
The
location was determined when xwiki was using Ant instead of
Maven
and I have not found how to pass the appropriate options to the
Maven
gwt compiler that would put the compiled code in the right location,
nor how to run a post-compile move of the directory as an
alternative.
post-compile move is an "Ant"ish thing and should be avoided if
possible. One thing you could do is check the sources of
the GWT plugin. I do
that frequently with the other plugins and it helps. If that doesn't
work maybe you could ask on the GWT plugin's mailing list/forum.
That seems like a non-trivial thing to do, at least their docs do not
show the properties for such settings.
From their documentation page:
http://code.google.com/p/gwt-maven/
(supposedly)
I seem to find that there's a property for maven1 but not for maven2
plugin:
google.webtoolkit.output
PS: I'm not even understanding what
you're trying to do so I'm just
answering generically here.
a post-compile move is what we are trying to do without considering
writing a plugin for such a task!
Following the curriki installation task-list.
http://curriki.xwiki.org/xwiki/bin/view/Main/
InstallationInstructions
where there are more of these manual moves which are fully natural
things in a world that is almost perfect.
paul
(wishing curriki went to maven-1.1! ;-))