"[EMAIL PROTECTED]" 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.
View the original post :
ht
Am I correct in assuming that if jboss-classloading.xml is present, any osgi
manifest will be ignored?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183542#4183542
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183542
"[EMAIL PROTECTED]" 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 jbos
One more related question... when following the future library deployment model
outlined by Sacha and Adrian, are we going to fit existing JARs with
jboss-classloading.xml files, or make "wrapper" deployment units for each
library that gets deployed?
View the original post :
http://www.jboss.c
OK, so lowercase names, separated by hyphens ("-") is the convention then.
I'll update my projects to match...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183000#4183000
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&
"[EMAIL PROTECTED]" 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 s
