[GORA-164] Use <type> instead of <classifier> configuration for test dependencies

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.2.1
• Fix Version/s: 0.3
• Component/s: build process, maven
• Environment: Maven 3
• Assignee: Lewis John McGibbney
• Reporter: Lewis John McGibbney
• Created: 06/Aug/12 17:06
• Updated: 01/Jul/13 05:05
• Resolved: 06/Aug/12 17:20

Description

Previous maven guides suggested to use <classifier>tests</classifier> instead of <type>test-jar</type>. While this currently works for some cases, it does not properly work during a reactor build of the test JAR module and any consumer if a lifecycle phase prior to install is invoked. In such a scenario, Maven will not resolve the test JAR from the output of the reactor build but from the local/remote repository. Apparently, the JAR from the repositories could be outdated or completely missing, causing a build failure (cf. MNG-2045).

A fix is required for all pom's which I will get sorted out ASAP