Issue Details (XML | Word | Printable)

Key: MPTEST-67
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Lukas Theussl
Reporter: Shinobu Kawai
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1.x Test Plugin

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

Created: 24/Jul/06 01:58 PM   Updated: 28/Jul/06 07:57 AM
Component/s: None
Affects Version/s: 1.8
Fix Version/s: 1.8.1

Time Tracking:
Issue & Sub-Tasks
Issue Only
Not Specified

File Attachments: 1. Text File MPTEST-67 (0.7 kB)


Sub-Tasks  All   Open   

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

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Shinobu Kawai added a comment - 24/Jul/06 01:59 PM
Patch to use maven.compile.target

Lukas Theussl added a comment - 24/Jul/06 02:57 PM
Applied. Thanks!

nicolas de loof added a comment - 28/Jul/06 03:24 AM
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.

Shinobu Kawai added a comment - 28/Jul/06 07:57 AM
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.