Provide Maven artifacts

[GoogleCodeExporter]

With the (IMHO unnecessary from looking at the source) dependency on the 
spytools library, it's not really trivial to put the client into a maven 
repository.  A large % of projects use Maven for portable builds and 
dependency management.

It would be nice to have a version of this library available in a Maven 
repository, ideally with clear and simplified dependencies.

Original issue reported on code.google.com by ryan.daum on 18 Jan 2009 at 4:25

[GoogleCodeExporter]

There's a minimal dependency on spy.jar.  I could probably just copy the code to
simplify things a bit.

Doing a maven 2 build isn't very easy, though.  I'd happily accept a 
contribution if
someone could make it work without losing main.  :)

Original comment by dsalli...@gmail.com on 20 Jan 2009 at 10:12

[GoogleCodeExporter]

I can do the Maven conversion for you. What do you mean about not losing main?

Original comment by ryan.daum on 21 Jan 2009 at 12:33

[GoogleCodeExporter]

dustinnmb:/tmp 508% java -jar memcached.jar 
spy.jar  on Mon Jan 19 11:23:00 PST 2009
Build platform:  java 1.5.0_16 from Apple Inc. on Mac OS X version 10.5.6
Tree version:  2.2-19-gdf6a205
(add -c to see the recent changelog)

-c includes the full history of the project.

It's a really good feature if, for no other reason, because it tells me exactly
where, how, and on what tree the app was built.

Original comment by dsalli...@gmail.com on 21 Jan 2009 at 5:27

[GoogleCodeExporter]

I'll have to look and see how you're doing this.  It should be possible with 
Maven.

Last time I looked at this I saw that there was a lot of work converting your 
tests
to be Maven-friendly, too.

Original comment by ryan.daum on 21 Jan 2009 at 6:29

[GoogleCodeExporter]

By the way, Maven can/will package the POM (which has version, etc. information 
in
it) inside the .jar along with the classes, effectively having the same info as 
what
you have, minus the changelog.

Original comment by ryan.daum on 21 Jan 2009 at 10:13

[GoogleCodeExporter]

What's wrong with the tests?

I'd like all that pom stuff generated straight-outta-git (git describe + git 
log).

That's how I do it now.  I don't want to think about it once it's in place.  :)

Original comment by dsalli...@gmail.com on 22 Jan 2009 at 4:46

[GoogleCodeExporter]

I just pushed a change that removes the spy.jar dependency (by copying all of 
the
parts I use into the tree).

Original comment by dsalli...@gmail.com on 27 Jan 2009 at 6:38

[GoogleCodeExporter]

The pom generated stuff can't come out of git; the pom is considered to be the 
master
of the version #, and won't take it from an external source.

It doesn't sound like you want to have Maven take over your build automation, 
since
you have your own ideas on how to do it (custom ruby scripts and the like.)

Maybe the best thing for you to do is to write a script to produce a POM from 
your
build, and publish the artifacts.  

Original comment by ryan.daum on 27 Jan 2009 at 6:39

[GoogleCodeExporter]

I don't so much have a custom ruby script as I'm just using Apache buildr to do 
the
work.  buildr is really great except for the weird dependency problems *it* has.

Original comment by dsalli...@gmail.com on 30 Jan 2009 at 8:23

[GoogleCodeExporter]

I have buildr producing poms and such.  I'll push the next release up to a 
maven repo
somewhere.

Original comment by dsalli...@gmail.com on 18 Sep 2009 at 7:49

• Changed state: Started

[GoogleCodeExporter]

As of 2.4rc1, maven 2 artifacts are available via my m2 repo (writing a wiki 
page now).

Original comment by dsalli...@gmail.com on 23 Sep 2009 at 11:05

• Changed state: Fixed

[GoogleCodeExporter]

You might be interested in this: 
http://nexus.sonatype.org/oss-repository-hosting.html

Original comment by ryan.daum on 23 Sep 2009 at 11:28