-
Story
-
Resolution: Duplicate
-
Major
-
None
-
None
From JBoss EAP 7.1 Migration Guide:
"5.16. JBoss Logging Changes
If your application uses JBoss Logging, be aware that the annotations in the org.jboss.logging package are now deprecated in JBoss EAP 7. They have been moved to the org.jboss.logging.annotations package, so you must update your source code to import the new package.
The annotations have also moved to a separate Maven groupId:artifactId:version (GAV) ID so you need to add a new project dependency for org.jboss.logging:jboss-logging-annotations in your project pom.xml file.
...
The following table lists the deprecated annotation classes and corresponding replacements.
Table 5.1. Deprecated Logging Annotation Replacements
Deprecated Class | Replacement Class | |
---|---|---|
org.jboss.logging.Cause | org.jboss.logging.annotations.Cause | |
org.jboss.logging.Field | org.jboss.logging.annotations.Field | |
org.jboss.logging.FormatWith | org.jboss.logging.annotations.FormatWith | |
org.jboss.logging.LoggingClass | org.jboss.logging.annotations.LoggingClass | |
org.jboss.logging.LogMessage | org.jboss.logging.annotations.LogMessage | |
org.jboss.logging.Message | org.jboss.logging.annotations.Message | |
org.jboss.logging.MessageBundle | org.jboss.logging.annotations.MessageBundle | |
org.jboss.logging.MessageLogger | org.jboss.logging.annotations.MessageLogger | |
org.jboss.logging.Param | org.jboss.logging.annotations.Param | |
org.jboss.logging.Property | org.jboss.logging.annotations.Property | " |
A new RHAMT Rule should be added to address this app migration issue.
When: application uses/references any of the deprecated annotation classes
Perform: warn the user about the package name change