It could be :
build
*plugins*
*plugin*
groupIdorg.apache.*maven*.*plugins*/groupId
artifactId*maven*-XXX-*plugin*/artifactId
configuration
archive
*manifest*
addClasspathfalse/addClasspath
/*manifest*
/archive
/configuration
/*plugin*
/*plugins*
/build
The XXX
Hi,
I found the an interesting thing about the problem that I reported in this
post thread. Basically, I set up my project as maven and then convert the
build EAR into eclipse projects so that I can debug my ejb and war app using
GEP (please also see my other post from
Hi bongosdude,
It looks like the war plugin is not javaee-5 aware. Anything you put
in the ear lib directory gets into the ear classloader which is a
parent to the war classloader. Thus you don't need the war manifest
classpath entries at all in an ee5 container such as geronimo. Your
David,
This is quite interesting point that you point it out. Do you know how I can
make maven stop generating the MANIFEST.MF file?
Thanks
-B
djencks wrote:
Hi bongosdude,
It looks like the war plugin is not javaee-5 aware. Anything you put
in the ear lib directory gets into the ear
On Jan 10, 2009, at 12:22 PM, bongosdude wrote:
David,
This is quite interesting point that you point it out. Do you know
how I can
make maven stop generating the MANIFEST.MF file?
I think you want maven to generate the manifest.mf file but not
include a CLASS-PATH entry. However, I
After I fixed the manifest classpath problem, maven successfully build my
project. But I still have questions about geronimo-web.xml.
Thanks
-B
Embedded error: Manifest class path entries must be a valid jar file (JAVAEE
5 Section 8.2): path= lib/callingcard-ejb-0.0.1-SNAPSHOT.jar, resolved to
The warning concerning the missing geronimo-web.xml is not related to
the INFO message about the Strict Manifest Classpath processing.
Concerning the LenientMFCP: This option was added to support archives
that don't adhere to the standard specification which requires that the
manifest
