2010/7/9 Lee Spector <lspec...@hampshire.edu> > > On Jul 8, 2010, at 7:49 PM, Laurent PETIT wrote: > > > >> 2010/7/9 Lee Spector <lspec...@hampshire.edu> > >> > >> How is the Clojure version set in Eclipse/Counterclockwise projects? I'm > still wanting to work in 1.1.0, and while my older projects are using 1.1.0 > my newer ones -- I guess maybe this changed after upgrading to > Counterclockwise 0.0.59.RC2 -- are running with 1.2.0-master-SNAPSHOT. I > don't see where I can set this when creating a new project or how to change > it for an old project. I vaguely remember seeing a way but that may very > well have been in NetBeans, which I was experimenting with a little earlier. > I imagine I could manually copy files around to make this work, but there > ought to be a better way, at least when creating a new project. > > > > Hi, > > > > Again, the answer is: it works with out-of-the-box Eclipse options: a > clojure project is a java project. With additional goodies, but still a java > project. So clojure, clojure-contrib etc. are viewed as java dependencies > for the project. How do you change this ? In your project, go to Project > > Properties > Java Build Path > Libraries . In this form, you can manage the > dependencies of your project. That is you can remove the dependencies that > have been installed by default by CCW, and point to other clojure, > clojure-contrib of your choice (currently you must have not only clojure, > but also clojure-contrib in your dependencies/classpath. This will disappear > with the next release, as forcing every project to depend on clojure-contrib > is too high a barrier). > > Given that it works this way the default dependencies should be for the > current stable versions of the libraries, which would be Clojure 1.1. > Newcomers (like me) shouldn't be given 1.2 snapshots by default. >
It is that way because of lack of coding time. The existing feature does not lead to a blocking state for the user. That's all. That said, I agree with your expectations ! > > Although I don't know what's involved in modifying the "new project" > wizard, I think it would be much better to add something there that allows > selection among Clojure versions than to force users to create a project > with the wrong version and then go and delete the libraries, independently > find the versions they want elsewhere on the web, download them separately, > put them in the right place, make the project point to them, etc. One of the > main reasons I'm working with Eclipse/Counterclockwise in the first place is > the relative ease of starting from nothing, downloading & installing, and > beginning to write and run Clojure programs. I didn't have to > find/download/install/configure anything else, and that was crucial. If I'll > have to jump through those kinds of hoops anyway, just to use the right > version of Clojure, then it's considerably less appealing for my purposes. > Even though I now appreciate that Counterclockwise has several other very > nice features the ease of getting started is one of my top priorities. > I understand, and this is one of the purposes of ccw, of course. I'll place this issue high in the todo-list (because adding powerful feature if no user is there to use them would make no sense :-) ) > > Following your instructions I was able to modify a new (1.2 snapshot) > project to use 1.1.0 but it required several steps: removing the > dependencies, then also deleting the jars from the project in the Package > Explorer, then copying the 1.1.0 jars from an older project into the newer > one (and I was only able to do this because I had an old project that I > created before 1.2 snapshot was the default -- if my students start from > scratch they'll have to find the 1.1.0 jars elsewhere and put them in the > right places via the OS, not in the Package Explorer), then go back into the > Project > Properties > Java Build Path > Libraries dialog to add the new > dependencies. This is quite a lot to add to the process every time I want to > create a new project, and for newbies there will be many steps at which > something can go wrong. (Update: I found a slightly shorter way but it also > relies on having an old project around and also seems to require a > "Clean"... still not nearly as good as being able to create the project with > the right Clojure version in the first place.) > Understood. BTW I would also personally very much like contrib also to always be > available without having to do any other downloading or configuration. > Yes, having contrib pre-installed as well as clojure will stay a possibility. What will differ is that currently it is *required* because the launched REPL uses clojure.contrib.repl_ln. I intend to make this requirement *vanish* for people that do not want contrib. Cheers, -- Laurent -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
