There's already a jira for this since I originally suggested it a long time ago. IIRC John and I looked at it and found some problems with it but I'd have to dig up the jira to remember.
-----Original Message----- From: Oleg Gusakov [mailto:[EMAIL PROTECTED] Sent: Sunday, October 19, 2008 4:51 PM To: Maven Developers List Subject: Re: compiler plugin: separate test compiler configuration This could be arranged, but Eugene has a very valid question - Eclipse sets all those on the project level and might misbehave as soon as somebody starts debugging such a project. Milos, you can say that's eclipse's problem. But is't a majority of users, whether it's good or bad, we need to respect that use case. So the question remains - should we modify the compiler plugin to allow separate configurations for test compiler? Or if such a need comes - it's an indication that it's time to move tests into a separate project? Anyone ? � wrote: > Yes Milos, it was my question. > > In fact, it's nice to can specify specific configuration for both source and > test. > > For instance, we want to be able to define the source and target level but > also some other configuration such as compilerArgument and so on > > R�my > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
