> way. Taking dependencies and packing them all into a single archive is > certainly doable, but when you're planning on going into an environment > like OSGi, that's a bad, bad idea. :)
I don't think Ron has literally built a single JAR with those artifacts all glommed together. Instead, he has a single Maven project (pom) that declares Hibernate, Tomcat, Spring etc as dependencies. Then he depends on THAT pom project in his own projects. That brings all those dependencies (in those specific versions) in transitively. Then he goes another step and specifies that pom as scope provided and puts all those jars in the server or lib folder of his app server. This keeps his actual project wars tiny and quick to deploy, and his various projects use the same small number of version-specific artifacts/dependencies across the board. Unsure how well this fits in with OSGi. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
