Configure you ejb plugin like this:
<build>
<plugins>
<plugin>
<artifactId>maven-ejb-plugin</artifactId>
<inherited>true</inherited>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
<generateClient>true</generateClient>
</configuration>
</plugin>
</plugins>
</build>
then in you module where you have dependency of this ejb client jar :
<dependencies>
<dependency>
<groupId>your_group_id</groupId>
<artifactId>dbserviceejb</artifactId>
<version>${version}</version>
<type>ejb-client</type>
</dependency>
</dependencies>
regards,
Markku
Markus KARG wrote:
Actually I don't want to do that but I want to know and do the
maven-ejb-plugin way.
Nevertheless,
thanks a lot!
Markus
[EMAIL PROTECTED] schrieb:
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]
