About

Profiles bundle some TrueVFS modules so that you can easily use them as a single all-in-one dependency. Other than that, profiles do not provide additional functionality. For a complete list of the modules bundled in a profile, please refer to its Dependencies report.

Using a profile with Maven

When using Maven, you can simply declare a profile as a dependency in your POM as follows:

<dependency>
    <groupId>net.java.truevfs</groupId>
    <artifactId>truevfs-profile-default</artifactId>
    <version>0.12.0</version>
    <type>pom</type>
</dependency>

Note that you should specify the dependency type as pom.

Excluding unwanted modules

A profile may bundle modules you do not want to use. You can exclude a module in your dependency declaration as follows:

<dependency>
    <groupId>net.java.truevfs</groupId>
    <artifactId>truevfs-profile-default</artifactId>
    <version>0.12.0</version>
    <type>pom</type>
    <exclusions>
        <exclusion>
            <groupId>net.java.truevfs</groupId>
            <artifactId>truevfs-driver-zip</artifactId>
        </exclusion>
    </exclusions>
</dependency>

The previous example assumes you would want to exclude the TrueVFS Driver ZIP.

Using a profile without Maven

If you do not want to use Maven then you can directly download the all-in-one JAR of a profile from Maven Central. These all-in-one JARs contain all transitive dependencies, including third party JARs, e.g. for Apache Commons Compress et al. However, you cannot exclude any dependencies or change their version.