Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0-beta-5
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
The patches contributed by myself and Vincent are faulty due to the assumption that project.getParent() returns an interpolated project which is not the case.
Additionally the only way I know to get 'cooked' (interpolated) projects is via reactor environment but this breaks the perfectly valid requirement of being able to generate a site and its links to parent and child projects on its own (i.e. not in a reactor build)
There's also a bug in patches that causes invalid paths to be generated in site:stage mojo under win32 where a ':' is left hanging in the middle fo the newly generated project URLs. i.e. D:\Foo ends up in the middle of patch.
I have a few made comments on confluence regarding the wider problems re addressing related projects and the need for a cooked project model when not in a reactor environment:
http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence
Issue Links
- relates to
-
MSITE-54
In parent site, automatically create link to modules sites and vice-versa
-