Re: [jboss-as7-dev] modules backed by a repo part 2
Bill Burke wrote:
1) Anybody know why jboss-seam-int-jbossas is copied directly into a
bundle/ directory of its module? And doesn't use<module-def> in the
build script?
Because Seam 2 has to be bundled with the deployment the only way to
link against Seam 2 classes is to add the jar to the deployment as a
resource root (rather than as a dependency).
Stuart
2) After you'd convert all modules to reference a maven artifact,
there's still the bundles and client jars left. 28.7M. OSGi isn't
enabled by default right? So these bundles aren't needed unless you're
doing OSGi?
3) How could our OSGi bundles be supported in this maven repo model? Is
it JBoss OSGi that locates and loads the bundles?