maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <>
Subject Re: [m2] Problem having the parent on the same level as the children using the site-plugin
Date Wed, 11 Jan 2006 21:46:13 GMT
This is exciting stuff. After setting together a minimal test case. It 
worked  *without* <relativePath/>. So i decided so go back through my 
session to see what had happened. Since I am using snapshots there were 
some updates done at the beginning of today's session:
Previous version was:
Previous version was:

So I guess that whatever problem I had earlier was solved by either of 
these two updates. Looking at the commits made to maven-site-plugin I 
found this one that looks like it could be the one:

Log: [MSITE-62] improve relative path discovery and apply to whole 

Sorry for the noise.

Dennis Lundberg

Brett Porter wrote:
> I agree, and I don't underestand why it fails in the parent (I
> understand why it would impact the children and it should be used in any
> case).
> Can you drop that test case into JIRA?
> Dennis Lundberg wrote:
>> I did not have <relativePath/> set at all. If I set that in module-1 a
>> link from the parent site to module-1 shows up in the menu. So that
>> solved my problem, thanks.
>> However I'm a bit confused as to why this is needed. The parent has all
>> the knowledge it needs about the children from the <modules/> section in
>> the parent's pom. The reason for putting a <relativePath/> in a child
>> would so that the child would know about its parent, like for creating a
>> link from the child to the parent. IMHO the rendering of the parent site
>> should not need <relativePath/> in its children to be able to create
>> links to the child sites.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message