When looking into a build issue it was discovered test from other modules (like kew) are depending on the test module from Rice core. A suggestion was made to create a shared test module instead of relying on the core test module:

I honestly don't know the solution to your problem. But it makes me wonder if we need to have some kind of core test module which has shared testing code in it? Might be less peculiar than depending on test jars from the core module? Just a thought.

Sent from my iPhone

On Jul 25, 2012, at 9:17 AM, "Jerry Neal" <jkneal@indiana.edu> wrote:
Hi Everyone,

Matt has been having problems building locally due to a maven error about a missing rice dependency in Nexus:
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:55.898s
[INFO] Finished at: Fri Jul 20 15:53:43 EDT 2012
[INFO] Final Memory: 53M/495M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project rice-kew-api: Could not resolve depend
encies for project org.kuali.rice:rice-kew-api:jar:2.2.0-M3-SNAPSHOT: Could not
find artifact org.kuali.rice:rice-core-api:jar:tests:2.2.0-M3-SNAPSHOT in kuali.
nexus (http://nexus.kuali.org/content/groups/public) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit