Mule

Move TCK classes and core tests back into core project

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Core: API
  • Labels:
    None
  • Similar Issues:
    MULE-2929 Move tck classes out of core's main sources
    MULE-935 Move EJB dependent classes from Core to the EJB-provider
    MULE-910 Remove unneeded mule-core dependency on activeio
    MULE-1316 Move Spring 2.x into the core
    MULE-1772 Move the Mule Assembly Verifier out of the core
    MULE-5247 Mule project archetype is missing the core-test jar dependency
    MULE-975 Move org.mule.tck classes out to a separate module
    MULE-2503 Fix Tests in Mule Core
    MULE-1757 JavaDoc the TCK package
    MULE-932 Move OGNL code out of core into its own module

Description

This is the anti-bug to MULE-975, which really seems to be collateral damage of the m2 migration. The only downside of this is the new compile scope dependency of mule-core on junit & mockobjects but that is not much of a problem.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Holger Hoffstaette added a comment - 26/Feb/07 07:56 PM

done in r5298. tck may move into its own project again later but we need to clean up the UMO* interfaces first.

Show
Holger Hoffstaette added a comment - 26/Feb/07 07:56 PM done in r5298. tck may move into its own project again later but we need to clean up the UMO* interfaces first.

People

Vote (0)
Watch (0)

Dates

  • Created:
    23/Feb/07 06:18 PM
    Updated:
    26/Feb/07 07:56 PM
    Resolved:
    26/Feb/07 07:56 PM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.