emezeske/lein-cljsbuild

Checkouts projects without :cljsbuild causes warnings

Open

#413 opened on Sep 7, 2015

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Clojure (153 forks)batch import
BugHelp WantedSuccessful Repro

Repository metrics

Stars
 (1,096 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

When you have a ClojureScript project with a non-ClojureScript checkouts project these warnings:

WARNING: no :cljsbuild entry found in project definition.
--------------------------------------------------------------------------------
WARNING: your :cljsbuild configuration is in a deprecated format.  It has been
automatically converted it to the new format, which will be printed below.
It is recommended that you update your :cljsbuild configuration ASAP.
--------------------------------------------------------------------------------
:cljsbuild
{:builds []}
--------------------------------------------------------------------------------
See https://github.com/emezeske/lein-cljsbuild/blob/master/README.md
for details on the new format.
--------------------------------------------------------------------------------

Happens in lein-cljsbuild 1.1.0, but not 1.0.6.

Contributor guide

Research direction
Investigate the code that triggers warnings for non ClojureScript checkout projects. Look for where :cljsbuild entry is checked and modify it to skip warnings when the project does not use ClojureScript.
Tech stack
None
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
LeiningenClojure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70