[
https://jira.codehaus.org/browse/MSITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297313#comment-297313
]
Todd Merrill commented on MSITE-639:
------------------------------------
I had this problem as well. Our site.xml is attached to parent pom also. The
site.xml downloaded fine on our Jenkins server, but did not work on my new
local workstation. I noticed that in the repository cache on the working
server machine there was in fact a 'module-1.0-SNAPSHOT-site_en.xml' file of
size 0 that was being created. Why, I don't know. In our nexus repo there is
no locale-specific descriptor.
I found a workaround by removing all the repositories from my settings.xml that
were external to my firewall, allowing only our local nexus repositories to be
referenced. I moved the external repos to a profile that I must remember to
turn off when calling the site target.
> sub-project tries to fetch a site_en.xml even though no locales are configured
> ------------------------------------------------------------------------------
>
> Key: MSITE-639
> URL: https://jira.codehaus.org/browse/MSITE-639
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Affects Versions: 3.0-beta-3
> Environment: Windows 7 64bit, Sun JDK 1.6.0_27
> Reporter: Martin Goldhahn
> Attachments: parent-project.zip, sub-project.zip
>
>
> I have a parent project that has a site descriptor and a pom project that has
> the parent project as parent. Neither of them defines the locales parameter
> of the site plugin.
> When I try to build the sub-project, I get an error that Maven cannot find
> the site_en.xml descriptor of the parent project. Why doesn't it just use the
> site.xml?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
