What we are doing when developing extensions (AMP files) is, that we double check jars included in alfresco.war (tedious work sometimes as you have to take into account also dependencies of dependencies) and just put "provided" to POM.
<dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> <version>2.4</version> <scope>provided</scope> </dependency>
It's worth of time spent because AMP doesn't include these jars, so you will not replace alfresco.war jars. Worst that can happen is that your extension doesn't work, but you don't risk seemingly "random" errors that can arise weeks after the deployment of your AMP.
Thank you guys,
now the problem is fully resolved.
I would carefully check dependencies next time.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.