Not clear at all. Sorry. Was probably doing something else ;-) In order to avoid each openejb module depends on geronimo-specs-*, we have a the javaee-api module aggregating all spec jars.
But instead of using javaee-api, some modules depends on geronimo-specs-* jars. As a result, when building openejb.war application, we get both: javaee-api and spec jars. So, if an openejb module (lets say openejb-cxf) needs an API (jaxws), do I have to add the API to javaee-api and depend on it? Or can i just add the API to the openejb module? Jean-Louis Jacek Laskowski wrote: > > On Tue, Apr 27, 2010 at 5:29 PM, Jean-Louis MONTEIRO > <[email protected]> wrote: > >> Do we need to put all our API dependencies in the javaee module? > > What does "our" point to? That's how javaee APIs are provided as a > single jar. I remember once having trouble understanding its aim, but > once I got it (see previous sentence) all is (?) clear. I think I > might not get your point. > > Jacek > > -- > Jacek Laskowski > Notatnik Projektanta Java EE - http://jaceklaskowski.pl > KapituĊa Javarsovia 2010 - http://javarsovia.pl > > -- View this message in context: http://openejb.979440.n4.nabble.com/Spec-jars-management-tp2067661p2123950.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
