Hi Luciano, There was no pom in the contrib/ folder as well (I've committed it at that time) so the only way to have it working without copying poms was either setting the parent to ../../trunk/modules/pom.xml or not using a parent which wouldn't bring some tuscany dependencies.
Before making the changes, I've checked the other modules found in contrib/modules and found out that they also have the parent set to ../pom.xml so this workaround fixes the build problem on the other modules too. I agree that duplicating poms from trunk is probably not the nicest solution but otherwise we'll need to modify all the other poms in each module. Changing the poms from contrib/ and contrib/modules not to define any child modules like in trunk seems like a clean solution for now. Any other ideas? It is possible to somehow import the poms from trunk so that when global changes are made, they won't have to be made in both trunk and contrib? Regarding the binding, I've just fixed the last issues and details so if that's ok with everybody I can proceed moving it to trunk these days. Will it enter the 2.0 release or are there any further steps needed? Florian
