Hi all, in my Magma Apache Lab I'm building some Maven archetypes during the main build process, and everything is working fine. Anyway, from time to time, an archetype stops working properly due to a refactoring, like a class or package name change, or some other similar event.
What I'd like to do is to test these archetypes during the build process. The first and easier test would be to actually use them to create a mock project and see it build properly, even eventually testing itself and propagating the failure to the main build process. I found in this mailing list only one thread dealing with archetype testing, and it was invoking another mvn command, on a temporary directory i suppose. Also, they were suggesting to use the Shitty plugin, which actually builds some other projects to run integration tests. I think a possible solution could be to use the maven-embedder called from a Junit test. This would give all the flexibility to run even more than one build cycle (for example with different parameters) and/or to perform more checks after the project has been created or built. What I'd like to know from you all is : - have you found any other nice way of testing an archetype? - is there an interest in this or am I the only paranoid searching for such a solution? :D - would it make sense to you to make at least the "build-it test" the default test phase during archetype build? (I'm planning a contribution here :) ) Let me know what you think about it. Simone -- Simone Gianni CEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
