On 3/26/10 12:23 PM, Marcel Offermans wrote: > On Mar 26, 2010, at 8:19 , Guillaume Nodet wrote: >> On Fri, Mar 26, 2010 at 15:58, Sahoo <sa...@sun.com> wrote: >>> Pierre De Rop wrote: >>>> However, the -Dmaven.test.skip=true option still has to be used because >>>> there is one pending issue in the DependencyManager junit tests, which has >>>> to be fixed. This is a known issue, and it's referenced here: >>>> http://issues.apache.org/jira/browse/FELIX-2078. >>> >>> >>> Why don't we exclude the test until it is fixed? That will keep CI server >>> to function as well. >>> >> > >> That's a good idea ;-) > > Whilst I don't mind too much doing that, I'm wondering why our build cannot > support subprojects that have failing tests? I mean as long as I'm not > releasing anything, a project that is in flux might have a few test cases > that are broken, right? That should not affect our whole build in a way that > it makes life hard on everybody else. > > Is it really not possible to have a solution where having tests that fail is > not a problem? Pass -fae to the maven command. This tells Maven that if a module fails in the reactor it should continue with the next buildable module (meaning one that doesn't have a dependency upon the failed module). (fae = fail at end).
However, this isn't going to resolve a cyclical dependency; nothing will. That just needs to be resolved. HTH, Justin > > If not, then just disable that test for now. > > Greetings, Marcel >
