You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oleg Gusakov (JIRA)" <ji...@codehaus.org> on 2008/10/20 20:05:19 UTC
[jira] Created: (MCOMPILER-83) add separate configuration for test
compiler
add separate configuration for test compiler
--------------------------------------------
Key: MCOMPILER-83
URL: http://jira.codehaus.org/browse/MCOMPILER-83
Project: Maven 2.x Compiler Plugin
Issue Type: New Feature
Affects Versions: 2.1
Environment: all
Reporter: Oleg Gusakov
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-83) add separate configuration for
test compiler
Posted by "Daniel Le Berre (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151438#action_151438 ]
Daniel Le Berre commented on MCOMPILER-83:
------------------------------------------
Tried that feature on SAT4J builds: it works perfectly!
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCOMPILER-83) add separate
configuration for test compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151385#action_151385 ]
olle edited comment on MCOMPILER-83 at 10/20/08 1:42 PM:
-----------------------------------------------------------------
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Snapshot published in apache snapshots. Changes commited to trunk
was (Author: olle):
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Snapshot published in apache snapshots.
Trying to commit - problems with authorization, working on that
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCOMPILER-83) add separate configuration for test
compiler
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MCOMPILER-83:
---------------------------------------
Affects Version/s: (was: 2.1)
2.0.2
Fix Version/s: 2.1
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.0.2
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Fix For: 2.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCOMPILER-83) add separate
configuration for test compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151385#action_151385 ]
olle edited comment on MCOMPILER-83 at 11/7/08 3:43 PM:
----------------------------------------------------------------
I modified 2.1 trunk, added
* *testSource*
* *testTarget*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Snapshot published in apache snapshots. Changes commited to trunk
was (Author: olle):
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Snapshot published in apache snapshots. Changes commited to trunk
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCOMPILER-83) add separate configuration for test
compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Gusakov closed MCOMPILER-83.
---------------------------------
Resolution: Fixed
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.
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-83) add separate configuration for
test compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151604#action_151604 ]
Oleg Gusakov commented on MCOMPILER-83:
---------------------------------------
{quote}
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?
{quote}
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 :)
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCOMPILER-83) add separate
configuration for test compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151385#action_151385 ]
olle edited comment on MCOMPILER-83 at 10/20/08 1:15 PM:
-----------------------------------------------------------------
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Snapshot published in apache snapshots.
Trying to commit - problems with authorization, working on that
was (Author: olle):
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Changes commited to trunk, snapshot published in apache snapshots
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-83) add separate configuration for
test compiler
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151435#action_151435 ]
Wendy Smoak commented on MCOMPILER-83:
--------------------------------------
If you bind an execution of the surefire plugin to the integration-test phase, which parameters get used?
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-83) add separate configuration for
test compiler
Posted by "Oleg Gusakov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151385#action_151385 ]
Oleg Gusakov commented on MCOMPILER-83:
---------------------------------------
I modified 2.1 trunk, added
* *testSource*
* *testSource*
* *testCompilerArgument*
* *testCompilerArguments*
So that we can now use:
{code}
<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>
{code}
Changes commited to trunk, snapshot published in apache snapshots
> add separate configuration for test compiler
> --------------------------------------------
>
> Key: MCOMPILER-83
> URL: http://jira.codehaus.org/browse/MCOMPILER-83
> Project: Maven 2.x Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: all
> Reporter: Oleg Gusakov
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira