'changelog_1x.md': 'changelogs/changelog_1x.md'
        # Redirect all contributing pages to contribute/*
        'contributing.md': 'contribute/contributing.md'
        'code_of_conduct.md': 'contribute/code_of_conduct.md'
        'concurrency.md': 'contribute/concurrency.md'
        'debug_logging.md': 'contribute/debug_logging.md'

nav:
  - 'Overview':
    - 'Overview': index.md

# Copy in special files that GitHub wants in the project root.
cat README.md | grep -v 'project website' > docs/index.md
cp CHANGELOG.md docs/changelogs/changelog.md
cp CONTRIBUTING.md docs/contribute/contributing.md

# Build the site locally

     *
     * @param userProperties The mutable user properties, never {@code null}.
     * @see #contribute(ProtoSession)
     */
    default void contribute(Map<String, String> userProperties) {}

    /**
     * Invoked just before session is created with proto session instance. The proto session contains user and

How to contribute
=================

Thank you so much for wanting to contribute to Guava! Here are a few important
things you should know about contributing:

1.  API changes require discussion, use cases, etc. Code comes later.
2.  Pull requests are great for small fixes for bugs, documentation, etc.
3.  Pull requests are not merged directly into the master branch.
4.  Code contributions require signing a Google CLA.

API changes
-----------

 * Classes implementing this interface can be discovered and loaded by Maven through the
 * Java ServiceLoader mechanism, allowing plugins and extensions to contribute functionality
 * to the Maven build process.
 * <p>
 * SPI services are typically registered in {@code META-INF/services/} files corresponding to
 * the specific service interface being implemented.
 * <p>

## FastAPI Experts

The people that help others the most in GitHub Discussions can become [**FastAPI Experts**](./fastapi-people.md#fastapi-experts){.internal-link target=_blank}.

This is normally the best way to contribute to the project.

## External Contributions

External contributions are very welcome and appreciated, including answering questions, submitting PRs, etc. 🙇‍♂️

     * <p>
     * This method is called by Maven during initialization to collect all custom enum values
     * that should be registered. The returned collection should contain all the enum values
     * that this provider wants to contribute.
     * <p>
     * The values returned by this method should be created using the appropriate factory methods
     * for the specific enum type, such as {@code language()}, {@code projectScope()}, or
     * {@code pathScope()}.

import org.apache.maven.lifecycle.mapping.LifecycleMojo;
import org.apache.maven.lifecycle.mapping.LifecyclePhase;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * TODO: this is session scoped as SPI can contribute.
 */
@Named
@Singleton
public class DefaultPackagingRegistry
        extends ExtensibleEnumRegistries.DefaultExtensibleEnumRegistry<Packaging, PackagingProvider>
        implements PackagingRegistry {

 So I guess it's important to figure out what people are using properties
 files for and see if we can't incorporate it all into the POM. Or if we do
 have properties file (something I would like to avoid) say they don't
 contribute in any meaningful way to information in the POM. For example a
 properties file could be used the specify $ so it can be interpolated in
 <developerConnection/> but you couldn't use a properties file to specify the

            int length = 0;
            for (int i = 0; i < pattern.length(); i++) {
                final char c = pattern.charAt(i);
                if (c == '*') {
                    // Wildcard doesn't contribute to priority length
                    continue;
                } else if (c == '$') {
                    // $ at the end adds to specificity
                    length++;
                } else {