Jörg Schaible wrote: > Hi folks, > > developing a new plugin I made usage of plexus-utils 1.5.1. > Unfortunately this fails when I try to run the plugin in a > real project, because some classes seem outdated (missing method in > FileUtils): > > ========= %< ============ > [FATAL ERROR] > com.elsagsolutions.buildsystem.maven2.plugin.templates.ActionM > ojo#execute() caused a linkage error > (java.lang.NoSuchMethodError) and may be out-of-date. Check the > realms: [FATAL ERROR] Plugin realm = > app0.child-container[com.elsagsolutions.buildsystem.maven2.plu > gin:es-template-maven2-plugin] > urls[0] = > file:/d:/repository/m2/com/elsagsolutions/buildsystem/maven2/p > lugin/es-template-maven2-plugin/1.0-SNAPSHOT/es-template-maven > 2-plugin-1.0-SNAPSHOT.jar urls[1] = > file:/d:/repository/m2/org/codehaus/plexus/plexus-utils/1.1/pl > exus-utils-1.1.jar [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/c:/Programme/Apache Software Foundation/Maven > 2.0.9/lib/maven-2.0.9-uber.jar > [INFO] > -------------------------------------------------------------- > ---------- > [ERROR] FATAL ERROR > [INFO] > -------------------------------------------------------------- > ---------- > [INFO] > org.codehaus.plexus.util.FileUtils.copyDirectoryStructureIfMod > ified(Ljava/io/File;Ljava/io/File;)V > ========= %< ============ > > Do I interpret this right, that I am stuck with plexus-utils > 1.1 despite the deps declared for my plugin?
Solved, the dependency was inherited transitively by maven-artifact-2.0.9. As soon as I declared plexus-utils-1.5.1 as direct dependency the newer classes have been found and the plugin worked as expected. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
