[ http://jira.codehaus.org/browse/MNG-2302?page=all ]
John Casey closed MNG-2302.
---------------------------
Assignee: John Casey
Resolution: Fixed
The DefaultMavenProjectBuilder.assembleLineage(..) method was setting the
descriptor File instance for the parent MavenProject even when that
MavenProject instance had been resolved from the repository. In these cases,
the descriptor location is was using was incorrect.
NOTE: I have not captured this in a unit test, or an integration test, as it
seems that the current system is incapable of running this test. The method
itself does too many things to unit test effectively, and the integration test
system currently doesn't support multiple Maven operations per test (required
to install the top and middle POMs from the attached test dir into the
repository).
> SCM path calculations don't work when parent and grandparent are in sibling
> directories
> ---------------------------------------------------------------------------------------
>
> Key: MNG-2302
> URL: http://jira.codehaus.org/browse/MNG-2302
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritence and Interpolation
> Affects Versions: 2.0.4
> Reporter: John Casey
> Assigned To: John Casey
> Fix For: 2.0.5
>
> Attachments: MNG-2302-test.zip
>
>
> I have the following directory structure:
> -top
> |
> +-grandparent
> |
> +-parent
> |
> +-child
> where modules are specified in grandparent and parent, respectively, as:
> <module>../parent</module>
> and
> <module>../child</module>
> When I put these into Continuum, and it tries to use the SCM info provided in
> the grandparent, it winds up thinking the child directory is a subdirectory
> of the parent directory.
--
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
