An issue has been just indentified with the Minyaa 3.4 for all 6.2.x and 6.3.x versions.
All functionnal tests were passed with success but the simple test of disabling a plugin was not done and it appears that it is causing some issue.
Impact on the functionalities has not been confirmed, but it is better for not using this version in Production environment.
All investigations are in progress to idenfify the root cause and we hope to provide an upate soon with a fix.
For reminder :
- Minyaa 3.4 for JIRA 6.0.x and 6.1.x are correct
- Minyaa 3.4 for JIRA 6.2.x to 6.3.5 are working, but fails on plugin disabling
- JIRA 6.3.6 and over are not yet supported
Update Oct’22 17:50 CET:
After a first analysis, it appears that we are facing to a JIRA Bug occuring since JIRA 6.2.
When a plugin V1 is disabled, its <component> modules are disabled one by one. But with JIRA 6.2, instead of removing them from the Pico-Container cache, it try to add them, and it causes the error “org.picocontainer.PicoCompositionException: Duplicate Keys not allowed. Duplicate for ‘xxxx'”.
See details in MYAA-1474.
Update Oct’23 10:00 CET:
Related the above issue, a bug seems to confirmed in JIRA : See JRA-40530
Related compatibility of Minyaa 3.4, the version 6.3.4-3.4 is compatible for JIRA 6.3.4 to 6.3.6.
A new version will be required for JIRA 6.3.7 and over.