Automate Clojure projects without setting your hair on fire.
Leiningen is for automating Clojure projects without setting your hair on fire.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:Dead_Mozay/leiningen && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_service | 0000000734 734 Bytes | |
_servicedata | 0000000242 242 Bytes | |
leiningen-2.9.2+20200228.ace4573e.obscpio | 0001557516 1.49 MB | |
leiningen.changes | 0000006089 5.95 KB | |
leiningen.obsinfo | 0000000117 117 Bytes | |
leiningen.spec | 0000002202 2.15 KB |
Revision 3 (latest revision is 15)
Dead Mozay (Dead_Mozay)
committed
(revision 3)
- Update to version 2.9.2+20200228.ace4573e: * Oops; forgot to bump to a snapshot after the last release. * Fix #586 for Windows as well * Bump pprint version to match Clojars, improve docs * Test multiple Java versions using workflows * CircleCI config cleanups * More tests and some refactoring * Run lein-pprint tests on Circle * Fix broken pprint plugin * Release lein-pprint 1.3.0. * Bump to Clojure 1.10.1 for Leiningen itself. * Include PGP public keys to use in tests * Revert "Deploy checksums for signatures." * Bump Pomegranate to version 1.2.0 * Revert "Pick up fix for CVE-2018-10237" * Remove mention of mailing list. * Add the exit code to the "Subprocess failed" message * Fix mistaken uses of non-side-effecting when. * Add CLI switches to control annotation behavior * Make sure release tags are annotated. * Apply explicit middleware and hooks even with disabled implicits * Fix #2571: filter the timestamp from pom.properties * Upgrade reply to 0.4.4 * Use a newer docker image. * add progress in lein release * add consistent load order for lein check * Remove duplicated test project explanation info from test projects * Overhaul project initialization * Recommend Java 8 to avoid illegal reflection. * Add FAQ entry: illegal reflective access
Comments 0