plugin tasks doesn't honour :library-path directive (lein swank doesn't work unless swank is in lib/) about leiningen

[robwolfe]

This bug was corrected some time ago. Make sure you use the latest stable version, namely 1.1.0.

$ ls

classes project.clj README src test war

$ ls war/WEB-INF/lib/lein-swank-1.2.0-20100308.145053-1.jar

war/WEB-INF/lib/lein-swank-1.2.0-20100308.145053-1.jar

$ lein version

Leiningen 1.1.0 on Java 1.5.0_17 Java HotSpot(TM) Client VM

$ lein swank

user=> Connection opened on local port 4005

#<ServerSocket ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=4005]>

[sunkencity]

I use 1.1.0

$ lein -v
Leiningen 1.1.0 on Java 1.6.0_17 Java HotSpot(TM) 64-Bit Server VM

[sunkencity]

weird, my comment didn't show up although I posted. Here again: I do run 1.1.0

lein -v
Leiningen 1.1.0 on Java 1.6.0_17 Java HotSpot(TM) 64-Bit Server VM

[robwolfe]

You're right. I used wrong version for test (my own experiment). Leiningen can find plugins only on system class path (defined in lein script), which does not honour :library-path. I played with using Leiningen class loader for finding plugins, but so far it is not ready solution.

[technomancy]

Yeah, the only way to fix this is to use the subclassloader to find plugin tasks. I probably won't implement this myself since I can't think of a good reason to override :library-path, but I would take a patch.

[technomancy]

I think this is fixed now that lib/dev is hardcoded for plugins.

[sunkencity]

great!