I wrote a jira and submitted a patch for this very problem: http://jira.codehaus.org/browse/MNG-1929 Please vote and or comment on it if you think it is important, as it hasn't been applied yet. Basically showing readonly parameters is more confusing than helpful, therefore they probably shouldn't be shown at all yet.
-----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Monday, April 10, 2006 12:28 PM To: Maven Users List Subject: Re: Trying to understand maven readonly parameters readonly parameters are meant for configuration from some other source, often another element in the POM. In this specific case, direct configuration of the maven-compiler-plugin could pretty easily lead to problems with other plugins that need to handle the project sources...that's because the list of compilable directories would be different for the compile action than for some other plugin. The build-helper-maven-plugin simply appends new source directories to the shared compileSourceRoots project field, much as a code-generating plugin might. -john On 4/10/06, Raymond Domingo <[EMAIL PROTECTED]> wrote: > > Hello, > > Can anyone explain why maven-compiler-plugin setting > compileSourceRoots is readonly ? > > Isn't it a pain in the as you have to use the > build-helper-maven-plugin to work around this problem or am I missing something ? > > raymond > > --------------------------------------------------------------------- > 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]
