Across the provided target versions, the following number of conflicts have been found: +--------------------------+-----+ |Type |Total| +--------------------------+-----+ |BEAN_OVERWRITE |1 | +--------------------------+-----+ |BEAN_RESTRICTED_CLASS |1 | +--------------------------+-----+ |CLASSPATH_CONFLICT |1 | +--------------------------+-----+ |ALFRESCO_INTERNAL_USAGE |2 | +--------------------------+-----+ |WAR_LIBRARY_USAGE |1 | +--------------------------+-----+ |JAKARTA_MIGRATION_CONFLICT|2 | +--------------------------+-----+ (use option --verbose for version details)
Alfresco extensions might hide conflicts of the following types if they contain Alfresco-specific libraries:
- BEAN_RESTRICTED_CLASS
- WAR_LIBRARY_USAGE
- ALFRESCO_INTERNAL_USAGE
They are hidden because these types of conflict exclude from processing all the classes in the extension’s classpath. By including a class present in both extension and WAR in the processing, this may partially solve the issue because:
- Two classes with the same canonical name could come from two different libraries, for example, an extension-specific library and an Alfresco library, or two different versions of the same Alfresco library. Therefore, checking the class name alone is not enough.
- Comparing their libraries would help only when the same library with the same version is used in both the extension and the WAR. In case of different versions of the same library, the class won’t be recognized as an Alfresco internal class.