[jira] Commented: (MNG-208) flag project that was the root of the execution

2005-09-21 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/MNG-208?page=comments#action_46872 ] Brett Porter commented on MNG-208: -- doesn't make sense with -r, I only intended with "modules". I think project.isExecutionRoot() would be sufficient. > flag project that was the root o

[jira] Commented: (MNG-208) flag project that was the root of the execution

2005-09-21 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-208?page=comments#action_46863 ] John Casey commented on MNG-208: you're assuming the list of projects comes from If it comes from a '-r' invocation, then [0] and [1] may have nothing to do with one another, and it's c

[jira] Commented: (MNG-208) flag project that was the root of the execution

2005-09-21 Thread Kenney Westerhof (JIRA)
[ http://jira.codehaus.org/browse/MNG-208?page=comments#action_46856 ] Kenney Westerhof commented on MNG-208: -- use ${reactorProjects}.get(0) -> that's the root of the execution > flag project that was the root of the execution > --

[jira] Commented: (MNG-208) flag project that was the root of the execution

2005-09-21 Thread John Casey (JIRA)
[ http://jira.codehaus.org/browse/MNG-208?page=comments#action_46850 ] John Casey commented on MNG-208: This affects things like the source for SCM information in the release plugin as well. Trouble is, what do you do when you have multiple roots, as in a '