title: eclipse does not add classpath to manifest file
body: <p>I have some dependencies that I need to specify in the manifest. So I created a manifest file manually and when doing that I exported my selected files and do next >> next and then choose "use existing manifest from file". this is the manifest I have locally:</p>
  
  <pre><code>  Manifest-Version: 1.0
    Main-Class: com.placeholder.ProcessServer
    Class-Path: . ProcessServer_lib/commons-net-3.3.jar ProcessServer_lib/
    com.ibm.mq.headers.jar ProcessServer_lib/db2jcc.jar ProcessServer_lib
    /db2jcc_license_cu.jar ProcessServer_lib/db2jcc_license_cisuz.jar Pro
    cessServer_lib/com.ibm.mq.jar ProcessServer_lib/com.ibm.mq.commonserv
    ices.jar ProcessServer_lib/connector.jar ProcessServer_lib/com.ibm.mq
    .jmqi.jar ProcessServer_lib/log4j-1.2.17.jar
  </code></pre>
  
  <p>I placed the jar in my unix box and invoke it via a shell script using -jar however it gives me a  <code>classdef not found exception</code>. Upon seeing the jar generated via decomplier/zip utility I can see the manifest only contains the main-Class line not the class-path. 
  While exporting the jar should I unselect the buildpath that comes in the right hand box selection ?
  I'm doing these deployment works for the first time, but I have tried for 1 day using <code>-cp</code> to specify jar folder and main class but I still haven't found a way. Could somebody help me or give me advice?</p>
  
  <p>p.s. I don't use maven/ant so no need to advice me on that.</p>