Maven 1.x Test Plugin

maven.compile.target is not considered in test:compile

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.8
  • Fix Version/s: 1.8.1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

Since maven.compile.target is not used to compile, forking with a lower version JVM does not work.

Activity

Hide
Shinobu Kawai added a comment -

Patch to use maven.compile.target

Show
Shinobu Kawai added a comment - Patch to use maven.compile.target
Hide
Lukas Theussl added a comment -

Applied. Thanks!

Show
Lukas Theussl added a comment - Applied. Thanks!
Hide
nicolas de loof added a comment -

Does this mean I cannot write my unit tests using Java5 extensions to test Java 1.3 classes (required by some tools like esaymock 2, Watij, ...) ?
Please consider an alternative way, for example a maven.test.compile.target property. IMHO test compilation has no reason to be identical to application classes compilation.

Show
nicolas de loof added a comment - Does this mean I cannot write my unit tests using Java5 extensions to test Java 1.3 classes (required by some tools like esaymock 2, Watij, ...) ? Please consider an alternative way, for example a maven.test.compile.target property. IMHO test compilation has no reason to be identical to application classes compilation.
Hide
Shinobu Kawai added a comment -

Good point.

You might want to create a new issue for that. The test plugin is recycling many of the java plugin properties (including maven.compile.source, too). It might be good to have test properties defaulting to the java properties.

Show
Shinobu Kawai added a comment - Good point. You might want to create a new issue for that. The test plugin is recycling many of the java plugin properties (including maven.compile.source, too). It might be good to have test properties defaulting to the java properties.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: