Hello, just to report what I have done and what is left. I have refactored woden-api, woden-om, woden-dom and created woden-ant and woden-commons. As of yet, I have just refactored the source and not the tests. I have a little problem with the tests and need your opinion. Maven convention about test is to store the test with the Maven project. However, in our case, most of the tests are shared between woden-om and woden-dom. So the solutions presented to use are the following: 1) create a separate test folder under trunk and update woden-om and woden-dom to use this folder (like it is done today). Pros: easy to implement. Cons: does not follow Maven conventions 2) create a separate test Maven project with two profiles (om and dom) to manage the dependency for the execution. Pros: follow Maven conventions. Cons: needs to run Maven twice 3) create a separate test Maven project without profiles that will launch Maven twice (thanks to the maven-invoker-plugin http://maven.apache.org/plugins/maven-invoker-plugin) one for OM and one for DOM. Pros: follow Maven conventions. Cons: needs 3 POMs
Please let me know what is your preferred choice, mine is the third. Jeff MAURY -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
