Thanks Justin, again for looking into details. On Thu, May 7, 2015 at 4:10 AM, Justin Mclean <[email protected]> wrote: > > AFAIK, i think this is not a test failure issue, but the first time > creation of db might be giving this error. We can create tracking jira to > remove such exceptions from console. > > > BTW - this stops the build from completing. I had to not run the tests in > order to get everything to compile. > > I know that the module you are building here which logs the exception, actually takes few minutes to run all tests - sometimes more than 5 minutes. I hope thats what you saw while building and thought build is stopped. Otherwise, I'm afraid that we don't know of the reason why the build got stopped.
> Default MAVEN_OPTS should work for lens. > > > It didn't on my machine and ran out of memory, but as they say your milage > may vary. > > Sure. It make sense to put indicative MAVEN_OPTS values in README. Will update accordingly. > The only thing i know of test setup is having JAVA_HOME defined. Anyone > else have more ideas here on what can be improved? > > > Adding a couple of lines to README would IMO help, but again nothing is > required. > > Sure. Will update an expectation time for test run to finish overall. > >> Pom.xml lists developers and their companies, s > > > oftware is developed by individuals at the the ASF > > Many projects have the affiliations mentioned, should we really remove > affiliations from developers? > > > IMO they probably shouldn’t, but that up to you as a project to decide > upon. Perhaps note this [2][3]. > > Sure, makes sense. Will go ahead and remove them. > > 1. http://www.apache.org/legal/src-headers.html > 2. http://apache.org/foundation/faq.html#corporate-membership > 3. http://apache.org/foundation/how-it-works.html#hats >
