I think the use case is valid - I have seen it a number of times
before. At runtime they are already separate (you can run surefire
with whatever JVM you want, regardless of what you target for
compilation).
The other parameter that needs to be changed is the ability to fork
your own javac, which I think is related to what you mentioned.
However, instead of overloading all the parameters - I think this is
the time to push toolchains forward. So a user could choose a tests
toolchain that would pick up the values from there, and if it isn't
specified it falls back to the values from the main compiler plugin
that it is using now.
Does that make sense?
Cheers,
Brett
On 20/10/2008, at 3:52 AM, Oleg Gusakov wrote:
One of the users requested a separate source/target configuration
for test compiler for the reason of running junit4 tests and yet
being java 1.4 in the main classes.
It's a trivial change in the compiler plugin, but I decided to ask
here before changing it.
The proposed change - add two configuration parameters:
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<testSource>1.5</testSource>
<testTarget>1.5</testTarget>
</configuration>
</plugin>
Please let me know if it breaks anything. Please also indicate if
you need more separation (like memory, etc)?
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
