gnodet merged PR #464:
URL: https://github.com/apache/maven-site/pull/464
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apach
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 he
slawekjaranowski commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1801539623
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
slawekjaranowski commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1801362863
Should we have license headers in files?
Does missing license will break site builds?
--
This is an automated message from the Apache Git Service.
To respond to the message
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1801326628
Note that adding `-alpha-8` in the file names won't exactly fix the existing
broken links.
But at least, it provides an easy fix...
--
This is an automated message from the Apache Gi
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796960251
I'm slightly worried about publishing unstable XSDs. This may cause problem
is the next 4.0.0 alpha/beta/milestone release does actually change it. Users
may have the schema cached by t
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796832812
The `plugin-[version].xsd` schemas are currently not published, so don't
bother with those.
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1796639967
The two missing XSDs should now be available by building maven master branch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
ditbace commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1792671361
I don't know that is what I'm trying to do.
On Fri, Nov 3, 2023 at 8:20 AM Guillaume Nodet ***@***.***>
wrote:
> Running mvn verify on latest maven master only creates a
ditbace commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1792669974
Thanks
On Fri, Nov 3, 2023 at 8:20 AM Guillaume Nodet ***@***.***>
wrote:
> Running mvn verify on latest maven master only creates a
> settings-1.3.0.xsd. How can I cre
gnodet commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1792339301
> Running `mvn verify` on latest maven master only creates a
`settings-1.3.0.xsd`. How can I create those 3 files ?
Part of the solution is https://github.com/apache/maven/pull/1297
froque commented on PR #464:
URL: https://github.com/apache/maven-site/pull/464#issuecomment-1791714603
Running `mvn verify` on latest maven master only creates a
`settings-1.3.0.xsd`. How can I create those 3 files ?
--
This is an automated message from the Apache Git Service.
To respo
froque opened a new pull request, #464:
URL: https://github.com/apache/maven-site/pull/464
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-ma
13 matches
Mail list logo
