/**
     * Constructs a new ThumbnailGenerationException with the specified message and cause.
     *
     * @param message the exception message
     * @param cause the underlying cause of this exception
     */
    public ThumbnailGenerationException(final String message, final Throwable cause) {
        super(message, cause);
    }

    /**
     * Constructs a new ThumbnailGenerationException with the specified message.

 *          ComponentConfigurator implementation to be used.
 *          <br>
 *          <i>NOTE: This will only be used in very special cases, using a highly controlled vocabulary of possible
 *          values. (Elements like this are why it's a good idea to use the descriptor tools.)</i>
 *      </td>
 *   </tr>
 *   <tr>
 *      <td>phase</td>

	updateCallback.Clauses = config.UpdateClauses

	rowCallback := db.Callback().Row()
	rowCallback.Register("gorm:row", RowQuery)
	rowCallback.Clauses = config.QueryClauses

	rawCallback := db.Callback().Raw()
	rawCallback.Register("gorm:raw", RawExec)
	rawCallback.Clauses = config.QueryClauses

    /**
     * Constructs a new SearchEngineClientException with the specified message and cause.
     *
     * @param message the detail message explaining the exception
     * @param cause   the underlying cause of the exception
     */
    public SearchEngineClientException(final String message, final Throwable cause) {
        super(message, cause);
    }

    /**

 * including those in many JDK classes.
 *
 * <p>{@code Object.hashCode} implementations tend to be very fast, but have weak collision
 * prevention and <i>no</i> expectation of bit dispersion. This leaves them perfectly suitable for
 * use in hash tables, because extra collisions cause only a slight performance hit, while poor bit

 * including those in many JDK classes.
 *
 * <p>{@code Object.hashCode} implementations tend to be very fast, but have weak collision
 * prevention and <i>no</i> expectation of bit dispersion. This leaves them perfectly suitable for
 * use in hash tables, because extra collisions cause only a slight performance hit, while poor bit

### Properties in entirely new classes

When developing an entirely new class (task, extension, domain object, etc), the API should consist of managed lazy properties.

Preferably, these new classes should be 100% managed and have their implementation generated by Gradle at runtime.

 * This exception can be thrown with a message, a cause, or both.
 */
public class MimeTypeException extends CrawlerSystemException {

    private static final long serialVersionUID = 1L;

    /**
     * Creates a new MimeTypeException with the specified detail message and cause.
     *
     * @param message the detail message explaining the reason for the exception
     * @param cause the underlying cause of the exception
     */

     * @param propertyName
     *            Property name
     * @param cause
     *            The cause of the exception
     */
    public IllegalPropertyRuntimeException(final Class<?> targetClass, final String propertyName, final Throwable cause) {
        super("ECL0059", asArray(targetClass.getName(), propertyName, cause), cause);
        this.targetClass = targetClass;
        this.propertyName = propertyName;
    }

            String locationInPom,
            String offendingVersion,
            File pomFile,
            InvalidVersionSpecificationException cause) {
        super(projectId, formatMessage(projectId, locationInPom, offendingVersion, cause), pomFile, cause);
        this.locationInPom = locationInPom;
        this.offendingVersion = offendingVersion;
    }

    private static String formatMessage(