leiningen
leiningen copied to clipboard
Moved to Codeberg; this is a convenience mirror
My immediate use-case for this feature is to be able to automatically activate different profiles depending on which OS lein is running. I opted for a more general solution so...
This is effectively the Windows version of #1996. It would require familiarity with shell and batch scripting, but you don't have to know the deep internals of Leiningen to solve...
I believe there's no way to get help for a task once you've aliased its name. This could be considered bad practice but it's also quite useful. Could there be...
It could be helpful for users to have a `--dry-run` command they can pass when calling the `release` and `deploy` commands. This would show exactly what would happen before it...
With the pull request #2174 we're not far away from replacing the batch script with powershell. This will require some investigation to keep the usability good (or at least alright):...
I'm currently working on a few projects that utilize [weavejester/codox](https://github.com/weavejester/codox), where I want to have the documentation generation part of the release process when I use `lein release`. I can...
What if we could provide some sort of verbose option that allowed users to see every task and alias invocation, along with the profiles active at the time?
I am recommending that you update the installation instructions to add PowerShell 4 as a requirement for Windows installations. Trying to run the PowerShell script on Windows 7, I received...
`lein self-install` throw unexpected PowerShell message on Windows 10. Despite this, installation process is correct. Lein download leiningen-2.5.3-standalone.jar and seems to works properly, only the output is misleading. ``` C:\Users\Kros>lein...
Currently self-installation produces some `curl` output noise, making a no-op command to cause self-installation to run desirable to avoid this cluttering up later commands; however, `lein self-install` issues a deprecation...