--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/O4wQ2DY34SkJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojuredev-users?hl=en.
Here we go:* source, resource, and test paths are not added to the classpath, requiring manual intervention to have a useful REPL
* Cmd-L appears to be bound to a Leiningen shortcut; that's Go To Line! :-)
* The actions in the Leiningen menu aren't great IMO; try "Update project configuration" and "Update dependencies" instead (ripped off from m2e).
* Workspace resolution. ;-)
On Apr 12, 2012, at 1:11 AM, Laurent PETIT wrote:Thx chas for the kind words.If you can make you suggestions real fast, like now, would be great since I'm beginning a work session in an hour or so.
--
2012/4/12 Chas Emerick <ch...@cemerick.com>Here we go:* source, resource, and test paths are not added to the classpath, requiring manual intervention to have a useful REPL
Due to the switch to upgrade to most recent version of leiningen-core just before releasing. They changed some keys from e.g. :source-path to :source-paths and then I delivered a buggy version.
Has been fixed in the version delivered today. (already present in the update site)
* Cmd-L appears to be bound to a Leiningen shortcut; that's Go To Line! :-)
Oh crap, I had carefully verified in the keys shortcuts in the Eclipse preferences, and it wasn't listed :-(
What about Ctrl + L as a prefix for Leiningen shortcuts instead ?
* The actions in the Leiningen menu aren't great IMO; try "Update project configuration" and "Update dependencies" instead (ripped off from m2e).
We had a discussion about that, and thought that the names from m2e weren't clear at all.
"Update dependencies": ok
"Update project configuration" : it is unclear whether this will be an append-only operation (deleting what the user may have added manually in the build path). And also, "project configuration" is pretty vague. Currently the command is just adjusting the java build path, erasing the old content.
* Workspace resolution. ;-)
"Workspace resolution" can be interpreted in a lot of ways.
I'm okay to work on the feature, I would just not end up with the wrong detail.
On Apr 12, 2012, at 4:55 AM, Laurent PETIT wrote:2012/4/12 Chas Emerick <ch...@cemerick.com>
Here we go:* source, resource, and test paths are not added to the classpath, requiring manual intervention to have a useful REPL
Due to the switch to upgrade to most recent version of leiningen-core just before releasing. They changed some keys from e.g. :source-path to :source-paths and then I delivered a buggy version.
Has been fixed in the version delivered today. (already present in the update site)
Nice, I'll go check it out.* Cmd-L appears to be bound to a Leiningen shortcut; that's Go To Line! :-)
Oh crap, I had carefully verified in the keys shortcuts in the Eclipse preferences, and it wasn't listed :-(
What about Ctrl + L as a prefix for Leiningen shortcuts instead ?That's clear from a defaults perspective. I don't know that shortcuts are desirable to begin with though. The actions are likely to be invoked quite rarely, esp. since the builder does such a good job at keeping the deps up to date when project.clj changes.Which reminds me: could the list of dependencies be sorted?
* The actions in the Leiningen menu aren't great IMO; try "Update project configuration" and "Update dependencies" instead (ripped off from m2e).
We had a discussion about that, and thought that the names from m2e weren't clear at all.
"Update dependencies": ok
"Update project configuration" : it is unclear whether this will be an append-only operation (deleting what the user may have added manually in the build path). And also, "project configuration" is pretty vague. Currently the command is just adjusting the java build path, erasing the old content.
"Reset project configuration", then. Yes, it's only touching the build path right now…but that will change, and the build path is probably the most important part of project configuration anyway.
* Workspace resolution. ;-)
"Workspace resolution" can be interpreted in a lot of ways.
I'm okay to work on the feature, I would just not end up with the wrong detail.Right, I promised a better description earlier.Assume project A has a transitive dependency on library X. If an open project B has the same maven/lein coordinates as library X, then project B's contribution should be added to project A *instead of* a reference to library X's artifact(s).
- Chas
One of the new features in Leiningen 2 is support for native libraries. For instance, Quil 1.0.0 uses Lein to download the native dependencies.
These are nicely shown in CCW with lein support in the Package Explorer > Leiningen Dependencies > expand jar > native folder, as well as the subfolder /native/OS/. However, they are not included in the library path of the project.
I was used to open the jar properties and set the native library path there, but these settings are locked (and rightly so) and can only be changed by changes to the project.clj. Trying results in the message "Leiningen Managed Dependencies. Reflects Leiningen Dependencies declared in project.clj.
As a workaround, one can open the Project properties > Java Build Path > Libraries > Leiningen Dependencies > Native Library Location > Edit > Workspace and browse to the native directory.
I'm posting this both to document the workaround as well as ask the obvious: Will the native library support of Lein 2 be included in CCW lein support ?
By the way, not nitpicking. CCW is without a doubt the best Clojure support in any Java IDE, and the first version of lein support is already more than I anticipated.
Op dinsdag 10 april 2012 23:38:12 UTC+2 schreef laurent.petit het volgende:
2012/4/9 Laurent PETIT <lauren...@gmail.com>
To post to this group, send email to clojuredev-users@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-users+unsubscribe@googlegroups.com.
One of the new features in Leiningen 2 is support for native libraries. For instance, Quil 1.0.0 uses Lein to download the native dependencies.
These are nicely shown in CCW with lein support in the Package Explorer > Leiningen Dependencies > expand jar > native folder, as well as the subfolder /native/OS/. However, they are not included in the library path of the project.
I was used to open the jar properties and set the native library path there, but these settings are locked (and rightly so) and can only be changed by changes to the project.clj. Trying results in the message "Leiningen Managed Dependencies. Reflects Leiningen Dependencies declared in project.clj.
As a workaround, one can open the Project properties > Java Build Path > Libraries > Leiningen Dependencies > Native Library Location > Edit > Workspace and browse to the native directory.
I'm posting this both to document the workaround as well as ask the obvious: Will the native library support of Lein 2 be included in CCW lein support ?
By the way, not nitpicking. CCW is without a doubt the best Clojure support in any Java IDE, and the first version of lein support is already more than I anticipated.
Op dinsdag 10 april 2012 23:38:12 UTC+2 schreef laurent.petit het volgende:
Additional info: I will be able to work on CCW in Thursday. So if I can have some feedback before, it'll be great.
2012/4/9 Laurent PETIT <lauren...@gmail.com>
To post to this group, send email to clojuredev-users@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-users+unsubscribe@googlegroups.com.
By the way, I noticed you opted for changing the classpath in the run configuration. Is that because run configurations are created dynamically, and they would work independently of the platform Eclipse is run under ?
Another option might have been to add an attribute to one or more classpath entries in the classpath file
<classpathentry kind="con" path="ccw.LEININGEN_CONTAINER"
<attribute
name="org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY"
value="native/windows/x86_64"/>
</classpathentry>
However, this would mean the .classpath file would have to be rewritten when it is loaded on a different platform ?
Op zaterdag 14 april 2012 21:30:18 UTC+2 schreef laurent.petit het volgende:
You received this message because you are subscribed to the Google Groups "counterclockwise" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-devel/-/Yt5bGIf927AJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojuredev-devel?hl=en.
* Workspace resolution. ;-)
"Workspace resolution" can be interpreted in a lot of ways.
I'm okay to work on the feature, I would just not end up with the wrong detail.Right, I promised a better description earlier.Assume project A has a transitive dependency on library X. If an open project B has the same maven/lein coordinates as library X, then project B's contribution should be added to project A *instead of* a reference to library X's artifact(s).
I agree this is a must have, working on it right now.
The algorithm will be quite as you're writing, with the additional logic as far as version handling is concerned: if A depends on library X version x.y.z, then a project in the workspace with same groupId/artifactId as X will only be used if its version is >= x.y.z
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/MwG8lmUTogoJ.
On Thursday, April 12, 2012 8:28:13 AM UTC-5, laurent.petit wrote:* Workspace resolution. ;-)
"Workspace resolution" can be interpreted in a lot of ways.
I'm okay to work on the feature, I would just not end up with the wrong detail.Right, I promised a better description earlier.Assume project A has a transitive dependency on library X. If an open project B has the same maven/lein coordinates as library X, then project B's contribution should be added to project A *instead of* a reference to library X's artifact(s).
I agree this is a must have, working on it right now.
The algorithm will be quite as you're writing, with the additional logic as far as version handling is concerned: if A depends on library X version x.y.z, then a project in the workspace with same groupId/artifactId as X will only be used if its version is >= x.y.z
Should that be a strict = instead of >=? I'm not sure what m2e does, but it seems like there might be some cases where I would want to use x.y.z (from my local repository) instead of an open project that has a version > x.y.z.What would maven do if a version > x.y.z were present in your local repository?Maybe the answer is to honor better the provided version range ?
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/MwG8lmUTogoJ.
To post to this group, send email to clojuredev-users@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-users+unsubscribe@googlegroups.com.
my :dev-dependencies don't seem to be added to build path
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/fU0zK2i3m-YJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.
How am I supposed to import the project into eclipse in the first place? Seems like I would still have to use lein-eclipse, or maven? I don't see any option under File->Import.
On Monday, April 9, 2012 1:21:55 PM UTC-4, laurent.petit wrote:Hello,
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
This is still beta quality software, but I'd like feedback before I continue adding features.
This Eclipse plugin is currently totally separate from the Counterclockwise plugin, making it easier for me to release both without interfering on each other shoes.
So, there is also a separate Software Update Site for it:
http://ccw.cgrand.net/updatesite-lein-betas
Please tell me how it does work for you!
Tip1 : after installing the plugin, Go to your project's contextual menu, and then Configure > Leiningen
Tip2 : after having installed support, there is a contextual menu entry for Leiningen for the project's root node.
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/9xp3u26EFaMJ.
I have not used Leiningen before,so I thought I would install this to find out what it's about.
Is there any documentation about this?
Your Tip1: there is only Convert to Maven Project on my project context menu.
Any advice how to get started with this?
On Monday, April 9, 2012 6:21:55 PM UTC+1, laurent.petit wrote:Hello,
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
This is still beta quality software, but I'd like feedback before I continue adding features.
This Eclipse plugin is currently totally separate from the Counterclockwise plugin, making it easier for me to release both without interfering on each other shoes.
So, there is also a separate Software Update Site for it:
http://ccw.cgrand.net/updatesite-lein-betas
Please tell me how it does work for you!
Tip1 : after installing the plugin, Go to your project's contextual menu, and then Configure > Leiningen
Tip2 : after having installed support, there is a contextual menu entry for Leiningen for the project's root node.
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/hEVq-hhms60J.
--You received this message because you are subscribed to the Google Groups "counterclockwise" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-devel/-/_TgeP5QhK64J.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojuredev-devel?hl=en.
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
On Monday, April 9, 2012 8:21:55 PM UTC+3, laurent.petit wrote:
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
this plugin adds shortcut "Update dependencies" Ctrl+L, U
which confuses with "go to line" Ctrl+U
and "run as > clojure app" shortcut Ctrl+Alt+L is not working for me
(don't know if this is related to ccw-lein, however)
--
--
zmi la
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/irW66Jb32VUJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojuredev-users?hl=en.
Hello,
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
The URL is invalid: http://ccw.cgrand.net/updatesite-lein-betas, is there a new URL?
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/XISrTGP7oAcJ.
Le 9 juin 2012 à 14:40, Benjamin Chi <bch...@gmail.com> a écrit :The URL is invalid: http://ccw.cgrand.net/updatesite-lein-betas, is there a new URL?
Yes, since a week, CCW and Lein integration updatsites have been merged. Now you can grab both, in a single operation, from http://ccw.cgrand.net/updatesite-betas/You may have to uninstall existing CCW/Lein support the first time.Cheers,Laurent
On Monday, April 9, 2012 1:21:55 PM UTC-4, laurent.petit wrote:Hello,--
I'm pleased to announce the availability of a first version of Leiningen support for Eclipse.
This is still beta quality software, but I'd like feedback before I continue adding features.
This Eclipse plugin is currently totally separate from the Counterclockwise plugin, making it easier for me to release both without interfering on each other shoes.
So, there is also a separate Software Update Site for it:
http://ccw.cgrand.net/updatesite-lein-betas
Please tell me how it does work for you!
Tip1 : after installing the plugin, Go to your project's contextual menu, and then Configure > Leiningen
Tip2 : after having installed support, there is a contextual menu entry for Leiningen for the project's root node.
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/XISrTGP7oAcJ.
To post to this group, send email to clojuredev-users@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-users+unsubscribe@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/clojuredev-users/-/Ygm4mzLzE3YJ.
To post to this group, send email to clojured...@googlegroups.com.
To unsubscribe from this group, send email to clojuredev-use...@googlegroups.com.