Well, I think it not a good idea to upload the stack trace for clojure- dev in clojure's google group files.
The files section is dedicated to sharing usable working clojure code with others. At least it is the way I understand it. For debugging session, we could indeed do it in the more dedicated "clojure-dev user" ml. And maybe just a single message when the debugging session is over, in order for the others to know that you finally succeeded with clojure-dev ! :-) -- Laurent On Jan 18, 9:57 pm, "T. Ettinger" <tommy.ettin...@gmail.com> wrote: > I just installed via the update site, and I got (almost) the same bug, > in the same place, upon the same action. "The selected wizard could > not be started. > Plug-in clojuredev was unable to load class > clojuredev.wizards.NewClojureProjectWizard. > An error occurred while automatically activating bundle clojuredev > (653)." > Note the error number is different. However, I can still create a > Java project, then create a new File with extension .clj . This > doesn't work either, so I will upload the errors it produces (eclipse > appears to have cut it short). If this isn't the place to upload > files (in the files section of the Clojure mailing list), then I won't > post any other clojuredev-related files outside of clojuredev-users . > I just think it is a little more convenient to have the whole > discussion on one mailing list. > > On Jan 18, 12:11 pm, lpetit <laurent.pe...@gmail.com> wrote: > > > Hello, > > > Welcome, second external user of clojure-dev ! :-). > > > You will find clojure-dev developers in this mailing list. And, if > > others think the discussions become too clojure-dev centric, we can > > still continue this on the user group for clojure-dev. > > > First of all, let me say there's an update site for what is considered > > the less buggy version, and I try to maintain this update site as soon > > as new functionalities are out : "Release early, release often !" :-) > > > The URL for the update site > > :http://clojure-dev.googlecode.com/svn/updatesite/ > > > It could be interesting that you test clojure-dev first via the update > > site, because it can help detect installation problems. > > The update site is hosted directly in clojure-dev svn repo, since > > there seems to be no possibility to host a static (unversioned) web > > site at google code for the moment. > > > Please note that, as you can guess from its version number (0.0.7), > > clojure-dev is still in its infancy. Nevertheless, you should be able > > to do what you described above, so please try again with the version > > packaged in the update site. > > > I have no time just right now, but in an hour or two I will make a > > summary page on the wiki concerning the current set of functionalities > > for clojure-dev. > > > Just ONE word concerning clojure-dev philosophy : we want to embrace > > the fact that clojure runs on the JVM. So we will try to use as many > > classical java mechanisms and standards as possible. > > > For example, a clojure project is really just a java project with > > library dependencies on clojure. > > - By default the clojure wizard will create a java project that will > > add an external dependency on the clojure library that is embedded > > with clojure dev. But you can remove this dependency, and replace it > > with the clojure version you want : this clojure version will then be > > the one used for launching REPL, browsing the namespace ... > > - You can also "enable clojure" on an existing java project : here > > again, the wizard will just add a dependency for you. > > > In both cases, clojure-dev will also add a clojure "nature" to your > > project, that is registering a new builder (clojure builder). This > > builder will (because right now it does nothing) build compiled > > versions of clojure namespaces, so that you can see the corresponding > > classes in normal java code for java-clojure collaboration. > > > Fiouuu, this was a long post again, > > > Regards, > > > -- > > Laurent > > > On Jan 18, 10:19 am, "T. Ettinger" <tommy.ettin...@gmail.com> wrote: > > > > I stumbled upon Clojure in a search for a scripting language for > > > the JVM that was more functional in style than the rest, and although > > > it isn't really a "scripting language," I really, really like its > > > feature set. Unfortunately, I really, really dislike emacs (every > > > option for the Mac I use is terrible), and the Vim/Gorilla thing was > > > not working, so I gave up on Clojure until I found Clojure-dev. > > > Eclipse is my favorite IDE and I am comfortable with it, so this plug- > > > in seemed great. I was considering writing my own using the amazing > > > Groovy plug-in as a base, but Clojure-dev seemed a lot easier at the > > > time. > > > I have encountered a number of problems (as is to be expected from > > > version 0.0.7). Although it took some work, with a few changes to the > > > source code, and with build order for clojure.jar having to be above > > > the JRE, which in turn had to be J2SE-1.5, I got the plug-in to build > > > without errors. However, when I ran the plug-in as part of a new > > > Eclipse window, "New Clojure Project" showed up as an option but could > > > not be started (the error is "The selected wizard could not be > > > started. > > > Plug-in clojuredev was unable to load class > > > clojuredev.wizards.NewClojureProjectWizard. > > > An error occurred while automatically activating bundle clojuredev > > > (416). > > > "). > > > Is anyone familiar enough with Eclipse or Clojure-dev to help out here? --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
