Github user ifedorenko commented on the pull request:
https://github.com/apache/maven/pull/40#issuecomment-89838717
@Stephan202 what is your usecase for having multiple maven or jvm options
for the same codebase? Is this to support svn (and similar) repositories that
effectively host multiple codebases or something else? .mvn is meant to
configure environment parameters like jvm -Xmx or builder and I can't think of
a reason these would be different for different parts of the same codebase.
As for searching "true" multi-module project root, lack of `pom.xml` is not
a good indicator traversal reached outside project tree. First, we wanted to
support alternative pom formats with this feature. Second, even for projects
that do use `pom.xml`, parent pom does not have to be at the root of the
project codebase.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
