Lee, Disregard my email. ;-) I thought the message was to myfaces-users. The two folders are next to each other in gmail. Sorry for the confusion.
Sean On 1/6/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > Lee, > > We're going to be moving the Maven stuff around tomorrow. Over the > next few days we should be settling on the final layout. Some of the > unit tests do not work (as you discovered) but should be excluded from > the build (for the moment.) > > Hopefully we'll get everything sorted out with lots of good docs to follow. > > Sean > > On 1/6/06, Lee Meador <[EMAIL PROTECTED]> wrote: > > I hate replying to myself. > > > > Even more than that I hate what I have to report. I don't really believe it > > myself but I saw it. > > > > This morning I came in. My computer was still running all the same stuff > > from yesterday. Eclipse was still running even. > > > > I did some Google type research and then fiddled with the classpath setting > > for a few jars and wars in my project. > > > > When I built, none of the failures I reported yesterday happened. I removed > > the xml stuff to ignore surefire errors/failures and verified it still > > works. > > > > I only tried it twice. I hate things to just start working because you never > > know when they will come back. > > > > Oh well. > > > > -- Lee Meador > > > > On 1/5/06, Lee Meador <[EMAIL PROTECTED]> wrote: > > > > > > More news: I told it to ignore surefire failures/errors on that project > > > and it failed on another (without excludes>. I repeated that a few times > > > but > > > it is still failing on a bunch of my projects' tests on "package" and the > > > exception that happens is that a class from one of my other projects is > > > not > > > found. All these tests still work for "site" or "test". > > > > > > What to do? > > > > > > Thanks. > > > > > > On 1/5/06, Lee Meador <[EMAIL PROTECTED]> wrote: > > > > > > > > I did notice (replying to my self) that the failing project is the only > > > > one with an <excludes> on the surefile plugin. > > > > > > > > On 1/5/06, Lee Meador < [EMAIL PROTECTED]> wrote: > > > > > > > > > > When I do 'mvn site' or 'mvn test' the tests run on all my projects. > > > > > They don't fail. > > > > > > > > > > When I do 'mvn package', one test fails. Two projects (including the > > > > > parent) have no tests. Then wo projects with tests succeed. Then two > > > > > projects with no tests. And then the failure happens on the next > > > > > project to > > > > > build. > > > > > > > > > > The failure is due to a java.lang.NoClassDefFoundError pointing to a > > > > > class that is in one of the earlier built projects' jar files. That > > > > > jar file > > > > > is in place and contains the class file. When I do -e -X it shows the > > > > > classpath on the test run and that jar file (the one with the class > > > > > that > > > > > can't be found) is listed. > > > > > > > > > > I have a parent/base project and a bunch of child projects sitting in > > > > > folder beside the folder for the parent. That leaves a lot of ".."s > > > > > in the > > > > > POMs but hasn't been a problem to this point. > > > > > > > > > > I don't know where to go from here. Help? > > > > > > > > > > Thanks. > > > > > > > > > > > > > > -- > > -- Lee Meador > > Sent from gmail. My real email address is [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
