Have commented on there. I think outputDirectory should be writeable, but I think that the compileSourceRoots should not. Instead, the build-help-maven-plugin should be used to add source roots. The limitation will be that you can't have multiple target directories without a profile. IF this is not sufficient we need to look again at the use case.
My concern is that anything that relies on the project.getCompileSourceRoots will not work for anything where the plugin configuration is altered directly. It's the same objection I have to the changes in MRESOURCES-8. - Brett Allison, Bob wrote: > Reported in JIRA as http://jira.codehaus.org/browse/MCOMPILER-13 > > -----Original Message----- > From: Pablo [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 12, 2006 04:42 > To: Maven Developers List > Subject: feature request for maven-compiler-plugin > > > Hello there > > If it's not a problem I'd like someone to remove @readonly attributes > for fields: > private List compileSourceRoots > private File outputDirectory > in class TestCompilerMojo in maven-compiler-plugin. > > I'd like to use this Mojo to compile integration-tests and this > attribute prevents me from using this plugin in custom applications. > > Cheers > Pablo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
