Google Git
Sign in
apache/maven-scripting-plugin/e678c7329a4ebd3a4b2d8fb57af2a86187186de1
commit
e678c7329a4ebd3a4b2d8fb57af2a86187186de1
[log]
author
Sylwester Lachiewicz <slachiewicz@apache.org>
Mon Aug 10 01:02:42 2026 +0200
committer
Sylwester Lachiewicz <slachiewicz@apache.org>
Mon Aug 10 02:55:26 2026 +0200
tree
afb74c0d8ea9858938da30d03ce4093ad575694e
parent
a7c6f5b8dae6fd5b6cf4ca14f1f0cb2deb09b517 [diff]
Remove the empty FAQ page

src/site/fml/faq.fml has never held a single <faq> entry since it was
added in 2021. It renders faq.html as nothing but the heading
"Frequently Asked Questions", and it is the only faq.fml in the Maven
estate that its own site.xml does not put in a menu, so the page is
reachable only from the sentence in index.md.vm that this commit also
drops - archetype boilerplate that invites the reader to consult a FAQ
that does not exist.

This removes faq.html from the published site. That is a URL that will
start returning 404, which is worth stating plainly, but the page has no
content to deep-link to and no menu entry pointing at it.

Verified by building the site before and after: faq.html is the only
page that disappears, the remaining 20 build clean, and no reference to
it is left anywhere in the repository.

Generated-by: Claude Opus 5 (1M context)
2 files changed
tree: afb74c0d8ea9858938da30d03ce4093ad575694e
  1. .github/
  2. src/
  3. .asf.yaml
  4. .gitignore
  5. Jenkinsfile
  6. LICENSE
  7. pom.xml
  8. README.md
README.md

Contributing to Apache Maven Scripting Plugin

Apache License, Version 2.0, January 2004 Maven Central Reproducible Builds Jenkins Status Jenkins tests

You have found a bug, or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

Getting Started

  • Make sure you have a GitHub account.
  • If you‘re planning to implement a new feature, it makes sense to discuss your changes on the dev list first. This way you can make sure you’re not wasting your time on something that isn‘t considered to be in Apache Maven’s scope.
  • Submit a ticket for your issue, assuming one does not already exist.
    • Clearly describe the issue, including steps to reproduce when it is a bug.
    • Make sure you fill in the earliest version that you know has the issue.
  • Fork the repository on GitHub.

Making and Submitting Changes

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:

  • Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
  • Make commits of logical units.
  • Respect the original code style: by using the same codestyle, patches should only highlight the actual difference, not being disturbed by any formatting issues:
    • Only use spaces for indentation.
    • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted, create a separate PR for this change.
    • Check for unnecessary whitespace with git diff --check before committing.
  • Make sure you have added the necessary tests (JUnit/IT) for your changes.
  • Run all the tests with mvn -Prun-its verify to assure nothing else was accidentally broken (you may need to run mvn install beforehand).
  • Submit a pull request to the repository in the Apache organization.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement.

Additional Resources