Maven 2.x Compiler Plugin

add separate configuration for test compiler

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.2
  • Fix Version/s: 2.1
  • Labels:
    None
  • Environment:
    all
  • Number of attachments :
    0

Description

use case: (described in http://www.nabble.com/compiler-plugin:-separate-test-compiler-configuration-tt20058021.html )

  • main code is java 1.4 and should remain such for the release
  • unit tests are junit 4 based

to address this use case in cli, modify compiler plugin to accept testSource and testTarget configuration parameters

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MCOMPILER-15 ability to have different test compilation parameters to general compilation parameters

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Oleg Gusakov added a comment - - edited

I modified 2.1 trunk, added

  • testSource
  • testTarget
  • testCompilerArgument
  • testCompilerArguments

So that we can now use:

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>2.1-SNAPSHOT</version>
        <configuration>
          <source>1.4</source>
          <target>1.4</target>
          <testSource>1.5</testSource>
          <testTarget>1.5</testTarget>
          <testCompilerArgument>-bootclasspath ${java.home}\lib\rt.jar</compilerArgument>
          <testCompilerArguments>
            <verbose />
          </testCompilerArguments>
        </configuration>
      </plugin>
    </plugins>
  </build>

Snapshot published in apache snapshots. Changes commited to trunk

Show
Oleg Gusakov added a comment - - edited I modified 2.1 trunk, added testSource testTarget testCompilerArgument testCompilerArguments So that we can now use: <build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.1-SNAPSHOT</version> <configuration> <source>1.4</source> <target>1.4</target> <testSource>1.5</testSource> <testTarget>1.5</testTarget> <testCompilerArgument>-bootclasspath ${java.home}\lib\rt.jar</compilerArgument> <testCompilerArguments> <verbose /> </testCompilerArguments> </configuration> </plugin> </plugins> </build> Snapshot published in apache snapshots. Changes commited to trunk
Hide
Permalink
Oleg Gusakov added a comment -

Changes made and commited. Test project with main code 1.4 and tests 1.5 works well: compiles, adding 1.5 code to main fails it.

Show
Oleg Gusakov added a comment - Changes made and commited. Test project with main code 1.4 and tests 1.5 works well: compiles, adding 1.5 code to main fails it.
Hide
Permalink
Wendy Smoak added a comment -

If you bind an execution of the surefire plugin to the integration-test phase, which parameters get used?

Show
Wendy Smoak added a comment - If you bind an execution of the surefire plugin to the integration-test phase, which parameters get used?
Hide
Permalink
Daniel Le Berre added a comment -

Tried that feature on SAT4J builds: it works perfectly!

Show
Daniel Le Berre added a comment - Tried that feature on SAT4J builds: it works perfectly!
Hide
Permalink
Oleg Gusakov added a comment -

Wendy Smoak - 20/Oct/08 09:24 PM
If you bind an execution of the surefire plugin to the integration-test phase, which parameters get used?

does not matter - they are used by name, so it all is defined by which compiler gets called. So in your case - it depends where your sources are and what you have in <build/> configuration. And which phase is linked in: compile or test-compile

Show
Oleg Gusakov added a comment - Wendy Smoak - 20/Oct/08 09:24 PM If you bind an execution of the surefire plugin to the integration-test phase, which parameters get used? does not matter - they are used by name, so it all is defined by which compiler gets called. So in your case - it depends where your sources are and what you have in <build/> configuration. And which phase is linked in: compile or test-compile

People

  • Assignee:
    Oleg Gusakov
    Reporter:
    Oleg Gusakov
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: