"david.lloyd@jboss.com" wrote:
How are you guys naming your modules?

Dividing code into 3 pieces:
- contract; jboss-xyz-spi
- user usage; jboss-xyz-api
- impl detail; jbos-xyz-plugins

Not every sub-project has api, but we have spi and plugins for all.
We're also letting maven know about the split, hence making it possible for
super advanced users to change impl on top of spi. :-)

 

"david.lloyd@jboss.com" wrote:
are we going to fit existing JARs with jboss-classloading.xml files, or make "wrapper" deployment units for each library that gets deployed?

I had this discussion with Scott in Neuchatel a few weeks ago,
and we agreed that we should have both notions available for jboss artifacts:
- (default) jboss-classloading.xml; to have custom control == some additional features
- osgi manifest.mf

The files should be mostly build by some tool, e.g. maven or ivy,
in rare/custom cases we should provide some exception.

For the external libs, we should first look into existing repos
if they perhaps already exist in some osgi-ish form,
else think of some mechanism.
e.g. mapping module/jar name with predetermined CLMD

 

"david.lloyd@jboss.com" wrote:
Am I correct in assuming that if jboss-classloading.xml is present, any osgi manifest will be ignored?

It's all about how we write and order deployers at the end. ;-)
But yes, if you ask me, we should consider our CLMD before anything else.