On 2010-07-01 18:11, Benjamin Wootton wrote:
> Ah indeed it was the project/URL. I didn't realise that was actually used as
> part of the site generation. Removing it from the default value fixes up the
> links.
>
> Out of interest, is there any document that describes how the URL works in
> re
Ah indeed it was the project/URL. I didn't realise that was actually used as
part of the site generation. Removing it from the default value fixes up the
links.
Out of interest, is there any document that describes how the URL works in
relation to sites. The pom reference describes it as "a nic
well one assumes that you have correctly defined the /project/url parameter.
there are a number of multi-module releases at apache and codehaus all of
which deploy their site via
mvn site-deploy
or via mvn release:perform
and I have not seen issues with the links in the deployed sites as long a
Hi Stephen
I am talking about the deployed site - though I'm actually deploying to a
file:// URL on the same server. Would this make a difference over an scp?
Thanks
Ben
On 1 Jul 2010, at 16:05, Stephen Connolly
wrote:
> On 1 July 2010 15:02, wrote:
>
>> I am experiencing the common proble
On 1 July 2010 15:02, wrote:
> I am experiencing the common problem of links broken in multi module
> sites with parent poms.
>
> I understand that* mvn site* builds individual module sites but doesn't
> link them, and the* mvn site:deploy* should repair the links. The latter
> however doesn't
I am experiencing the common problem of links broken in multi module
sites with parent poms.
I understand that mvn site builds individual module sites but doesn't
link them, and the mvn site:deploy should repair the links. The latter
however doesn't happen.
>From here http://maven.apache.org/
