aspose file tools*
The moose likes Websphere and the fly likes How to set conflicting MANIFEST jar name Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "How to set conflicting MANIFEST jar name" Watch "How to set conflicting MANIFEST jar name" New topic
Author

How to set conflicting MANIFEST jar name

Marc Gagnon
Greenhorn

Joined: Dec 17, 2004
Posts: 6

Hi,

I am using WSAD 5.1.0 and I would like to clarify how to set classpath in manifest.

In my dynamic web project, I want to use XStream which uses among other jars the xalan-2.4.1.jar and xercesImpl-2.4.0.jar (with these exact names).

In my DefaultEAR project, I copied xalan-2.4.1.jar and xercesImpl-2.4.0.jar at the root of the project.

Back in the dyn. web project, I opened the properties, go in "Java JAR Dependencies" and I can see xalan-2.4.1.jar in the available dependent JARs (which lists the content of the DefaultEAR). I mark the xalan checkbox.

So far so good.

Back in the DefaultEAR, I now see the following error message:
"IWAE0024W The Manifest Class-Path for archive xalan-2.4.1.jar contains an entry xercesImpl.jar, that is now resolvable to a file or module in the EAR: DefaultEAR".

The Xstream (or other component) is using specific names like xalan-2.4.1.jar or xercesImpl-2.4.0.jar... But xalan-2.4.1.jar itself needs xercesImpl and its MANIFEST file has an entry without a version name for this.

What should I do? Should I rename xercesImpl-2.4.0.jar --> xercesImpl.jar?

Seems like I'm loosing an important visual information.

Is there a better way to handle utility jars?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: How to set conflicting MANIFEST jar name