[
https://issues.apache.org/jira/browse/MNGSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784080#comment-17784080
]
ASF GitHub Bot commented on MNGSITE-527:
----------------------------------------
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1802027696
> Should we have license headers in files? Does missing license will break
site builds?
Those files are generated. Not sure if the old ones have been manually
edited to add the header before publication or if the generation somehow
changed in modello...
> By the way ... maybe we should create html page at
https://maven.apache.org/xsd/ with description for which component and version
specific xsd should be used
>
> another idea - add to xsd comments component and version
>
> of course all for next PRs
I'd like to avoid maintaining the whole list of schemas manually. I think
using a `.htaccess` could be leveraged to provide a `readme.html` to display on
top of the listing. See [apache
mod_autoindex](https://httpd.apache.org/docs/2.0/mod/mod_autoindex.html#indexoptions)
> broken link to settings-1.3.0.xsd
> ---------------------------------
>
> Key: MNGSITE-527
> URL: https://issues.apache.org/jira/browse/MNGSITE-527
> Project: Maven Project Web Site
> Issue Type: Bug
> Reporter: Filipe Roque
> Priority: Major
>
> The url of the XSD mentioned in the settings.xml settings tag is broken in
> Maven 4
> {code:java}
> <settings xmlns="http://maven.apache.org/SETTINGS/1.3.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.3.0
> https://maven.apache.org/xsd/settings-1.3.0.xsd";> {code}
> Both the settings.xml found at apache-maven-4.0.0-alpha-8/conf/settings.xml
> and at https://maven.apache.org/ref/4-LATEST/maven-settings/settings.html
> reference a broken url.
> There are older Versions at [http://maven.apache.org/xsd/].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
