Re: Running unit tests under maven2?

[Bill Dudney]

On Jan 9, 2006, at 7:37 PM, Wendy Smoak wrote: On 1/9/06, Bill Dudney <[EMAIL PROTECTED]> wrote: I've tried -Dmaven.test.skip=false and still the tests are skipped. I also did a quick find/grep and I could find no instance of <skip>true</skip> in any pom except the api/pom.xml. Weird, I'm still digging... That's the one... I'm not sure if this is correct, but the api/pom.xml has:   <groupId>org.apache.myfaces</groupId>   <artifactId>myfaces</artifactId>   <packaging>pom</packaging>   <version>1.1.2-SNAPSHOT</version> And tomahawk has:  <parent>     <groupId>org.apache.myfaces</groupId>     <artifactId>myfaces</artifactId>     <version>1.1.2-SNAPSHOT</version>   </parent> So that *is* tomahawk's parent pom, and that's why the skipped tests defined there are affecting tomahawk. Ah the artifactId, is what is causing it... I really think we need a top level pom that is obviously a top level pom. What does everyone think about deleting 'build' and moving that pom into current? So on checkout of 'https://svn.apache.org/repos/asf/myfaces/current' we'd get this structure; myfaces/pom.xml => the parent pom, groupId = org.apache.myfaces artifactId = myfaces myfaces/api/pom.xml => parent to api and assembly, child to myfaces/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-api-module myfaces/api/api/pom.xml =>  child to myfaces/api/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-api myfaces/api/myfaces-assembly/pom.xml =>  child to myfaces/api/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-assembly myfaces/commons/pom.xml =>  child to myfaces/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-commons myfaces/impl/pom.xml =>  child to myfaces/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-impl myfaces/sandbox/pom.xml =>  parent to sandbox, sandbox-assembly and sandbox-examples - child to myfaces/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-sandbox-module myfaces/sandbox/sandbox/pom.xml =>  child to myfaces/sandbox/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-sandbox myfaces/sandbox/sandbox-assembly/pom.xml =>  child to myfaces/sandbox/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-sandbox-assembly myfaces/sandbox/sandbox-examples/pom.xml =>  child to myfaces/sandbox/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-sandbox-examples myfaces/tomahawk/pom.xml =>  parent to tomahawk, tomahawk-assembly and tomahawk-examples - child to myfaces/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-tomahawk-module myfaces/tomahawk/tomahawk/pom.xml =>  child to myfaces/tomahawk/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-tomahawk myfaces/tomahawk/tomahawk-assembly/pom.xml =>  child to myfaces/tomahawk/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-tomahawk-assembly myfaces/tomahawk/ tomahawk-examples/pom.xml =>  child to myfaces/tomahawk/pom.xml groupId = org.apache.myfaces artifactiId = myfaces-tomahawk-examples I think we could also get rid of all the externals and have something like this; myfaces/trunk/pom.xml myfaces/trunk/api myfaces/trunk/commons myfaces/trunk/impl myfaces/trunk/sandbox myfaces/trunk/site myfaces/trunk/tomahawk Which would not prevent us from doing separate releases and tags for the separately released stuff. I'm not positive this is the right thing to do, I chatted with the maven folks though and they are doing something similar on the mojo and the maven.apache.org project. Thoughts? -bd- I would have thought myfaces-build would be the parent pom, but  haven't studied the changes made over the weekend other than to note that the build works. :) -- Wendy