Revisited: Including a Class-Path In Your MANIFEST.MF

In January 2008 I wrote about putting additional information into your Manifest.mf (see original entry). Recently a colleague told me that this does not work as expected in JDeveloper 11.1.1.1.0.

A short investigation showed that JDeveloper 11.1.1.1.0 does two things while going through the deployment process.

  1. It checks the correctness of the tag and its usage.
  2. It expects a value in the same line as the tag.

The first is nice and necessary to avoid any surprises. The second is a bit surprising if you follow my advise in having a separate line per Class-Path element. To get it work as in the original post, you need to be sure that every multi-line tag entry must have the form <tag>: <first_value> in the first line. For example:

Class-Path: ./lib
  commons-lang.jar
  etc.

Comments:

Post a Comment:
Comments are closed for this entry.
About

This is my blog for things I found useful during my work as Senior Solution Architect for Identity Management and Service-oriented Architecture at Oracle. All text expressed on this blog is my own opinion and not related to my employer.

Search

Top Tags
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today