Started by an SCM change3987bdc2bfa9a9df42d4f12604f2bf57c775643a0d87bdc2bfa9a9df42d4f12604f2bf57c775643a0dorigin/develop87bdc2bfa9a9df42d4f12604f2bf57c775643a0d87bdc2bfa9a9df42d4f12604f2bf57c775643a0dorigin/develop87bdc2bfa9a9df42d4f12604f2bf57c775643a0d87bdc2bfa9a9df42d4f12604f2bf57c775643a0dorigin/develophttp://sing-group.org/dt/gitlab/dgss-2526-teamA/microstories.gitfalse#39115643250022microstories-2526-teamA #3939false3941SUCCESS1762196890191http://sing.ei.uvigo.es/dt/jenkins/view/all/job/microstories-2526-teamA/39/tests/pom.xmldomain/pom.xmlear/pom.xml87bdc2bfa9a9df42d4f12604f2bf57c775643a0d1762196691000http://sing.ei.uvigo.es/dt/jenkins/user/mrjatoMiguel Reboiro-Jatomrjato@uvigo.esFixes resource management configuration causing test failure When disabling the maven-resources-plugin to prevent WildFly from being downloaded during test execution in modules that do not need it, the inclusion of resources in the packages was also disabled. This led to errors in the execution of tests in other modules that could not find the XMLs of the datasets or the script files. This problem has been solved by disabling the “copy-wildfly-resources” execution configuration in modules that do not need WildFly instead of disabling the “maven-resources-plugin” plugin completely. 2025-11-03 20:04:51 +010087bdc2bfa9a9df42d4f12604f2bf57c775643a0dFixes resource management configuration causing test failureeditdomain/pom.xmleditear/pom.xmledittests/pom.xmlgithttp://sing.ei.uvigo.es/dt/jenkins/user/43324098+sad878743324098+sad8787http://sing.ei.uvigo.es/dt/jenkins/user/devpabloggdevpablogghttp://sing.ei.uvigo.es/dt/jenkins/user/mrjatoMiguel Reboiro-Jato3.6.3