Points taken.
After rethinking about this, thanks to your feedback, it seems indeed
really wrong to silently automatically override existing Java build paths.
I think I will confine the automatic leiningen conversion only for projects
which do not yet appear to be Java/just projects - those
What would this mean in practice for using the new drag/drop functionality to
open Clojure projects, regardless of origin or history? Would some require an
additional manual step to behave as proper Leiningen projects?
This new functionality has been making life *much* better for me and for
Hello lee,
The drag and drop of projects with a project.clj file should not be
affected :
- if the project already has eclipse metadata (that's what .project and
.classpath files are), then ccw will rely on them and not try to overwrite
them.
- if the project has no eclipse metadata (or no
Sounds great -- thanks Laurent.
-Lee
On Oct 4, 2014, at 10:24 AM, Laurent PETIT laurent.pe...@gmail.com wrote:
Hello lee,
The drag and drop of projects with a project.clj file should not be affected :
- if the project already has eclipse metadata (that's what .project and
.classpath
Counterclockwise, the Eclipse Clojure development tool.
Counterclockwise 0.28.1 has been released.
Improvement over 0.28.0 based on user feedback. Thanks to all who helped
improve Counterclockwise by their constructive comments!
- Drag Drop from Github / Bitbucket / Google Code URLs works in
