defining a plugin within <plugins> affects configuration of the same plugin defined within <pluginManagement> -------------------------------------------------------------------------------------------------------------
Key: MNG-2482 URL: http://jira.codehaus.org/browse/MNG-2482 Project: Maven 2 Issue Type: Bug Components: Ant tasks, Plugin API Affects Versions: 2.0.4 Environment: windows xp sp2 Reporter: Martin Ploeckinger Attachments: build_part_of_pom.xml a problem occurs using the antrun-plugin in maven for some different tasks. first i defined the antrun-plugin within <pluginManagement> for execution tasks only in the child poms, even with 2 different execution tags and phases and it worked perfect. and now i wanted to add an ant job which should be executed only once at top level and therefore i had to "redefine" the antrun-plugin outside of <pluginManagement> with an <inherited>false</inherited> option. but however this does not work, the ant tasks within <pluginManagement> are now executed at top level too.... it is funny that both definitions work, the top-level job and the child jobs, but not togehter in one pom...i always have to leave the other ones aside i used the attached build section in my top level pom.xml and the error i get is that "rmic" is also executed at top level pom where no source is available understandably -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira