Revisited: Including a Class-Path In Your MANIFEST.MF
By Olaf Heimburger-Oracle on Oct 21, 2009
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 184.108.40.206.0.
A short investigation showed that JDeveloper 220.127.116.11.0 does two things while going through the deployment process.
- It checks the correctness of the tag and its usage.
- 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: