* @return the profile path
     */
    public String getProfilePath() {
        return this.profilePath;
    }

    /**
     * Returns the user's home directory path.
     * @return the home directory path
     */
    public String getHomeDirectory() {
        return this.homeDirectory;
    }

    /**
     * Returns the user's home drive letter.
     * @return the home drive

    }

    private static Stream<Arguments> completionFilterProvider() {
        return Stream.of(Arguments.of(FILE_NOTIFY_CHANGE_FILE_NAME, "File name changes"),
                Arguments.of(FILE_NOTIFY_CHANGE_DIR_NAME, "Directory name changes"),
                Arguments.of(FILE_NOTIFY_CHANGE_ATTRIBUTES, "Attribute changes"), Arguments.of(FILE_NOTIFY_CHANGE_SIZE, "Size changes"),

 * {{{./logging.html}logging API}}.

 * since 3.3.1 (see {{{/docs/3.3.1/release-notes.html#Core_Extensions}3.3.1 release notes}} for more details),
   per project settings can be defined by files in <<<.mvn/>>> directory:

   * <<<.mvn/jvm.config>>> containing jvm options,

   * <<<.mvn/maven.config>>> containing Maven command-line parameter,

   * <<<.mvn/extensions.xml>>> containing {{{./core-extensions.html}a list of extensions}},

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent</name>
  <description>Most classical case: child in direct subdirectory with directory name == child artifactId</description>

  <modules>
    <module>child-artifact-id</module>
  </modules>

  <!-- 5 urls in the pom will be inherited with path added -->

 * we'll make sure to filter the list of packages before generating the file.
 *
 * It is assumed that the layout of the directories follow the JVM conventions. This allows us to effectively skip opening the class files to determine the real package name.
 */
@CacheableTask
abstract class PackageListGenerator : DefaultTask() {

    companion object {

    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-repository-metadata</artifactId>

  <name>Maven Repository Metadata Model</name>
  <description>Per-directory local and remote repository metadata.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-annotations</artifactId>
    </dependency>
    <dependency>

    fun extractDmg(androidStudioDistribution: File) {
        val volumeDir = "/Volumes/$VOLUME_NAME"
        val srcDir = "/Volumes/$VOLUME_NAME/Android Studio.app"
        require(!File(srcDir).exists()) {
            "The directory $srcDir already exists. Please unmount it via `hdiutil detach $volumeDir`."
        }

        try {
            execOps.exec {

        assertPathWithNormalizedFileSeparators(pom.getValue("build/testSourceDirectory"));
        assertPathWithNormalizedFileSeparators(pom.getValue("build/resources[1]/directory"));
        assertPathWithNormalizedFileSeparators(pom.getValue("build/testResources[1]/directory"));
        assertPathWithNormalizedFileSeparators(pom.getValue("build/filters[1]"));
        assertPathWithNormalizedFileSeparators(pom.getValue("reporting/outputDirectory"));

				"application/vnd.ipunplugged.rcprofile",
				"application/vnd.irepository.package+xml",
				"application/vnd.is-xpr",
				"application/vnd.jam",
				"application/vnd.japannet-directory-service",
				"application/vnd.japannet-jpnstore-wakeup",
				"application/vnd.japannet-payment-wakeup",
				"application/vnd.japannet-registration",
				"application/vnd.japannet-registration-wakeup",

- `stopwords.txt` - Words to exclude from indexing
- `stemmer_override.txt` - Custom stemming rules
- `protwords.txt` - Protected words (no stemming)
- `mapping.txt` - Character/token mappings

**Example directory structure:**
```
dictionary/
└── sv/
    ├── stopwords.txt
    ├── stemmer_override.txt
    └── protwords.txt
```

## Important Notes

### No Database Changes Required