```

## Development

### Build Commands
```bash
# Compile the source code
mvn compile

# Build JAR file
mvn package

# Clean and rebuild
mvn clean compile

# Install to local repository
mvn install
```

### Testing
```bash
# Run all tests (JUnit 4 based)
mvn test

# Run specific test class
mvn test -Dtest=SpecificTest

# Alternative test runner

     *
     * This method handles SSO logout requests, coordinating with the SSO provider
     * to properly terminate the user's SSO session. It may involve redirecting
     * to the SSO provider's logout endpoint or performing local logout operations.
     *
     * @return ActionResponse directing to the logout page or SSO provider logout endpoint
     */
    @Execute
    public ActionResponse logout() {

    /**
     * User property for chained LRM: the new "head" local repository to use, and "push" the existing into tail.
     * Similar to <code>maven.repo.local.tail</code>, this property may contain comma separated list of paths to be
     * used as local repositories (combine with chained local repository), but while latter is "appending" this
     * one is "prepending".
     *
     * @since 4.0.0

     * Processes collection definitions and tracks the element hierarchy.
     *
     * @param uri the namespace URI, or empty string if none
     * @param localName the local name without prefix, or empty string if namespace processing is not performed
     * @param qName the qualified name with prefix, or empty string if qualified names are not available

    /**
     * Main to test version parsing and comparison.
     * <p>
     * To check how "1.2.7" compares to "1.2-SNAPSHOT", for example, you can issue
     * <pre>java -jar ${maven.repo.local}/org/apache/maven/maven-artifact/${maven.version}/maven-artifact-${maven.version}.jar "1.2.7" "1.2-SNAPSHOT"</pre>
     * command to command line. Result of given command will be something like this:
     * <pre>

             * global profile manager which is required to build a POM like a CLI invocation does. Failure to consider
             * the activated profiles can cause repo declarations to be lost which in turn will result in artifact
             * resolution failures, in particular when using the enhanced local repo which guards access to local files
             * based on the configured remote repos.

            if (typeof options.locale.daysOfWeek === 'object')
                this.locale.daysOfWeek = options.locale.daysOfWeek.slice();

            if (typeof options.locale.monthNames === 'object')
              this.locale.monthNames = options.locale.monthNames.slice();

            if (typeof options.locale.firstDay === 'number')
              this.locale.firstDay = options.locale.firstDay;

Nevertheless, if you just use `pip` directly, the packages would be installed in your **global Python environment** (the global installation of Python).

### The Problem { #the-problem }

So, what's the problem with installing packages in the global Python environment?

null!=e.meridiemHour?e.meridiemHour(a,t):(null!=e.isPM&&((s=e.isPM(t))&&a<12&&(a+=12),s||12!==a||(a=0)),a)}(e._locale,e._a[De],e._meridiem),null!==(n=L(e).era)&&(e._a[fe]=e._locale.erasConvertYear(n,e._a[fe])),wa(e),la(e)}else Ta(e);else ka(e)}function ba(e){var a,t,s=e._i,n=e._f;return e._locale=e._locale||ua(e._l),null===s||void 0===n&&""===s?y({nullInput:!0}):("string"==typeof s&&(e._i=s=e._locale.preparse(s)),D(s)?new k(la(s)):(d(s)?e._d=s:i(n)?function(e){var a,t,s,n,r,d,i=!1;if(0===e._f.length)return...

/**
 * Manages the organization and access of artifacts within the local Maven repository.
 * The local repository serves as a cache for downloaded remote artifacts and storage
 * for locally installed artifacts. This manager provides services to determine the
 * appropriate paths for artifacts within the local repository structure.
 *
 * <p>The LocalRepositoryManager is responsible for:
 * <ul>