[ https://issues.jboss.org/browse/LOGTOOL-105?page=com.atlassian.jira.plugi... ] Sanne Grinovero commented on LOGTOOL-105: ----------------------------------------- As an alternative to enabling this switch, I've found that adding the dependency explicitly also works fine. For example in a Maven build I can add them as dependencies to the annotation processor: {code:xml} <plugin> <groupId>org.bsc.maven</groupId> <artifactId>maven-processor-plugin</artifactId> <version>2.2.4</version> <executions> <execution> <id>process</id> <goals> <goal>process</goal> </goals> <phase>generate-sources</phase> <configuration> <processors> <processor>org.jboss.logging.processor.apt.LoggingToolsProcessor</processor> </processors> <compilerArguments>-AskipGeneratedAnnotation=false -AtranslationFilesPath=${project.basedir}/src/main/resources/ -source 1.7 -target 1.7</compilerArguments> </configuration> </execution> </executions> <dependencies> <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging-processor</artifactId> <version>${jbossLoggingProcessorVersion}</version> <scope>compile</scope> </dependency> <dependency> <groupId>javax.annotation</groupId> <artifactId>jsr250-api</artifactId> <version>1.0</version> </dependency> </dependencies> </plugin>{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)