On 19.11.12 09:52, Georg Kallidis wrote: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2. > 12:test (default-test) on project turbine: No tests were executed! (Set > -DfailI > fNoTests=false to ignore this error.) -> [Help 1] > > Environment: Maven 3.0.4, Java 1.6.0_29, 32bit, windows xp (the same for > Java 1.7 and windows 7, c.p.). May be this is a windows problem. I > digged not much further into details, might be related to a fork issue > resolved in version 2.12.2.
Maven 2.2.1/JDK 1.6.0_37/Mac OSX 10.6 works fine here. > As the parent is just released, we have to overwrite the surefire > version in the turbine trunk, if we do not want instantly move to a > newer parent. > > Anyone with a better idea? Well, the people at commons release their parent pom with "lazy consensus", i. e. if nobody objects, the artifact is pushed out. Do we want to do something similar? Opinions? In any case, please do the fixes for the POM in the 3-SNAPSHOT and try a "mvn deploy" (given that your Maven setup is prepared as described in http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env). I'll try with Maven 2.2.1 then. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@turbine.apache.org For additional commands, e-mail: dev-h...@turbine.apache.org
