[ http://jira.codehaus.org/browse/MNG-2363?page=comments#action_83059 ] Franz Garsombke commented on MNG-2363: --------------------------------------
Same problem. I have a predefined ant plugin (in pluginmanagement) at the aggregator level. I do not want all of the sub modules to inherit this ant plugin since some of the sub modules need to define their own executions for the ant plugin. Creating profiles at the aggregator level and then inheriting a profile seemed like the right approach. The <file> activation does not allow me to work at the submodule level. Thanks, Franz > <profile><activation><file><exists/> does not work in a multi-project build > --------------------------------------------------------------------------- > > Key: MNG-2363 > URL: http://jira.codehaus.org/browse/MNG-2363 > Project: Maven 2 > Issue Type: Bug > Components: Profiles > Reporter: David Boden > Priority: Critical > Fix For: 2.1 > > Attachments: problemactivation.zip, screenshot-1.jpg > > > I would expect each subproject to have the profile turned on or off depending > on whether ${basedir}/file-to-check-for exists. > Instead, during a multi-project build the profile is either on or off > depending on whether the file exists relative to the *aggregator pom*. The > decision is made once. > Variable substitution doesn't work, so I can't explicitly use > <exists>${basedir}/file-to-check-for</exists> or any variation on this theme > to workaround the bug. > Some background to my particular problem. I have 10 modules to build. Some of > them are GUI modules and contain a file called plugin.xml in the subproject > directory. I want to package these up specially and sign them, ready for > deployment to webstart. The other modules are shared and server code and I > don't want these packaged in the same way. So, I've got a dependency in my > *parent* pom file which activates a profile called "guibundle" if a > plugin.xml file exists in the subproject directory. -- 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
