[ https://issues.apache.org/jira/browse/MNGSITE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645647#comment-17645647 ]
ASF GitHub Bot commented on MNGSITE-503: ---------------------------------------- bmarwell commented on PR #354: URL: https://github.com/apache/maven-site/pull/354#issuecomment-1345305885 > Two issues: > * I think that using this plugin is redundant when we have this: https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#special-variables > * Pushing the expires every time like not a having an expires at all. I'd rather make it a *fixed date* and 1 month before evaluate again. It is like push the appointment with the dentist every time. Huh. It's manual work and highly likely it's forgotten. It's very likely that * We push this project at least once or twice a year * The project is being maintained (or at least reachable) about 12 months after pushing out the last release. -1 for a fixed date. * It doesn't add any value * Can easily be forgotten * Needs extra pushes/releases. The special variable doesn't work with offsets. And I fail to see how this would help. The expiry format MUST BE an ISO 8601 timestamp. > add .well-known/security.txt > ---------------------------- > > Key: MNGSITE-503 > URL: https://issues.apache.org/jira/browse/MNGSITE-503 > Project: Maven Project Web Site > Issue Type: Improvement > Reporter: Benjamin Marwell > Assignee: Benjamin Marwell > Priority: Major > Labels: security > > As per consensus on the mailing list (+1 from [~rmannibucau] and me), we > should add a file `.well-known/security.txt`. > I will prepare a PR. > References: > * [.well-known/security.txt at maven.apache.org > (mail-archive.com)|https://www.mail-archive.com/dev@maven.apache.org/msg128366.html] > * [.well-known/security.txt at maven.apache.org-Apache Mail > Archives|https://lists.apache.org/thread/tvfg1lx9nd72c9t4t4s3zlx6l0tpnmwy] -- This message was sent by Atlassian Jira (v8.20.10#820010)