On Thu, May 26, 2011 at 17:11, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Thu, May 26, 2011 at 16:56, Bogdan Flueras
<flueras.bogdan(a)gmail.com> wrote:
Hello devs,
Today I've cloned the xwiki - {platform and commons} modules from GitHub.
1) When I tried to build the platform module it gives me a strange
error. See it at
http://pastebin.com/HMTLkc76.
It's xwiki-commons-tool-xar-handlers.3.1-SNAPSHOT dependency that is not
fetched correctly.
In an attempt to fix it, I've cleaned my local repo and forced updates
via mvn .. -U command line option.
So after getting the same error message [see above], I've inspected my
repo and the following files were found:
resolver-status.properties
xwiki-commons-tool-xar-handlers-3.1-SNAPSHOT.jar.lastUpdated
xwiki-commons-tool-xar-handlers-3.1-SNAPSHOT.pom.lastUpdated
All these files contain the same content:
#NOTE: This is an internal implementation file, its format can be
changed without prior notice.
#Thu May 26 16:37:28 CEST 2011
maven-metadata-xwiki-plugins-snapshots.xml.error=
maven-metadata-xwiki-plugins-snapshots.xml.lastUpdated=1306420648539
maven-metadata-xwiki-plugins-externals.xml.lastUpdated=1306420648539
maven-metadata-xwiki-plugins-externals.xml.error=
2) I've also tried to clone the xwiki-trunks module and to build it, but
I think there is a little inconsitency with respect to directory layout(
SVN layout). See the <parent> section where the relative path is
"commons" instead of xwiki-commons.
Of course that I can go to the problematic submodules and further
pinpoint the problem (this is what I will do now), but personally I
would like to do nothing more than a simple "mvn install" at the root of
the main module.
Thanks and looking forward hearing from you,
--
ing. Bogdan Flueras
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
I think you just found a problem in our nexus configuration which is
supposed to clean unused SNAPSHOT and the problem is that no
modification has been done for too long or the configuration is too
short. I will disable it and force a commons deploy for now. In the
meantime you could simply build commons since you cloned it.
Should be ok now (when commons and rendering build will bee finished
but at least I fixed the configuration).
Thanks for catching it, we all have commons in our local repository so
we would not have seen it before long I think.