Brett Porter wrote: >> >>1) java.lang.OutOfMemoryError. I can't really say what triggers this, >>but it happens every now and then when doing a full build of all modules. > > > Others have had success skipping tests. We'll have forking of tests > available soon which will also help. We're yet to determine if the > leak is in tests themselves or in surefire - can I check out cocoon > and run m2 package at the root to replicate it? >
because some of our tests are failing and we haven't been good in fixing them, i always build with -Dmaven.test.skip=true By all means, check out cocoon 2.2.x [1] , and from the root do install or package. >>2) a module fails to build during full build, complaining about missing >>poms or invalid dependencies. However when I then go and build the >>module independent of the full build it's fine again - without changing >>anything. This behaviour is not specific to one particular module. > > > Probably need more info here - it's weird. It's hard to reproduce - but I know of at least one other person who has noticed this. Can I enable some full trace logging somehow, would this help? Regards Jorg [1] http://svn.apache.org/repos/asf/cocoon/trunk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
