Fixed
Stephen Duncan wrote: > It's because "protocol" wasn't added as a module in the top-level > pom.xml, so it's not included when trying to build from that level. > > -Stephen > > On 9/8/06, Ugo Cei <[EMAIL PROTECTED]> wrote: >> There is something strange in maven-land here, because if I clean my >> m2 cache and run mvn install from trunk I get: >> >> [INFO] Scanning for projects... >> [INFO] Reactor build order: >> [INFO] JSON (From Abdera) >> [INFO] Apache Abdera >> [INFO] Abdera Core >> [INFO] Abdera Parser >> [INFO] Abdera Client >> [INFO] Abdera Security >> [INFO] Abdera Server >> [INFO] Abdera Extensions >> [INFO] Abdera Examples >> >> Where is Abdera Protocol? There is a dependency on it in client/ >> pom.xml, still it doesn't get built, which leads to client's >> compilation failing. >> >> If I go to protocol and run mvn install there, it builds, then I can >> go back up and build everything fine (well, if I use - >> Dmaven.test.skip=true, because one test is failing). >> >> I cannot fathom why this is happening. >> >> Ugo >> >> > >
