default "lein new" overrides lein-newnew

[sritchie]

I'm trying to instantiate a template w/ lein-newnew on Leiningen 1.7.0, but the default lein new task seems to be catching everything. Here's a test:

lein plugin install lein-newnew 0.1.2

lein templates now produces:

List of 'lein new' templates on the classpath:
default: A basic and general project layout.
plugin: A leiningen plugin project.
template: A skeleton 'lein new' template.

but running lein new template helperproject generates a new project called "helperproject" with a helper.core.clj file. I guess user level plugins are getting squashed?

[Raynes]

@technomancy Any idea? ^

[technomancy]

I can reproduce this, but I cannot understand it. The classpath clearly has lein-newnew ahead of the self-install jar.

[technomancy]

The problem is the .class files from lein's built-in task are of a newer date than the lein-newnew plugin. I don't think there's a fix for this other than a new release of lein-newnew.

[sritchie]

Would it make sense to name lein-newnew's task something other than lein new? I know it matches because this functionality will be in Leiningen 2.0, but perhaps a new release of lein-newnew with the task aliased as lein generate would prevent this from happening down the road.

[Raynes]

I'd really hate to do that. I don't want people instructing users to use 'generate' because of "some nutty bug".

[technomancy]

I wonder if I could fake out the timestamps on the .class files for future leiningen releases to be artificially old. This is normally a good feature of Clojure.