Well, at least I know I'm not just doing something stupid...sounds like
this may be the most reasonable path for the current plugin release.
Mike
Wayne Fay wrote:
I also get the duplication of jars, but just don't care about it. ;-)
Here's my "after ear'ing is complete" layout:
ear
|
|-war
|
jar
lib-jar
ejb-jab
|
jar
lib-jar
ejb-jar
Fortunately the jars are all pretty small. This duplication of jars,
while not ideal, is not a big deal, at leat for me...
Wayne
On 2/17/06, Mike Darretta <[EMAIL PROTECTED]> wrote:
Hi Wayne.
I have the same configuration, and see identical results. My issue,
though, is that I have similar dependencies between my ejb and war
modules. As such, I end up with the following in my ear:
ear
|
|--war
|
|
jar1
jar2
|
|
ejb-jar
jar1
jar2
As you can see, my jars are replicated in both the ear's internal war
file *and* at the ear's parent directory (pulled in as transitive
dependencies for my ejb jar).
I've tried changing scope, using excludes, etc., but to no avail.
BTW, can someone verify my syntax for the excludes, or if it should have
any bearing on transitive dependencies?
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
<excludes>*.jar</excludes>
</configuration>
Can anyone help us??
Thanks,
Mike
Wayne Fay wrote:
Hi Mike,
I'm experiencing the exact same troubles. I actually just posted a
similar email to the list earlier today, though it doesn't seem to
have gotten through yet -- my first post so perhaps its moderated? Its
called "[m2] include dependent jars in Ejb-jar".
I am able to successfully deploy my EJBs after adding the following to
my EJB pom.xml:
(this assumes you are using <packaging>ejb</packaging> in the
<project> element of this pom.xml...)
<build>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ejb-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
</configuration>
</plugin>
</build>
It still does not package the shared lib jar from my project into the
ejb jar in a lib folder, but my container (oc4j) is able to figure out
what I want and deploys things successfully. Perhaps this helps?
If you figure out how to force the EJB plugin to include your
dependent jars in a lib folder, definitely respond back to the list
with details!
Wayne
On 2/17/06, Mike Darretta <[EMAIL PROTECTED]> wrote:
When I build my EJB module, the dependent jars are not included with the
EJB jar. The research I've done seems to indicate that this is the
behaviour of maven-ejb-plugin.
Is there a way to include my dependency jars with my EJB jar, which in
turn will be included in my ear file?
Thanks for your help.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mike Darretta
Computer Sciences Corporation (CSC)
Sr. Software Engineer
(o) 831.656.4324
(c) 209.814.2774
[EMAIL PROTECTED]
------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
------------------------------------------------------------
---------------------------------------------------------------------
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]
--
Mike Darretta
Computer Sciences Corporation (CSC)
Sr. Software Engineer
(o) 831.656.4324
(c) 209.814.2774
[EMAIL PROTECTED]
------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use
of e-mail for such purpose.
------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
