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>
<artifactId>maven-ear-plugin</artifactId>
<version>2.3</version>
<configuration>
<archive>
<addMavenDescriptor>false</addMavenDescriptor>
<manifest>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
</manifest>
</archive>
</configuration>
</plugin>
[snip]
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
