[jira] Commented: (MNG-4120) Profile activation should be per module
[ http://jira.codehaus.org/browse/MNG-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171845#action_171845 ] Benjamin Bentmann commented on MNG-4120: Looks like a dup of MNG-2363, isn't it? File-based profile activation resolves relative paths against the current working directory, not the module base directory. > Profile activation should be per module > --- > > Key: MNG-4120 > URL: http://jira.codehaus.org/browse/MNG-4120 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, POM >Affects Versions: 2.0.9 >Reporter: Karsten Tinnefeld > > In a multi-module-project, one might wish to run certain targets dependent on > the existance of some file or directory. > In a single-module-project, I'd say > do-if-file-exists > some/special/path > > This however does not work on a per-module base in a multi-module project, > but the profile is (de)activated depending on the situation on the run pom > only, and this is not even documented. > In my opinion, profile activation should be on a per-module basis. -- 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
[jira] Commented: (MNG-4120) Profile activation should be per module
[ http://jira.codehaus.org/browse/MNG-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171685#action_171685 ] Karsten Tinnefeld commented on MNG-4120: Second try. > Profile activation should be per module > --- > > Key: MNG-4120 > URL: http://jira.codehaus.org/browse/MNG-4120 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, POM >Affects Versions: 2.0.9 >Reporter: Karsten Tinnefeld > > In a multi-module-project, one might wish to run certain targets dependent on > the existance of some file or directory. > In a single-module-project, I'd say > do-if-file-exists > some/special/path > > This however does not work on a per-module base in a multi-module project, > but the profile is (de)activated depending on the situation on the run pom > only, and this is not even documented. > In my opinion, profile activation should be on a per-module basis. -- 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
[jira] Commented: (MNG-4120) Profile activation should be per module
[ http://jira.codehaus.org/browse/MNG-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171631#action_171631 ] Brett Porter commented on MNG-4120: --- I'm not sure I understand - are you trying to activate based on an inherited profile? Can you attach a sample project that illustrates? > Profile activation should be per module > --- > > Key: MNG-4120 > URL: http://jira.codehaus.org/browse/MNG-4120 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, POM >Affects Versions: 2.0.9 >Reporter: Karsten Tinnefeld > > In a multi-module-project, one might wish to run certain targets dependent on > the existance of some file or directory. > In a single-module-project, I'd say > do-if-file-exists > some/special/path > > This however does not work on a per-module base in a multi-module project, > but the profile is (de)activated depending on the situation on the run pom > only, and this is not even documented. > In my opinion, profile activation should be on a per-module basis. -- 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
