RE: Classpath in EAR's manifest?
Hallo Jörg, -Original Message- From: ext Jörg Schaible [mailto:[EMAIL PROTECTED] Can I turn that off somehow? I couldn't find an option in the documentation in http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html None of my generated EARs has a manifest that contains a Class-Path entry. So it must be something within your configuration or you provide a manually generated one. You were right. Sorry for the fuss: plugin artifactIdmaven-ear-plugin/artifactId configuration ... archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin I think this explains it :( Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Classpath in EAR's manifest?
[EMAIL PROTECTED] wrote on Friday, June 22, 2007 12:29 PM: Hallo Jörg, -Original Message- From: ext Jörg Schaible [mailto:[EMAIL PROTECTED] Can I turn that off somehow? I couldn't find an option in the documentation in http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html None of my generated EARs has a manifest that contains a Class-Path entry. So it must be something within your configuration or you provide a manually generated one. You were right. Sorry for the fuss: plugin artifactIdmaven-ear-plugin/artifactId configuration ... archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin I think this explains it :( Definitely ;-) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Classpath in EAR's manifest?
Hi, why is the classpath also generated in the EAR's manifest? It should not, the JavaEE verifier in netbeans is complaining about it: Manifest file of an EAR file should not contain Class-Path entries. Please refer to J2EE 1.4 Platform Specification Section #8.2 for further information. Manifest file of this EAR file contains [ ... ] as the Class-Path entry. Can I turn that off somehow? I couldn't find an option in the documentation in http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html Thanks, Andreas Ebbert-Karroum Senior Software Design Engineer - Nokia Siemens Networks / Operations Business Software phone: +49-211-94123928, fax: +49-211-94123838 Heltorfer Straße 1, 40472 Düsseldorf, Germany Nokia Siemens Networks GmbH Co. KG * Sitz der Gesellschaft: München / Registered office: Munich * Registergericht: München / Commercial registry: Munich, HRA 88537 * WEEE-Reg.-Nr.: DE 52984304 Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management GmbH * Geschäftsleitung / Board of Directors: Joachim Malterer, Lydia Sommer * Sitz der Gesellschaft: München / Registered office: Munich * Registergericht: München / Commercial registry: Munich, HRB 163416 This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia Siemens Networks GmbH Co. KG does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia Siemens Networks GmbH Co. KG is a German Company. Further information about the Company is available from its offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nsn.com/
RE: Classpath in EAR's manifest?
Hi Anread, -Original Message- From: andreas.ebbert-karroum Sent: Thursday, June 21, 2007 11:54 AM Subject: Classpath in EAR's manifest? Hi, why is the classpath also generated in the EAR's manifest? It should not, the JavaEE verifier in netbeans is complaining about it: Manifest file of an EAR file should not contain Class-Path entries. Please refer to J2EE 1.4 Platform Specification Section #8.2 for further information. Manifest file of this EAR file contains [ ... ] as the Class-Path entry. Can I turn that off somehow? I couldn't find an option in the documentation in http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html None of my generated EARs has a manifest that contains a Class-Path entry. So it must be something within your configuration or you provide a manually generated one. You can print the effective POM (mvn help:effective-pom) and compare the settings for the ear-plugin with my settings though: [snip] plugin artifactIdmaven-ear-plugin/artifactId version2.3/version configuration archive addMavenDescriptorfalse/addMavenDescriptor manifest addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries addDefaultImplementationEntriestrue/addDefaultImplementationEntries /manifest /archive /configuration /plugin [snip] - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
