Issue 122424 - Relative paths in MANIFEST.MF of juh-3.2.1.jar and jurt-3.2.1.jar prevent deployment on JBoss AS
Summary: Relative paths in MANIFEST.MF of juh-3.2.1.jar and jurt-3.2.1.jar prevent dep...
Status: UNCONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.4.1
Hardware: All All
: P3 Normal
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-30 08:13 UTC by Vincent Massol
Modified: 2013-05-30 08:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Vincent Massol 2013-05-30 08:13:03 UTC 
Both juh and jurt jars have relative paths in their MANIFEST.MF files:

juh-3.2.1.jar 
Manifest-Version: 1.0
Class-Path: ridl.jar jurt.jar ../../lib/ ../bin/

and

jurt-3.2.1.jar
Manifest-Version: 1.0
Class-Path: ridl.jar unoloader.jar ../../lib/ ../bin/

This is not correct since it makes these JARs not usable in environments where there's no ../../lib and ../bin/ directories...

Specifically this makes application servers that check this choke, like the JBoss AS.

For ore details see:
* https://issues.jboss.org/browse/WFLY-788
* http://jira.xwiki.org/browse/XE-1302

PS: I had to selection a version to be able to enter this bug even though I have no idea what version it corresponds to. I probably chose the wrong "product" but App Dev seemed the closest choice. Sorry about that. The version of juh/jurt is 3.2.1. Thanks