I found this thread from back in June 2005 and I have the same exact
situation. I'm hoping that perhaps the answer has changed since it has
been 7 mos since this issue was brought up on the list.
From[EMAIL PROTECTED]
Subject RE: M2 - Dependent Jars for EJB
DateWed, 22 Jun 2005 12:59:39
The ear plugin does this for you.
I don't think it's part of the j2ee spec to have dependent jars
bundled inside the ejb.jar. I believe that they normally get grouped
together inside of an ear file.
You setup a seperate project with packaging of ear and add your
ejb.jar as a dependency. Your
Now that I have discovered the:
build
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
archive
manifest
addClasspathtrue/addClasspath
/manifest
/archive
/configuration
/plugin
/build
bit of configuration code, my problems seem to be resolved.
Is
Yup (well roughly) in the working with manifest document.
On 2/17/06, Wayne Fay [EMAIL PROTECTED] wrote:
Now that I have discovered the:
build
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
archive
manifest
