-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic clean
before deploy
can break Cljx lib releases
#1586
Comments
The best way to handle this would be to include whatever's writing to |
Great, thanks Phil! Appreciate the quick response - cheers :-) |
Unfortunately this is not only about Maybe just excluding |
AFAICT, just using What am I doing wrong here? Reopening so that the thread isn't lost. Meta: it again seems like the challenges posed by AOT are forcing those of us not using AOT to babysit our builds to restore basic behaviour (in this case "stuff that's in |
Had to revert previously removed prep-tasks. See technomancy/leiningen#1586 for more.
Hi there!
v2.4.0 introduced the following change:
Automatically clean before deploy to avoid AOT in libraries. (Phil Hagelberg)
. Not sure if this was discussed somewhere - struggling to find the relevant issue?Anyway, this change can break libraries that use Cljx transforms that output to a clean target path (handy, quite common, and currently recommended by the Cljx docs).
Is this something that was considered? Is there a recommended workaround? Is there a way to disable the new [auto cleaning] behaviour?
Thanks a lot, cheers! :-)
UPDATE: Found the original issue motivating this change: #1512
UPDATE 2: Okay, found the
:auto-clean false
project.clj option. Will keep digging to understand this better.The text was updated successfully, but these errors were encountered: