Turns out mvn test filters for classes that have a name ending with Test. The test cases are all named ending with Tests.
Assaf On 12/14/06, Lance Waterman <[EMAIL PROTECTED]> wrote:
It doesn't look like a vendetta thing. Not sure why the plugin can't find the tests - I'll take a look. Lance On 12/13/06, Assaf Arkin <[EMAIL PROTECTED]> wrote: > > When I run bpel-test, I get "no tests to run". By design, or does Maven > have > something personal against me? > > Assaf > > On 12/13/06, Lance Waterman <[EMAIL PROTECTED]> wrote: > > > > Thanks Matthieu - yes I was trying to run the bpel-test. I'll check my > > Xalan > > jar. > > > > > > On 12/13/06, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > > > > I have before. Which tests are failing, the bpel-test ones? > > > > > > This is due to a bad version of Xalan. All Maven servers I've found > have > > a > > > Xalan 2.7.0 producing weird exceptions like this one (for a quick > check, > > > the > > > standard Xalan distro is 2.9MB whereas the corrupted one downloaded by > > > Maven > > > is 2.6MB). To get rid of this problem I've added our own Xalan > directly > > > from > > > the distro with a groupId of org.apache.ode (check the root pom). That > > > sort > > > of reduces the maven uncertainty principle. A bit. > > > > > > Matthieu > > > > > > On 12/13/06, Lance Waterman <[EMAIL PROTECTED]> wrote: > > > > > > > > I just pulled down the latest SVN image and I'm seeing most of the > > unit > > > > tests failing with parsing errors. Anyone else seeing this? > > > > > > > > NAMESPACE_ERR: An attempt is made to create or change an object in a > > way > > > > which is incorrect with regard to namespaces. > > > > > > > > Lance > > > > > > > > > > > > > > > > > > > > > -- > CTO, Intalio > http://www.intalio.com > >
-- CTO, Intalio http://www.intalio.com
