Hi, you don't usually depend on EJBs in your WARs. You should depend on ejb- client. IIRC you'll have to explicitely configure your EJB project to create an ejb-client artifact.
I just tried that though, and the ejb-client JAR is still kept inside the WAR. Are you planning to deploy your WAR files also in a servlet container? Because if not, you could mark the ejb/ejb-client dependency as provided. That's how we solved that. Stefan ------------------------------------- On Thursday 17 November 2016 15:07:31 Stefan Seidel wrote: > On 17 Nov 2016, Clemens von Musil wrote: > > We pushed a very minimal example project to a public github repo located > > here: > > > > https://github.com/kr1schan/mavenToy > > > > The project consists of an ear, two war modules, one ejb module and one > > plain jar artifact. > > Both war modules depend on the ejbmodule as well as on the jar artifact. > > SkinnyWar is enabled and configured in all conscience. > > > > After 'mvn clean package', the resulting ear shows correct handling of the > > jar dependency. > > The ejb dependency remains in both war files. > > Good to have a minimal example showing the problem! I confirm that I can > reproduce the buggy (?) behavior. > > Unfortunately I can reproduce it and can't see the error when looking > into it for 5 minutes. Don't have time for a close look right now, sorry. > > - martin
