One other concern would be that in general, the EJB client generation
from the same EJB module violates Maven's principle of one artifact per
project/module.  As I understand it today, the only benefit of using it
is that it will generate a separate JAR file in the repo that can be
referenced by a client as an EJB client dependency and that you can
selectively filter out classes (bean classes, etc.) from the client jar
(but not dependencies carried over from the EJB or any of its transitive
dependencies).

-Daryl

 

-----Original Message-----
From: Markus KARG [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 14, 2006 11:51 AM
To: Maven Users List
Cc: [EMAIL PROTECTED]
Subject: Re: EJB Client JAR

Daryl,

thanks a lot for your answer once again. Indeed we managed to let the
ejb packager create the client jar and now understand why you have not
been using it. Actually it is scary to see all the Class-Path entries in
the client... Maybe we should file a feature request.

Thanks again
Markus

[EMAIL PROTECTED] wrote:
> Not necessarily the maven-ejb-plugin way, but you can create a 
> separate module for the EJB client and then add a compile dependency 
> on the that project in your EJB project's pom.  We did this to get 
> around the fact that using the generateClient option on the 
> maven-ejb-plugin generates a pom for the client with way too many 
> dependencies (includes all of the EJBs dependencies) and so that we 
> could compile the EJB in 1.5 but compile the client under 1.4.
>  
>
> -----Original Message-----
> From: Markus KARG [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 14, 2006 4:23 AM
> To: Maven Users List
> Subject: EJB Client JAR
>
> Using Maven2's ejb package, I was able to create an ejb-jar from my 
> sources.
> But not I want Maven to create an "EJB Client JAR", that only contains

> the interfaces, and make another JAR dependent of that "EJB Client
JAR"
> (by means of Class-Path: entry in MANIFEST.MF).
>
> How to do that?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to