Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168311704
I second @khmarbaise answer, I do neither understand the problem you have.
Looking at the demo project you have provided, I looks completely screwed up.
Modules are supp
Github user khmarbaise commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168306169
First i see your setup as wrong..cause you use modules multiple times
within the reactor (Apart from using `..` which is
simply not needed`). What i don't understand is
Github user nhojpatrick commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168305170
I've worked on 5+ projects where they ranged from 75-150 maven projects.
Allow this configuration would have simplified and reduce build times. The
usual work around I
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/75#issuecomment-168279059
@jvanzyl Should be allow this or rather fail and force people to fix their
setup?
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user nhojpatrick opened a pull request:
https://github.com/apache/maven/pull/75
Patch for MNG-5956
Issue raised https://issues.apache.org/jira/browse/MNG-5956
If you use modules, and that results in the same project/pom being included
multiple times then an