Hi, Once again I need your advices and support for a problem I'm locked in :) This time it relates to transtitive dependencies in an EJB+CLIENT+EAR context.
I have 3 projects: - Project A --> EJB JAR project which generates 2 artifacts : the ejb JAR and the ejb-client JAR - Project B --> EAR project which depends on ProjectA : it simply creates the EAR for Project A - Project C --> simple JAR client which depends on Project A's ejb-client JAR Ok, pretty classical case. Now, my EJB project (A) has many dependencies: on the spring, hibernate and other libs. I don't want my client (C) to depend on these libraries because of transitive dependencies. Thus I have put these dependencies as <optional> in my EJB project (A). The problem is: because of that, my EAR project (B) does not bundle these libraries in my ear artifcat anymore which results in an incomplete EAR file !! What are the solution(s) for such a problem ? I can 'duplicate' my dependencies in the EAR project (B) ==> heavy to maintain: each time I add a library I have to add the dependency in A and B. Is there any 'clean' solution to this issue ? (I want the libs in my EJB project, in my EAR but not in my client) Thanks in advance. Greets, Ozeebee. -- View this message in context: http://www.nabble.com/-M2--EJB-JAR-%2B-client-JAR-%2B-EAR-transitive-dependencies-problem-t1760618.html#a4789568 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
