All Downloads are FREE. Search and download functionalities are using the official Maven repository.

org.gradle.api.file.FileCollection Maven / Gradle / Ivy

There is a newer version: 8.6
Show newest version
/*
 * Copyright 2010 the original author or authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.gradle.api.file;

import groovy.lang.Closure;
import org.gradle.api.Buildable;
import org.gradle.api.Incubating;
import org.gradle.api.provider.Provider;
import org.gradle.api.specs.Spec;
import org.gradle.api.tasks.AntBuilderAware;
import org.gradle.internal.HasInternalProtocol;

import java.io.File;
import java.util.Set;

/**
 * 

A {@code FileCollection} represents a collection of file system locations which you can query in certain ways. A file collection * is can be used to define a classpath, or a set of source files, or to add files to an archive.

* *

There are no methods on this interface that allow the contents of the collection to be modified. However, there are a number of sub-interfaces, such as {@link ConfigurableFileCollection} that * allow changes to be made.

* *

A file collection may contain task outputs. The file collection tracks not just a set of files, but also the tasks that produce those files. When a file collection is used as a task input * property, Gradle will take care of automatically adding dependencies between the consuming task and the producing tasks.

* *

You can obtain a {@code FileCollection} instance using {@link org.gradle.api.Project#files}.

*/ @HasInternalProtocol public interface FileCollection extends Iterable, AntBuilderAware, Buildable { /** * Returns the content of this collection, asserting it contains exactly one file. * * @return The file. * @throws IllegalStateException when this collection does not contain exactly one file. */ File getSingleFile() throws IllegalStateException; /** * Returns the contents of this collection as a {@link Set}. The contents of a file collection may change over time. * *

Note that this method returns {@link File} objects that represent locations on the file system. These {@link File} objects do not necessarily refer to regular files. * Depending on the implementation of this file collection and how it has been configured, the returned set may contain directories, or missing files, or any other kind of * file system element. *

* * @return The files. Returns an empty set if this collection is empty. */ Set getFiles(); /** * Determines whether this collection contains the given file. Generally, this method is more efficient than calling * {@code getFiles().contains(file)}. * * @param file The file to check for. * @return true if this collection contains the given file, false otherwise. */ boolean contains(File file); /** * Returns the contents of this collection as a platform-specific path. This can be used, for example, in an Ant * <path> element. * * @return The path. Returns an empty string if this collection is empty. */ String getAsPath(); /** *

Returns a {@code FileCollection} which contains the union of this collection and the given collection. The * returned collection is live, and tracks changes to both source collections.

* *

You can call this method in your build script using the {@code +} operator.

* * @param collection The other collection. Should not be null. * @return A new collection containing the union. */ FileCollection plus(FileCollection collection); /** *

Returns a {@code FileCollection} which contains the difference between this collection and the given * collection. The returned collection is live, and tracks changes to both source collections.

* *

You can call this method in your build script using the {@code -} operator.

* * @param collection The other collection. Should not be null. * @return A new collection containing the difference. */ FileCollection minus(FileCollection collection); /** *

Restricts the contents of this collection to those files which match the given criteria. The filtered * collection is live, so that it reflects any changes to this collection.

* *

The given closure is passed the File as a parameter, and should return a boolean value.

* * @param filterClosure The closure to use to select the contents of the filtered collection. * @return The filtered collection. */ FileCollection filter(Closure filterClosure); /** *

Restricts the contents of this collection to those files which match the given criteria. The filtered * collection is live, so that it reflects any changes to this collection.

* * @param filterSpec The criteria to use to select the contents of the filtered collection. * @return The filtered collection. */ FileCollection filter(Spec filterSpec); /** * Returns true if this collection is empty. Generally, calling this method is more efficient than calling {@code * getFiles().isEmpty()}. * * @return true if this collection is empty, false otherwise. */ boolean isEmpty(); /** * Converts this collection to a {@link FileTree}, if not already. For each file in this collection, the resulting file * tree will contain the source file at the root of the tree. For each directory in this collection, the resulting * file tree will contain all the files under the source directory. * *

The returned {@link FileTree} is live, and tracks changes to this file collection and the producer tasks of this file collection.

* * @return this collection as a {@link FileTree}. Never returns null. */ FileTree getAsFileTree(); /** * Returns the contents of this file collection as a {@link Provider} of {@link FileSystemLocation} instances. See {@link #getFiles()} for more details. * *

The returned {@link Provider} is live, and tracks changes to this file collection and the producer tasks of this file collection.

* * @since 5.6 */ @Incubating Provider> getElements(); /** * Ant types which a {@code FileCollection} can be mapped to. */ enum AntType { MatchingTask, FileSet, ResourceCollection } /** * Adds this collection to an Ant task as a nested node. The given type determines how this collection is added: * *
    * *
  • {@link AntType#MatchingTask}: adds this collection to an Ant MatchingTask. The collection is converted to a * set of source directories and include and exclude patterns. The source directories as added as an Ant Path with * the given node name. The patterns are added using 'include' and 'exclude' nodes.
  • * *
  • {@link AntType#FileSet}: adds this collection as zero or more Ant FileSets with the given node name.
  • * *
  • {@link AntType#ResourceCollection}: adds this collection as zero or more Ant ResourceCollections with the * given node name.
  • * *
* * You should prefer using {@link AntType#ResourceCollection}, if the target Ant task supports it, as this is * generally the most efficient. Using the other types may involve copying the contents of this collection to a * temporary directory. * * @param builder The builder to add this collection to. * @param nodeName The target node name. * @param type The target Ant type */ void addToAntBuilder(Object builder, String nodeName, AntType type); /** * Adds this collection to an Ant task as a nested node. Equivalent to calling {@code addToAntBuilder(builder, * nodeName,AntType.ResourceCollection)}. */ @Override Object addToAntBuilder(Object builder, String nodeName); }




© 2015 - 2024 Weber Informatics LLC | Privacy Policy