[ http://jira.codehaus.org/browse/MNG-2363?page=comments#action_83175 ] Ben Tatham commented on MNG-2363: ---------------------------------
I have the same issue, but not using modules. This is the critical point: "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." I want a parent pom to define some plugin executions (like xdoclet, jspc, etc), so I can reuse those plugin configurations in all my other projects that need these tools. Of course, that parent project doesn't have servlets/tags/jsps to compile, so I have to use a profile to define them so that I can actually install the pom project itself. But I don't want to have to use a command line property to turn it on...my tests rely on those plugins running. > <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
