Thanks all for suggestions. The problem is that there is not an infinite number of phases in a standard lifecycle, and I cannot take another phase than the default one (packaging) for these. Other phases are already used for other treatments (or it would be somehow dangerous to use them for a job they should not do). And to answer Jörg, yes, for plugins executing goals at the same phase, declaration order defines the position in lifecycle. There even was an issue about this, corrected in version 2.0.5.
-----Message d'origine----- De : Adrian Gonzalez [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 octobre 2007 11:12 À : Maven Users List Objet : RE : Configuration not working for multiple calls of same plugin As Joerg says, just merging the two execution in the same executions element, and including a phase element ? <executions> <execution> <id>ear-eclipse-manifest</id> <phase>generate-resources</phase> <configuration> ... </configuration> </execution> <execution> <id>another-task</id> <phase>anotherphase-after-generateersources</phase> <configuration> ... </configuration> </execution> </executions> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
