https://github.com/xenit-eu/alfresco-hotfix-mnt-20557

https://github.com/xenit-eu/alfresco-hotfix-mnt-20557

alfresco alfresco-module

Last synced: 6 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/xenit-eu/alfresco-hotfix-mnt-20557
• Owner: xenit-eu
• License: apache-2.0
• Created: 2019-04-26T11:36:26.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2023-12-15T02:47:19.000Z (11 months ago)
• Last Synced: 2024-04-16T13:05:13.648Z (7 months ago)
• Topics: alfresco, alfresco-module
• Size: 84 KB
• Stars: 2
• Watchers: 6
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Hotfix for Alfresco issue [MNT-20557](https://alfresco.atlassian.net/browse/MNT-20557)

## Description

[MNT-20557](https://alfresco.atlassian.net/browse/MNT-20557) issue description (credits to Axel Faust):

> Alfresco Content Services 6.x includes `javax.annotation-api-1.2.jar`, `jsr250-api-1.0.jar` and `geronimo-annotation_1.0_spec-1.1.1.jar`. All three JARs are essentially providing the same spec API, albeit from different source projects and in different versions. They overlap in 11 classes which are common in the 1.0 spec version of javax.annotation, with javax.annotation-api-1.2.jar providing a more extensive set of classes.

>

> `jsr250-api-1.0.jar` and `geronimo-annotation_1.0_spec-1.1.1.jar` are direct dependencies in alfresco-repository, while `javax.annotation-api-1.2.jar` is a transitive dependency in alfresco-data-model via TIKA parsers.

There are multiple instances of duplicate class definitions on the classpath, but this one in particular blows up with Java 11 in Alfresco 6.1 and higher when you try to use Spring annotations. 

## Workaround

The Alfresco Module Package provided by this project will **overwrite** the two conflicting JARs with two **empty** jars in the `WEB-INF/lib` folder of the Alfresco distribution: `jsr250-api-1.0.jar` and `geronimo-annotation_1.0_spec-1.1.1.jar`. This effectivly removes the conflicting classes from the classpath and only one correct implementation of the JSR-250 'Common Annotations' specification remains.

## Artifact Coordinates

The AMP artifact is available in Maven Central:

```xml

  eu.xenit.alfresco

  alfresco-hotfix-MNT-20557

  1.0.2

  amp

```

## Problem analysis

> The `javax.annotation.Resource` class in `jsr250-api-1.0.jar` does not define / provide the `String lookup()` method, while the `javax.annotation-api-1.2.jar` (Alfresco 6.0) and `javax.annotation-api-1.3.2.jar` (Alfresco 6.1 / 6.2) does, as does the Oracle Java 8 core library `rt.jar`.

* This means this was never a problem on JDK8, because the class was loaded from the bootstrap-classloader and never from the system classpath.

* In Java 9 some Java EE modules were deprecated and finally removed in Java 11. This means that `javax.annotation.Resource` is no longer available from the bootstrap classpath, but should be loaded from `javax.annotation:javax.annotation-api` instead.