We should definitely get the dependency info added to the pom.xml.
I think the half the problem here is we don't really use Maven internally in the project (well it's not fully Mavenised), we just upload artifacts when we release, so we're not fully in tune with the Mavenesque way of doing this
Its weird. When I first started using maven i cursed it to death...Now I don't know what to do without it...
"When I first started using maven i cursed it to death...Now I don't know what to do without it..."
Same with me...
For instance, we have hornetq-int on trunk. Trunk is using maven, everything is allright.
Now I have to import it to EAP. But EAP doesn't use maven. Instead of writing a 20 lines pom.xml file, I will have to debug/install the build-tragic.
Build-magic is awesome when everything is in place... but boot strapping a new module with it is hard.