10 Jul
2015
10 Jul
'15
10:18 a.m.
Actually I think I just found why 3.0.5 is not happy (but I can't see
how 3.3.3 can work): you kept 7.2-SNAPSHOT in the pom when you merged
the new module to 7.1.x branch.
See
https://github.com/xwiki/xwiki-platform/blob/stable-7.1.x/xwiki-platform-co…
On Fri, Jul 10, 2015 at 10:03 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
No much other ideas than trying to workaround the
Maven bug. Now it's
not like the plan was to go back to an older version of Maven, using
the last version would be logical anyway (provided the plugins we are
using don't have issues on it).
I'm still using 3.0.5 myself partly because people using more recent
versions of Maven like you often report issues with dependencies
resolution.
On Fri, Jul 10, 2015 at 9:02 AM, vincent(a)massol.net <vincent(a)massol.net> wrote:
--
Thomas Mortagne
Hi devs,
From IRC yesterday:
“
- guys
- seems we have a problem with maven 3.0.5 on jenkins
- http://ci.xwiki.org/job/xwiki-platform-7.1.x/56/consoleFull is failing because maven
doesn't build the modules in the right order
- url-scheme-filesystem is built after oldcore
- with maven 3.3.1 locally the order is correct and when I switched to maven 3.0.5
locally I was able to get the wrong order too
- so it seems there's a bug in 3.0.5 on the reactor ordering
- I wonder if we shouldn't try to upgrade to 3.3.3 on the agent
- does anyone any issue with 3.3.3 for us?
“
WDYT? Any other idea?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne