folders 300 in the present implementations described herein annotations that are to be indexed by gas may be predefined in the folder u201c gas properties u201d 302 the folder u201c gas properties u201d 302 may reside in a u201c build system lib gas u201d folder the example folder u201c gas properties u201d 302 may be added as indexed annotation the file u201c gas xml u201d 304 may be generated into a lt resource_folder gt before the build system packages a java archive or jar file in one implementation the file u201c gas xml u201d 304 may be packaged with the java archive or jar file and particularly into a module jar as illustrated in fig3 in an implementation a build system may call gas jar to generate the u201c gas xml u201d 306 during u201c package service u201d target the gas jar may package a simple scanner that scans classes folder for finding classes by using u201c resourcescanner u201d the file u201c gas xml u201d 306 contains the xml serialized by xstream from a map which maps annotation with a set of classes that are annotated with that annotation fig4 shows an exemplary process 400 for implementing at least in part the technology described herein in particular process 400 depicts a flow to generate and implement an annotating index the process 400 may be performed by a computing device an example architecture of such a computer device is described below with reference to fig5 at 402 running a build file is performed in certain implementations the build file is a java file that is executed at 404 generating an xml file or an index is performed as the build file is run.