I suspect that you will have deployment issues if the EJB module does not have visibility of the interface classes.
You should perhaps be placing this jar in the EAR/lib directory (assuming a JEE5+ compliant container) and sharing it between the RAR and EJB jar. On 22/02/2012, at 5:13 AM, Markus Karg wrote: > I have set up a typical EAR scenario, where a EJB module and a RAR > module are packaged into a EAR module (using the respective package > types of ear, ejb and rar). To be able to compile the EJB module, I have > to make it dependend of the interface JAR (which is later packed into > the RAR) with compile scope. But, this leads to the fact that the EAR > later contains not only the EJB and the RAR, but also the interface JAR. > As the interface JAR already is contained in the RAR, this is redundant. > What is "The Maven Way" to prevent this redundance, so the EAR will not > contain the additional interface JAR? > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
