On 1/30/06, jerome lacoste <[EMAIL PROTECTED]> wrote: > On 1/30/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > I'm plenty confused myself. I'd have liked to hear from more people, but > > I think at this point I'll take the proposal to the Maven lists to see > > if I can kick the discussion off a bit more. > > I just have a question, althought I am probably rather late to the > debate: this plugin seems to be rather helpful when you do not > completely follow the maven way of setting up your build. > > Promoting it to apache makes it sound like other ways are more > accepted than before. Although I am all in favor of giving people > tools to solve their issues, I am just wondering if something hasn't > changed there. It's maybe just a feeling... > > Finally, if adding a source or a test-source or attach an artifact > becomes an accepted concept, I tend to wonder why it doesn't become > part of the pom itself. I find strange that one needs to add 20 lines > of XML when the real content is just one line.
I am kind of reconsidering this issue. I am searching for a solution to compile generated-sources. I need to add these sources to the compiler but the compileSourceRoots is read-only. [BTW, this should be visually indicated on the plugin documentation. Or removed from the plugin documentation.] The apparently only current solution is to use the build helper plugin. I've seen people also use the <sourceRoot> configuration with the ant run plugin, but I cannot use that in my case. Automatically generating sources is becoming more and more common. We need an official way to add these generated sources roots to the compiler. If the compiler plugin configuration is not made writable, then the build helper plugin needs to be more official. I'd rather the compiler plugin to become more flexible. See also http://jira.codehaus.org/browse/MCOMPILER-13 WDYT? J
