On Wed, Jun 11, 2008 at 6:17 PM, John Casey <[EMAIL PROTECTED]> wrote: > Hi everyone, > > As I'm sure you've noticed from the discussion on this list and my commit > logs, I've been working to solve a problem between concrete interpolation of > the POM at project-construction time and the need to update plugin > configurations to reflect changing state in the project instance as the > build progresses. The full proposal is here: > > http://docs.codehaus.org/display/MAVEN/Dynamic+POM+Build+Sections > > And the relevant JIRAs are mainly: > > - MNG-3530 > - MNG-3355
Hei, I've read the above proposal, (understood part of it), and wonder how this relates to http://jira.codehaus.org/browse/MNG-3595 (marked for 2.1) in particular this sentence "For instance, dynamically injecting new dependencies is absolutely not a good thing, since it affects Maven's ability to understand what external libraries a project depends on - in that scenario, the only way to get the full complement of project dependencies is to first run the plugin, then check the project dependency list." Many plugins affect dependencies. Most do it just for their own execution (e.g. easyb), others do it for the whole forked lifecycle (e.g. clover). The intent is very different. How does the above quote affect the clover use case ? Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
