[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19820: ----------------------------------------------- To check if a library or a project has Batch artifacts, there is only one way - to scan classes. The list of wildfly projects that have Batch API in classpath, with number of scanned classes and used time: wildfly-testsuite-shared - 56240 classees in 24068 ms, wildfly-testsuite-compat - 9990 classes in 5784 ms, wildfly-jberet - 7578 classes in 3229 ms, wildfly-ts-integ-xts - 4967 classes in 2309 ms, wildfly-batch - 4885 classes in 773 ms, wildfly-spec-api-test - 3096 classes in 109 ms, wildfly-ts-integ-basic 2321 classes in 331 ms, wildfly-ts-integ-picketlink - 868 classes in 63 ms, wildfly-ts-integ-clustering - 249 classes in 63 ms, wildfly-ts-integ-web - 206 classes in 40 ms, wildfly-ts-integ-smoke - 231 classes in 25 ms, wildfly-ts-integ-rts - 125 classes in 9 ms, wildfly-ts-integ-rbac - 118 classes in 6 ms, wildfly-ts-integ-multinode - 135 classes in 17 ms, wildfly-ts-integ-manualmode - 160 classes in 14 ms, wildfly-ts-integ-java8 - 117 classes in 7 ms, wildfly-ts-integ-iiop 131 classes in 7 ms, wildfly-testsuite-integration-mixed-domain - 129 classes in 13 ms, wildfly-testsuite-integration-domain - 138 classes in 10 ms, Totally about 92000 classes processed in 37 s. These projects hava totally about 450 jars in their classpath, and search for Batch artifacts in them takes 56 s. Totally for 92000 classes and 450 jars - 93 s. -- This message was sent by Atlassian JIRA (v6.3.15#6346)