[MGNLDAM-928] Do not bypass the binary compatibility check on dam-app-compatibility Created: 25/Jan/21 Updated: 26/Jan/21 Resolved: 26/Jan/21 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Maxime Michel |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
In the following PR, sang.ngo ran into a situation in which it wasn't clear how to make the binary compatibility check without bypassing it altogether. This had however been experimented with by rdhar in his initial research work: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/pull-requests/1639/diff#security-app/pom.xml The goal of this ticket is to replace the disabling of the check by a more subtle configuration, and to then document it in the following Wiki page: https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=231783236 |
| Comments |
| Comment by Maxime Michel [ 26/Jan/21 ] |
|
Source commit got reverted. There is something weird with japicmp that's worth investigating regardless, but the description of this ticket is obsolete for now. |