Hello,

The documentation there seems to indicate it's talking about using
properties inside the content:

> To filter properties into any supported documentation format, add a 
> .vmextension to the filename.
>
> For example, the module for the Maven website contains a
> src/site/apt/download.apt.vm<http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/download.apt.vm>file,
>  which uses the expression
> ${currentVersion} to filter in a property set in the 
> POM<http://svn.apache.org/repos/asf/maven/site/trunk/pom.xml>
> .
>
> *Note:* Velocity <http://velocity.apache.org/> is used to apply the
> filtering. Because Velocity uses a dot-notation internally you can *not*use 
> dots in your properties.
>
Is this still applicable to the <distributionManagement><site><url>?  It's
not clear from the documentation that it is.

Changing my property from ${pd.site.url} to ${pd-site-url} hasn't fixed the
problem either, which makes me really think this is MSITE-501 as I
originally thought.

Cheers,
Derek

On Wed, Aug 31, 2011 at 12:05 AM, Olivier Lamy <[email protected]> wrote:

> Hello,
> Properties with dot are not supported.
> See
> http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
> section Filtering.
>
> HTH,
> --
> Olivier Lamy
> Talend : http://talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> 2011/8/31 Derek Lewis <[email protected]>:
> > Hello,
> >
> > I'm having a problem where the URLs (child and parent) in the HTML files
> > generated by the maven-site-plugin:3.0 are not using values defined in a
> > property in the settings.xml. (This sounds like
> > http://jira.codehaus.org/browse/MSITE-501)  The site uploads to the URL
> in
> > ${pd.site.url}, but the HTML includes "${pd.site.url}" in the links
> instead
> > of replacing that with the value from settings.xml.
> >
> > This bug has been around in JIRA for very close to a year.  Is there any
> > possibility of a fix or workaround?
> >
> > Thanks,
> > Derek
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to