Skip to content

Support for 'Class-Path' in jar manifest #46

mlehman opened this Issue May 8, 2010 · 2 comments

2 participants

mlehman commented May 8, 2010

For some deployments, I tend to prefer not using an uberjar, but instead using a regular jar and a lib folder for dependencies. However it can be painful getting the class-path set up so setting the 'Class-Path' in the jar manifest lets it still be run with a simple "java -jar". Is this worth adding (or maybe I'm missing another easier way)?

Here's a rough but working example in 'make-manifest':


Clean up make-manifest. Closed by 0966229.


Oops; didn't realize you had a fix for this already. Could you send it as a pull request in the future?

@robwolfe robwolfe pushed a commit to robwolfe/leiningen that referenced this issue Aug 20, 2011
@technomancy Clean up make-manifest. Fixes #46. 0966229
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.