Hi Keheliya,
On Mon, Jan 9, 2012 at 3:31 PM, Keheliya Gallaba <[email protected]> wrote:
> Hi,
>
> Although there are few variables (like product.name, product.version,
> fixed.issue.filter) referred from filter.properties file when generating
> documentation, they are not properly replaced in the built
> ${server}-${version}-docs.zip archive. (ie: The created pages have content
> like 'Welcome to @product.name@ [email protected]@!' ) I checked with
> BPS, GReg & BRS. So I assume this is a problem with Maven 3.x & site
> plugin[1], or am I missing any procedure to follow when building
> documentation?
>
AFAIR, filter.properties file is used by maven assembly plugin but not by
maven site plugin. During the process of assembling the binary, docs and
source distributions, assembly plugin uses this file to replace certain set
of variables.
There is an issue with maven assembly plugin, where it does not recognize
new maven 3 variables (e.g: ${project.version}). Since we moved our
variables to these new variables, this could be a regression issue.
Will check it and update.
Thanks and Regards,
Harshana
>
> [1]
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-SiteandReporting
>
> Regards,
> Keheliya
>
> --
> Keheliya Gallaba
> Software Engineer
> WSO2 Inc.
>
> E-mail: keheliya AT wso2.com
> M: +94 71 551 8881
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
--
Harshana Martin
Software Engineer
WSO2 Inc.
Web:http://wso2.com
http://wso2.org
Mobile: +94 716062650
Blog: http://harshana05.blogspot.com
Profile: https://www.google.com/profiles/harshana05
Twitter: http://twitter.com/harshana05
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
