here is what I use:

<siteUrl>*file:///*/var/www/html/site/${pom.version}</siteUrl>

there are 3 forward slashes before my root /var directory

---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Twitter: http://twitter.com/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---



On Sun, Feb 15, 2009 at 7:17 AM, Dennis Lundberg <denn...@apache.org> wrote:

> Randall Fidler wrote:
> > Hello,
> >
> >
> >
> >             I have a multi-module project that seemed to deploy fine
> > with SCP but not with FILE.  Inside settings.xml I've got a var which
> > points to the local directory where the site files should be deployed to
> > and things work fine for the parent but not the child.
> >
> >
> >
> > Parent (1.0_SNAPSHOT)   (has site in dist mgmt set to
> > file://${site.dir}/${project.artifactId}/${project.version}
>
> Does ${site.dir} start with a / ?
>
> A file URL normally has three /-characters, like this:
>
> file:///directory/path
>
> This is because the host is omitted from the URL.
>
> >
> >  |
> >
> >  |
> >
> >  ----- Child (1.0_SNAPSHOT)
> >
> >
> >
> > What happens is I end up with both sites in the same directory instead
> > of the child being nested under the parent, which means that the link in
> > the modules section of the parent site has the wrong link for the child
> > site.  It thinks the child is at {parent site directory}/Child  but as I
> > said, the parent and child are at the same level.
> >
> >
> >
> > Suggestions?  As I said, the sites are structured properly deployed
> > using SCP but with file it doesn't com out correctly.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Randall
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to