/*
 * Copyright 2021 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.integtests.fixtures.validation;

import org.gradle.internal.reflect.validation.Severity;

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

/**
 * A dummy annotation which is used to trigger validation problems
 * during tests
 */
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.METHOD, ElementType.FIELD})
public @interface ValidationProblem {
    Severity value() default Severity.WARNING;
}

@@ -950,19 +950,16 @@
 problems
-%0A *
  during 
@@ -963,16 +963,210 @@
 ng tests
+.%0A *%0A * This is handled via %7B@link ValidationProblemPropertyAnnotationHandler%7D,%0A * a service available globally in the embedded integration test runner only.%0A *%0A * @see ValidationServicesFixture
 %0A */%0A@Re

Document how the `@ValidationProblem` annotation works