If I understand you correctly, you are building ear-file and you want
to remove certain jars from that ear?
You could do that by:
<dependency>
<groupId>javax.xml.soap</group>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
<exclusions>
<exclusion>
<groupId>{groupId for jaxp-api}</groupId>
<artifactId>jaxp-api.jar</artifactId>
<version>1.4</version>
</exclusion>
</exclusions>
</dependency>
Cheers,
Per-Henrik
Don't thi
On Fri, Sep 10, 2010 at 8:57 AM, <[email protected]> wrote:
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
