-
Notifications
You must be signed in to change notification settings - Fork 151
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
1.1.4 causes cljsbuild to sometimes compile sources in other build configs #451
Comments
I have the same issue. Current workaround is to split individual build-ids into separate lein :profiles and not expose cljsbuild to other build-ids. |
@cap10morgan @darwin I think I know which code change is responsible for this, but I don't understand yet why it's causing the mentioned behaviour. Sorry for this. Does this happen for any @darwin Would you mind sharing your build config or project for which this happens? |
@mneise I tried to prepare a branch with reproducible build, but I'm unable to reproduce it here anymore. Even going back and hard-resetting my master branch to previously failing commit does not reproduce the issue anymore. |
I have this issue also with a work repo so not something I can share without making a minimal example. I'll try. It is not consistent. Dev machines show issue with but CI server builds are fine? In our case it was pulling in a ns from "test" src folder not defined in the "release" config we were building. Even if the "test" build config was commented out. |
I've tried reproducing this but so far wasn't able to. If any of you has a project where this issue can be reproduced, please let me know 😉 |
This is enough to reproduce, just add some source to (defproject test "1.0.0-SNAPSHOT"
:dependencies [[org.clojure/clojure "1.8.0"]
[org.clojure/clojurescript "1.9.229"]]
:min-lein-version "2.0.0"
:plugins [[lein-cljsbuild "1.1.4"]]
:cljsbuild {:builds [{:source-paths ["src/cljs"]
:compiler {:output-to "resources/main_dev.js"}}
{:id "production"
:source-paths ["src/cljs"]
:compiler {:output-to "resources/main_prod.js"}}]}
:hooks [leiningen.cljsbuild]) I can reproduce it 99% of the time. |
I don't see any relevant difference between 1.1.3 and 1.1.4. Also, given that different people have problems reproducing it - maybe it's caused by some [transitive] dependency and version range? |
Figured I'd mention that I also ran into this issue very recently and as soon as I removed the
line the problem went away (luckily I didn't really need that in my project.clj anyway). Before I found out that that fixed the problem for me, I did try downgrading to 1.1.3 and the problem also went away then too. However now I have no problem with 1.1.4 and without the |
I can't consistently reproduce this (in the best way: in my dev environment I can't get it to happen ever, in my CI environment it always happens), but
lein with-profile production cljsbuild once min
theproject.clj
below sometimes tries to compile code undertest/cljs
and fails because its dependencies aren't available (specifically the ones in the:dev
leiningen profile).1.1.3 and below do not exhibit this behavior in any environment.
The text was updated successfully, but these errors were encountered: