Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-7760

Create shared test module instead of relying on test module from Rice core

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-4826Create a top level test module
      KULRICE-13086Create module IT CI jobs
      KULRICE-2186Remove remaining "module-specific" maven modules from Rice and get unit tests working within a single module
      KULRICE-4793Create a development support module in rice.
      KULRICE-4633Break out core into it's own module
      KULRICE-6843Create groovy folders in core-service-framework and core-service-web modules (src/test/groovy) to allow eclipse to compile
      KULRICE-2975Move KEW HtmlUnit tests into the "web" module
      KULRICE-5612Check in selenium tests to rice-sampleapp module
      KULRICE-8616Wrong slf4j-log4j12 version resolved when depending on rice-core-impl
      KULRICE-2079Move XAPoolDataSource from kns to shared module
    • Rice Module:
      Rice Core
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      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

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel