4 Sep
2008
4 Sep
'08
6:04 p.m.
Tiago Rinck Caveden wrote:
On Thu, Sep 4, 2008 at 11:10 AM, Vincent Massol
<vincent(a)massol.net> wrote:
If you build only that module, then it won't be OK.
XE includes all other modules in the XE/web module.
XE/web depends on platform/web.
platform/web depends on the core.
The core depends on the parent pom.
So, if you don't build one of the items from this dependency chain, it
will be downloaded from the external repositories.
To make sure your changes are found in the final XE archive, you should
build the whole platform trunks, then build the enterprise project using
the -o maven parameter.
If it doesn't work, then somebody forgot to update some of the
dependency versions, and the wrong pom ends up in the build. You should
check the version in the modified pom and the one in the resulting archive.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Maven uses the most recent dependencies, first
looking in your local
repository. So if you have built it this will be the most recent
Well, then maybe what I'm expecting is not right anymore.
I changed the platform/pom/pom.xml, the goal was to change the generated
xwiki.cfg. I changed the xwikiCfgPlugins and the
xwikiCfgAdditionalProperties. But these changes are not propagating to the
final xwiki.cfg.
Should they propagate or it doesn't work like that anymore?