Hi Howard, I answered this question for you here: http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL PROTECTED]
I filed: http://jira.codehaus.org/browse/MCOMPILER-15 as a result. You might like to watch/vote for it. It should be something we are able to support properly, but that workaround should work in either parent or individual module in the mean time. On 3/20/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > OK, moving the <plugin> element from the parent POM to the module POM > fixes things; it works as expected. It shouldn't have, I don't think, unless I'm missing something. > > I'm interpreting this as: > > > > "when the goal is compile:compile, use source 1.3, etc." and > > "when the goal is "compile:testCompile, user source 1.5, etc." > > > > However, that's isn't quite what I see when I build: > > An execution is always an additional binding to the lifecycle, so it doubles up when it is already bound through the presets for the packaging. The only way to configure the presets is through the configuration element in the plugin node itself (outside of executions). Unfortunately, you only get one per plugin. I think we should reconsider this use case for 2.1, but also the compiler plugin should have separate test configuration that uses the others as defaults to avoid doubling up, but allows them to be set differently if needed. > > Further, how am I expected to know the correct goal/phase/whatever > > from the documentation? Sometimes Maven feels like an exclusive club > > that leaves a lot of people, people not initmately familiar with the > > source code and implications thereof, out in the cold! I attempted to explain how executions work here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Do you have some suggestions for what areas that needs to improve upon? Thanks, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
