Re: clojars question

2011-09-21 Thread Mark Rathwell
Anyone can create their own account on clojars and publish their own
forks to their own group name.  There are 22 forks of enlive on
github, the original is by Chrisotphe Grand [1], [2].  His most recent
version published to clojars is 1.0.0.  Generally, people try not to
publish their own forks to clojars unless they have good reason (e.g.
the original is no longer maintained, or will not accept desired
patches, or doesn't publish quickly enough, etc.).

Unless there is something in one of the forked versions that you want,
I would use the original: [enlive 1.0.0].  You may, however, want to
post to the enlive group [3] to see if maybe there is a reason to use
one of the other versions.

[1] https://github.com/cgrand/enlive
[2] http://clojars.org/enlive
[3] http://groups.google.com/group/enlive-clj


On Wed, Sep 21, 2011 at 5:12 PM,  labwor...@gmail.com wrote:
 I'm confused on what version to obtain from clojars for enlive. I see
 1.2.0-alpha1 dated yesterday but I also see 2.00 dated from August. Which
 one should I pick? are there several versions? Please enlighten me.

 --
 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

-- 
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


Re: Re: clojars question

2011-09-21 Thread labwork07

Thanks. It does get confusing some times.

On , Mark Rathwell mark.rathw...@gmail.com wrote:

Anyone can create their own account on clojars and publish their own



forks to their own group name. There are 22 forks of enlive on



github, the original is by Chrisotphe Grand [1], [2]. His most recent



version published to clojars is 1.0.0. Generally, people try not to



publish their own forks to clojars unless they have good reason (eg



the original is no longer maintained, or will not accept desired



patches, or doesn't publish quickly enough, etc.).





Unless there is something in one of the forked versions that you want,



I would use the original: [enlive 1.0.0]. You may, however, want to



post to the enlive group [3] to see if maybe there is a reason to use



one of the other versions.





[1] https://github.com/cgrand/enlive



[2] http://clojars.org/enlive



[3] http://groups.google.com/group/enlive-clj







On Wed, Sep 21, 2011 at 5:12 PM, labwor...@gmail.com wrote:



 I'm confused on what version to obtain from clojars for enlive. I see


 1.2.0-alpha1 dated yesterday but I also see 2.00 dated from August.  
Which



 one should I pick? are there several versions? Please enlighten me.







 --



 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





--



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


--
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

Re: Clojars question

2010-02-03 Thread Konrad Hinsen

On 2 Feb 2010, at 20:35, Meikel Brandmeyer wrote:

clojuresque is independent of the Clojure version used in the  
project and allows easy deployment of non-AOT'd jars to Clojars. It  
handles POM and jar generation and gives reflection warnings (if  
desired) even if not AOT'ing. But gradle might be a too heavy  
dependence. YMMV.


Gradle would be just a development dependency, right? Users of my  
library would not need to install Gradle I guess.


My main issue with Gradle is that it's yet another tool to learn :-(

PS: On Windows deployment to Clojars does not work due to scp  
trouble. Only Unix/Mac OS X supported at the moment for deployment.


My brain doesn't work with Windows either, so that doesn't matter ;-)

Konrad.

--
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


Re: Clojars question

2010-02-03 Thread Meikel Brandmeyer
Hi,

On Feb 3, 3:58 pm, Konrad Hinsen konrad.hin...@fastmail.net wrote:

 Gradle would be just a development dependency, right? Users of my  
 library would not need to install Gradle I guess.

Yes. The users of your library can use whatever they want: maven, ant
+ivy, gradle, wget, bit hand carry, ... They specify the dependency
and get your jar.

 My main issue with Gradle is that it's yet another tool to learn :-(

True. But worth it AFAICT up to now. You can easily handle multiple
projects with a single build.gradle, if you like, minimising
boilerplate as much as possible. It is sufficiently flexible to do
custom stuff without losing too much hair.

With clojuresque there also some rough edges left. So it's by no way
perfect, but does a pretty good job on the standard project.

Sincerely
Meikel

-- 
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


Re: Clojars question

2010-02-03 Thread Shawn Hoover
On Tue, Feb 2, 2010 at 2:35 PM, Meikel Brandmeyer m...@kotka.de wrote:

 PS: On Windows deployment to Clojars does not work due to scp trouble. Only
 Unix/Mac OS X supported at the moment for deployment.


If that's a blocker for anyone on Windows, they should parameterize the
Clojars scp program and set it to pscp.exe from the Putty folks. It's a
champ.

-- 
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

Re: Clojars question

2010-02-03 Thread Konrad Hinsen

On 2 Feb 2010, at 21:52, Alex Osborne wrote:


Sure, you can just write the POM by hand.  The reason the POM is
necessary is so clojars knows the groupId, artifacId, version and
description of your lib.  So just create the jar however you want (eg
just use the 'jar' command-line tool).  Then create a pom.xml file  
with

a text editor.


Thanks, that looks refreshingly simple!  :-)


tried it).  However if your lib depends on nothing but clojure.core,
then you may as well leave off dependency section entirely, as anyone
consuming it is going to specify which version of Clojure they want.


Indeed. Except that I just figured out that it does require Clojure  
1.2 after all...


Konrad.

--
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


Re: Clojars question

2010-02-03 Thread Laurent PETIT
And it's also standard in maven to have the final artifact (e.g. a jar) be
self-documented by having pom.xml and pom.properties in the META-INF
directory of the jar :

META-INF/maven/groupId/artifactId/pom.xml
META-INF/maven/groupId/artifactId/pom.properties

Not sure if clojars can be fed by simply providing a jar providing
self-describing metadata yet, though.

2010/2/3 Konrad Hinsen konrad.hin...@fastmail.net

 On 2 Feb 2010, at 21:52, Alex Osborne wrote:

  Sure, you can just write the POM by hand.  The reason the POM is
 necessary is so clojars knows the groupId, artifacId, version and
 description of your lib.  So just create the jar however you want (eg
 just use the 'jar' command-line tool).  Then create a pom.xml file with
 a text editor.


 Thanks, that looks refreshingly simple!  :-)


  tried it).  However if your lib depends on nothing but clojure.core,
 then you may as well leave off dependency section entirely, as anyone
 consuming it is going to specify which version of Clojure they want.


 Indeed. Except that I just figured out that it does require Clojure 1.2
 after all...

 Konrad.


 --
 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.comclojure%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/clojure?hl=en


-- 
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

Re: Clojars question

2010-02-02 Thread Alex Osborne
Hey Konrad,

Konrad Hinsen konrad.hin...@fastmail.net writes:

 I would like to deposit a small library on clojars.org. Is it possible
 to do this without using either Maven or Leiningen? Neither of these
 tools seems to be appropriate for my library.

Sure, you can just write the POM by hand.  The reason the POM is
necessary is so clojars knows the groupId, artifacId, version and
description of your lib.  So just create the jar however you want (eg
just use the 'jar' command-line tool).  Then create a pom.xml file with
a text editor.

If you have no dependencies then at the bare minimum all you need is
this:

?xml version=1.0 encoding=UTF-8?
project
  modelVersion4.0.0/modelVersion
  groupIdyourlib/groupId
  artifactIdyourlib/artifactId
  version1.0.0/version
  descriptionDoes awesome things./description
/project

Finally just upload it to clojars with scp:

scp pom.xml yourlib.jar cloj...@clojars.org:

 If my understanding of Leiningen and Maven is correct, neither one can
 handle any Clojure version as a dependency. But it seems that
 Clojars wants a pom.xml, which I don't know how to generate otherwise.

There is a syntax for specifying version ranges in dependencies:

http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges

It should work with Maven and since Leiningen uses Maven for dependency
resolution in theory it should work with Leiningen too (I haven't
tried it).  However if your lib depends on nothing but clojure.core,
then you may as well leave off dependency section entirely, as anyone
consuming it is going to specify which version of Clojure they want.

Cheers,

Alex

-- 
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