Marcel: So you have a situation where you have a bunch of dependencies in your core EJB jar and you don't want them to leak into your EJB client jar? Something like that? Only reason why I ask is that I don't run into this problem and I'm trying to figure out why? :D!
I think the reason is that any dependencies of my EJB module goes into the EAR (/lib) with a corresponding Class-Path manifest entry which doesn't effect the EJB client jar at all. To be honest though, most of my projects have very sparse EJB client jars with not a whole lot minus some local client interfaces (and potentially a domain object or two...). -aps On 5/29/07, Marcel Schutte <[EMAIL PROTECTED]> wrote:
Hi Alexander, What I mean is that an ejb-client artifact normally has far less dependencies than the ejb artifact. A typical ejb in our case uses hibernate for its persistence, but of course an application that wants to call this ejb by using the ejb-client doesn't want this (and all transitive dependencies) on its classpath. The problem is that both are built from the same pom.xml. I am not sure whether your suggestion with scope provided and manifest configuration could solve this. I can't use scope provided because for the ejb I need the dependencies to be packaged in the containing ear. Regards, Marcel ----- Original Message ---- From: Alexander Sack <[EMAIL PROTECTED]> To: Maven Users List <[email protected]> Sent: Tuesday, May 29, 2007 4:03:51 PM Subject: Re: Some guidance using EJB client dependencies Remy and Marcel: Thanks! I saw the JIRA below and feel this is royally bad for 2.0.6. Guys, how the heck am I suppose to use Maven for projects that need to define ejb-clients? Right now I would have to write some ugly ANT code to do all the heavy lifting. When is 2.0.7 due out? I really need this fix badly. I'm getting around this in pure maven by just changing the packaging schemes which is not what I wanted architecturally (including the ejb-jar in the EAR in order to avoid classpath issues). Marcel, can you be a little bit more specific in terms of what you want out of the ejb-client dependencies functionality? I'm curious on what you mean. Are you having problems with Maven including all of the dependencies in your ejb-client jar instead of subset? Why not just specify in the project that some of those are scope provided and then use the manifest configuration stuff to specify an exact Class-Path, etc.? Again, just curious.... Thanks! -aps On 5/29/07, Rémy Sanlaville <[EMAIL PROTECTED]> wrote: > > Hi, > > I think it's related to http://jira.codehaus.org/browse/MNG-2921 > > Rémy > -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson ____________________________________________________________________________________Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
