[ http://jira.codehaus.org/browse/MNG-359?page=comments#action_39737 ]
Rod Coffin commented on MNG-359:
--------------------------------
If the <modules> allowed "../" in order refer to modules at the same level as
the parent project then working with a maven project within Eclipse would be
much simpler. I have used a similar technique in M1 and is has served me well
in several applications. I agree that hierarchical support for projects within
Eclipse would be preferable but in the meantime this technique would be quite
helpful.
As an example, I would like to define modules as follows:
<modules>
<module>../m2-test-app</module>
<module>../m2-test-web</module>
<module>../m2-test-plugin</module>
</modules>
What is the reasoning behind disallowing "../"? I'm sure that you had good
reasons for adding this limitation.
> support project inheritence with flat project layout
> ----------------------------------------------------
>
> Key: MNG-359
> URL: http://jira.codehaus.org/browse/MNG-359
> Project: Maven 2
> Type: Wish
> Components: maven-core
> Versions: 2.0-alpha-1
> Reporter: Ryan Sonnek
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> the project inheritence does not currently support projects that are laid out
> with a "flat" directory structure.
> ex:
> --/my-project-root/
> ----pom.xml (base pom)
> --/my-subproject-one/
> ----pom.xml (child pom)
> original thread on mailing list:
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111442037703037&w=2
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
