assertNotNull(sitePath);
        assertTrue(sitePath.toString().contains("site"));
    }

    public void test_getPluginPath() {
        Path pluginPath = ResourceUtil.getPluginPath("plugin.jar");
        assertNotNull(pluginPath);
        assertTrue(pluginPath.toString().contains("plugin"));
    }

    public void test_getProjectPropertiesFile() {

Configuration config = new PropertyConfiguration(props);
CIFSContext context = new BaseContext(config);
```

## 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

Releases
--------

Our [change log][changelog] has release history.

The latest release is available on [Maven Central](https://search.maven.org/artifact/com.squareup.okhttp3/okhttp/5.1.0/jar).

```kotlin
implementation("com.squareup.okhttp3:okhttp:5.1.0")
```

Snapshot builds are [available][snap]. [R8 and ProGuard][r8_proguard] rules are available.

        <artifactId>toolchains-maven-plugin</artifactId>
      </plugin>
      <plugin>
        <artifactId>maven-toolchains-plugin</artifactId>
      </plugin>
      <plugin>
        <artifactId>maven-jar-plugin</artifactId>
      </plugin>
      <plugin>
        <extensions>true</extensions>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <version>5.1.9</version>

     *
     * <h4>Design note</h4>
     * All types of path are determined together because they are sometime mutually exclusive.
     * For example, an artifact of type {@value org.apache.maven.api.Type#JAR} can be placed
     * either on the class-path or on the module-path. The project needs to make a choice
     * (possibly using heuristic rules), then add the dependency in only one of the paths
     * identified by {@link PathType}.

    try {
      fileSystem.read(file) {
        put(inputStream(), RepositoryPlugin.PutOptions())
        println("Deployed ${file.name}")
      }
    } catch (e: IllegalArgumentException) {
      if ("Jar does not have a symbolic name" in e.message!!) {
        println("Skipped non-OSGi dependency: ${file.name}")
        return
      }
      throw e
    }
  }

  companion object {

    tr '\n' ' '
  fi
}

MAVEN_PROJECTBASEDIR="`find_maven_basedir "$@"`"
MAVEN_OPTS="$MAVEN_OPTS `concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config"`"
LAUNCHER_JAR=`echo "$MAVEN_HOME"/boot/plexus-classworlds-*.jar`
LAUNCHER_CLASS=org.codehaus.plexus.classworlds.launcher.Launcher

# For Cygwin and MinGW, switch paths to Windows format before running java(1) command
if $cygwin || $mingw ; then
  [ -n "$JAVA_HOME" ] &&

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Immutable;
import org.apache.maven.api.annotations.Nonnull;

/**
 * A Maven artifact is a file, typically a JAR, that is produced and used by Maven projects.
 * It is identified by a unique combination of a group ID, artifact ID, version, classifier,
 * and extension, and it is stored in a repository for dependency management and build purposes.

    /**
     * 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>

application/vnd.ms-access      mdb mda mde      # MS Access
application/vnd.ms-project     mpp              # MS Project
application/x-wais-source      src              # WAIS Sources
application/zip                zip jar          # ZIP Compressed File
audio/basic                    au snd           # Audio Sound File
audio/x-aiff                   aif aiff aifc    # AIFF Sound File
audio/x-midi                   mid              # MIDI Sound File