Add to Maven repo

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to use Warp in a Maven project
2. No warp artifacts in any public repo

What is the expected output? What do you see instead?

Would like to be able to add warp-persist as a Maven dependency

What version of the product are you using? On what operating system?

Maven 2.2.1, Linux, JDK 1.6.0_16

Original issue reported on code.google.com by jace...@gmail.com on 6 Oct 2009 at 9:21

[GoogleCodeExporter]

Yea Im happy to have this happen but just don't have the time nor the maven 
expertise. Do you want to 
contribute this?

Original comment by dha...@gmail.com on 7 Oct 2009 at 4:38

[GoogleCodeExporter]

Sure. I am going through something similar for my own project:
http://javabuilders.org

Once I figure it all out, I can see how hard it is for warp.
it would be much easier if your project was Mavenized as well, since then 
pushing to
a repo can be just part of the build cycle.

Original comment by jace...@gmail.com on 7 Oct 2009 at 1:50

[GoogleCodeExporter]

Oh, if you decided to go the Maven way, don't bother to even waste your time 
with the
m2eclipse plugin, it's more trouble than it's worth.

Just use raw maven commands from command line and every time you change 
dependencies
just use the "mvn eclipse:eclipse" goal to regenerate the Eclipse project for 
you (I
presume there is a similar plugin for IDEA as well).

I will save you countless hours of figuring out why m2eclipse is misbehaving :-)

Original comment by jace...@gmail.com on 7 Oct 2009 at 2:16

[GoogleCodeExporter]

you should consider using the sonatype oss nexus instance 
http://nexus.sonatype.org/oss-repository-hosting.html

further m2eclipse works just fine here, their latest release fixed quite some 
issues

Original comment by franci...@gmail.com on 7 May 2010 at 7:56