/**
 * Copyright (C) 2014 android10.org. All rights reserved.
 * @author Fernando Cejas (the android10 coder)
 */
package com.fernandocejas.android10.gandalf.annotation;

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

import static java.lang.annotation.ElementType.CONSTRUCTOR;
import static java.lang.annotation.ElementType.METHOD;
import static java.lang.annotation.RetentionPolicy.CLASS;

@Retention(CLASS)
@Target({ CONSTRUCTOR, METHOD })
public @interface GStrictMode {}

@@ -414,16 +414,838 @@
 CLASS;%0A%0A
+/**%0A * %3Cbr%3EGandalf Strict Mode enables Android %7B@link android.os.StrictMode%7D on your application, so%0A * when violations are detected, the logcat output will show information about these ones as they%0A * happen.%3Cbr%3E%0A *%0A * %3Cbr%3EREMEMBER: It is not necessary to annotate each method/constructor, it is enough with%0A * just using the annotation on the main entry point of your app to activate%0A * %7B@link android.os.StrictMode%7D. Thus this feature will live along the execution of your app.%3Cbr%3E%0A *%0A * %3Cbr%3EFOR EXAMPLE: It is a good practice to annotate%0A * %7B@link android.app.Activity#onCreate(android.os.Bundle)%7D method of your main activity or%0A * %7B@link android.app.Application#onCreate()%7D method of your %7B@link android.app.Application%7D class%0A * so the violations can be detected as they happen along the execution of your app.%0A */%0A
 @Retenti

Add documentation to Gandalf Strict Mode annotation.