Hi, at first thanx to all replies until now!
Here´s some more detailed information, where the same problem has appeared: http://forums.sdn.sap.com/message.jspa?messageID=4753421 In our environment we see: com.sap.engine.services.library_container.deploy.LCDeploymentException: [ERROR CODE DPL.LIB.103] Class-path entry jaxb-api.jar specified in /usr/sap/GZG/J00/j2ee/cluster/server0/temp/deploy/kvkams-ear-SAP.ear1283962052624/lib/jaxb-impl-2.1.9.jar/META-INF/MANIFEST.MF file cannot be resolved.] Thanx, Torsten Martin Gainty <[email protected]> 10.09.2010 12:54 Bitte antworten an "Maven Users List" <[email protected]> An <[email protected]> Kopie Thema RE: Maven *.ear build for SAP Web AS can you display the error you see when Application Server encounters Version-specific jars jaxp-api-VERSION.jar jax-qname-VERSION.jar activation-VERSION.jar servlet-VERSION.jar does your filesystem accept alpha, dash and numeric characters in jar filename? gruss Martin ______________________________________________ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > To: [email protected] > Subject: Maven *.ear build for SAP Web AS > From: [email protected] > Date: Fri, 10 Sep 2010 08:57:24 +0200 > > Hi, > > actually we´re trying to get our *.ear built by Maven to be deployable und > executable on SAP Web Application Server. > > We run into problems, caused by a classpath in (for example) > > <groupId>javax.xml.soap</group> > <artifactId>saaj-api</artifactId> > <version>1.3</version> > > This jar has a MANIFEST.MF containing > > Class-Path: jaxp-api.jar jax-qname.jar activation.jar servlet.jar > > The application server is complaining about this classpath because Maven > puts the *.jars with their version names into it, > that means jaxp-api-1.4.jar (for example) > > => Is there a way to come around this? Do I have to customize all my > module filenames? > > Torsten >
