The upload bundle, which is found at
http://jira.codehaus.org/browse/MAVENUPLOAD-2464, promotes Clojure as
org.clojure:clojure:1.0.0. It hasn't received any atention from the
Upload team yet, but I do hope it gets uploaded within the next
weeks. Maybe voting could speed it up...
dysinger
I signed up and voted. Only took about 30 seconds.
Thanks for the work everyone. I would love to see Clojure get into the Maven
repo.
Paul
On Tue, Jun 2, 2009 at 6:04 AM, Stefan Hübner sthueb...@googlemail.comwrote:
The upload bundle, which is found at
Christian Vest Hansen karmazi...@gmail.com writes:
On Mon, May 18, 2009 at 8:59 AM, Stefan Hübner sthueb...@googlemail.com
wrote:
I've submitted the Maven bundle for Clojure 1.0.0 to
http://jira.codehaus.org/browse/MAVENUPLOAD-2464. Processing the request
might take a couple of days.
I personally have used the -lang qualifier in my own POM work so as to
have an (unspoken) consensus with Howard's POM work.
However, I would rather clojure proper just be named
org.clojure:clojure in maven/ivy-land myself and I have heard that
from quite a few others.
On May 10, 1:17 pm,
I've submitted the Maven bundle for Clojure 1.0.0 to
http://jira.codehaus.org/browse/MAVENUPLOAD-2464. Processing the request
might take a couple of days.
Once the bundle is uploaded to Central, one of the following two
snippets can be used to declare a dependency to Clojure:
!-- Clojure with
thank you for your clarifaction! I'll prepare the bundle then.
-Stefan
Rich Hickey richhic...@gmail.com writes:
On Tue, May 12, 2009 at 5:36 PM, Laurent PETIT laurent.pe...@gmail.com
wrote:
Hello,
It seems that it's really a matter of convention, I don't see any technical
problem of
On Tue, May 12, 2009 at 5:36 PM, Laurent PETIT laurent.pe...@gmail.com wrote:
Hello,
It seems that it's really a matter of convention, I don't see any technical
problem of having a groupId of org.clojure and an artifactId of clojure.
Please let me try to summarize this never ending
On Tue, May 12, 2009 at 4:51 PM, Howard Lewis Ship hls...@gmail.com wrote:
It's the answer to why the main artifact is called clojure-lang not
just clojure. It's do differentiate Rich's framework,
clojure-lang, from the Contrib librarys (clojure-contrib) even
though they are both in the
Daniel Renfer d...@kronkltd.net writes:
On Tue, May 12, 2009 at 4:51 PM, Howard Lewis Ship hls...@gmail.com wrote:
It's the answer to why the main artifact is called clojure-lang not
just clojure. It's do differentiate Rich's framework,
clojure-lang, from the Contrib librarys
Laurent PETIT wrote:
On 8 Mai, 01:39, Laurent PETIT laurent.pe...@gmail.com wrote:
note that clojure must be compatible with JDK 1.5, so if you compile with
1.6, maybe you should verify the compatibility mode (not sure if what I
write here makes sense, I'm not a specialist in javac
I use Maven indirectly via Ivy, so I just wanted to request that,
whatever the choice of naming, the artifact and module names should
parallel. The reason for this request is that Ivy can resolve
dependencies in maven by creating URLs from a pattern. For example:
dependency org=org.clojure
It's the answer to why the main artifact is called clojure-lang not
just clojure. It's do differentiate Rich's framework,
clojure-lang, from the Contrib librarys (clojure-contrib) even
though they are both in the same Maven group.
On Sun, May 10, 2009 at 8:36 AM, Phil Hagelberg p...@hagelb.org
Hello,
It seems that it's really a matter of convention, I don't see any technical
problem of having a groupId of org.clojure and an artifactId of clojure.
Please let me try to summarize this never ending discussion:
Currently the master build script is ant's build.xml.
It generates clojure.jar
Hi Alex,
ataggart alex.tagg...@gmail.com writes:
I use Maven indirectly via Ivy, so I just wanted to request that,
whatever the choice of naming, the artifact and module names should
parallel. The reason for this request is that Ivy can resolve
dependencies in maven by creating URLs from a
Hello Laurent,
thanks for the summary! I'm looking forward to the decision and hope, we
can move forward soon.
-Stefan
Laurent PETIT laurent.pe...@gmail.com writes:
Hello,
It seems that it's really a matter of convention, I don't see any technical
problem
of having a groupId of
On 10 Mai, 22:17, d...@kronkltd.net (Daniel E. Renfer) wrote:
Phil Hagelberg p...@hagelb.org writes:
Howard Lewis Ship hls...@gmail.com writes:
clojure-lang because there will be a clojure-contrib artifact for the
same group.
And this is ... a bad thing? I'm lost.
-Phil
Good, at
Howard Lewis Ship hls...@gmail.com writes:
clojure-lang because there will be a clojure-contrib artifact for the
same group.
And this is ... a bad thing? I'm lost.
-Phil
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Phil Hagelberg p...@hagelb.org writes:
Howard Lewis Ship hls...@gmail.com writes:
clojure-lang because there will be a clojure-contrib artifact for the
same group.
And this is ... a bad thing? I'm lost.
-Phil
Good, at least I'm not the only one.
Why can't we have both clojure and
On 9 Mai, 17:08, Howard Lewis Ship hls...@gmail.com wrote:
clojure-lang because there will be a clojure-contrib artifact for the
same group.
It didn't occur to me yet, that having clojure-contrib in the same
group would render org.clojure:clojure a bad choice as
groupId:artifactId for clojure
On 8 Mai, 01:39, Laurent PETIT laurent.pe...@gmail.com wrote:
note that clojure must be compatible with JDK 1.5, so if you compile with
1.6, maybe you should verify the compatibility mode (not sure if what I
write here makes sense, I'm not a specialist in javac retrocompatibility
concerns).
2009/5/9 Stefan Hübner sthueb...@googlemail.com
On 8 Mai, 01:39, Laurent PETIT laurent.pe...@gmail.com wrote:
note that clojure must be compatible with JDK 1.5, so if you compile with
1.6, maybe you should verify the compatibility mode (not sure if what I
write here makes sense, I'm not a
2009/5/10 Laurent PETIT laurent.pe...@gmail.com
2009/5/9 Stefan Hübner sthueb...@googlemail.com
On 8 Mai, 01:39, Laurent PETIT laurent.pe...@gmail.com wrote:
note that clojure must be compatible with JDK 1.5, so if you compile
with
1.6, maybe you should verify the compatibility mode (not
Laurent PETIT laurent.pe...@gmail.com writes:
I also think it makes sense to deposit the whole battery :
clojureXX.jar
clojure-slimXX.jar
OK, I would bundle clojure-slim.jar too. I'm not familiar with it, though
curious. Would you enlighten me by throwing some light on it's purpose?
2009/5/7 Stefan Hübner sthueb...@googlemail.com:
Laurent PETIT laurent.pe...@gmail.com writes:
I also think it makes sense to deposit the whole battery :
clojureXX.jar
clojure-slimXX.jar
OK, I would bundle clojure-slim.jar too. I'm not familiar with it, though
curious. Would you
OK, I've got it. Thanks, Laurent!
I would bundle clojure-slim.jar as a classified clojure, like Maven
calls it. So the final filename would be clojure-lang-1.0.0-slim.jar.
To use this one instead of clojure-lang-1.0.0.jar, the following
dependency needs to be declared:
dependency
Seems fine to me.
One question, though: I see that you want to name the artifact
clojure-lang and not just clojure.
Why not just clojure as is the case for the ant build script ?
I guess this could just confuse people ?
2009/5/7 Stefan Hübner sthueb...@googlemail.com:
OK, I've got it.
Laurent PETIT laurent.pe...@gmail.com writes:
Seems fine to me.
One question, though: I see that you want to name the artifact
clojure-lang and not just clojure.
Why not just clojure as is the case for the ant build script ?
I guess this could just confuse people ?
Very good point!
2009/5/7 Stefan Hübner sthueb...@googlemail.com:
Laurent PETIT laurent.pe...@gmail.com writes:
Seems fine to me.
One question, though: I see that you want to name the artifact
clojure-lang and not just clojure.
Why not just clojure as is the case for the ant build script ?
I guess this
I guess only Rich can make the choice: statu quo, clojure (breaks
maven artifact id), clojure-lang (breaks build.xml).
Not that I have a strong stake in this, but I'd vote for going with
clojure and getting it right for 1.0.
- J.
--~--~-~--~~~---~--~~
You
Laurent PETIT laurent.pe...@gmail.com writes:
You're right, so from the beginning the ant script creates
clojure... while the maven script creates clojure-lang
To be precise here, there's no such maven script that creates
clojure-lang, neither does Maven do anything during Clojure's build
2009/5/7 Stefan Hübner sthueb...@googlemail.com:
Laurent PETIT laurent.pe...@gmail.com writes:
You're right, so from the beginning the ant script creates
clojure... while the maven script creates clojure-lang
To be precise here, there's no such maven script that creates
clojure-lang,
On Thu, May 7, 2009 at 4:47 PM, J. McConnell jdo...@gmail.com wrote:
I guess only Rich can make the choice: statu quo, clojure (breaks
maven artifact id), clojure-lang (breaks build.xml).
Not that I have a strong stake in this, but I'd vote for going with
clojure and getting it right for
Christian Vest Hansen karmazi...@gmail.com writes:
On Thu, May 7, 2009 at 4:47 PM, J. McConnell jdo...@gmail.com wrote:
I guess only Rich can make the choice: statu quo, clojure (breaks
maven artifact id), clojure-lang (breaks build.xml).
Not that I have a strong stake in this, but I'd
Laurent PETIT laurent.pe...@gmail.com writes:
I also think it makes sense to deposit the whole battery :
clojureXX.jar
clojure-slimXX.jar
clojure-sourcesXX.jar
Since clojure-slim is not bundled in the distributed ZIP for 1.0.0, I'm
going the build all three libraries from SVN tag 1.0
2009/5/8 Stefan Hübner sthueb...@googlemail.com
Laurent PETIT laurent.pe...@gmail.com writes:
I also think it makes sense to deposit the whole battery :
clojureXX.jar
clojure-slimXX.jar
clojure-sourcesXX.jar
Since clojure-slim is not bundled in the distributed ZIP for 1.0.0, I'm
Hi all,
Since Clojure now has a stable 1.0.0 I would like to take a step
forward and push it to Maven's Central Repo at http://repo1.maven.org/maven2/.
This would allow people using Maven to integrate Clojure more easily,
since no 3rd party repo wouldn't be involved anymore.
I'm going to follow
If you do push clojure-1.0.0.jar, please also add the sources jar;
it's especially annoying when one has to set up sources jars manually
(in intellij or whatever) by manually downloading the source and
depositing it somewhere safe on the filesystem when maven could be
doing it for me.
Thanks!
I also think it makes sense to deposit the whole battery :
clojureXX.jar
clojure-slimXX.jar
clojure-sourcesXX.jar
2009/5/7 Josh Daghlian daghl...@gmail.com:
If you do push clojure-1.0.0.jar, please also add the sources jar;
it's especially annoying when one has to set up sources jars manually
38 matches
Mail list logo
