Producing + publishing maven artifacts

[GoogleCodeExporter]

Hi there guys,

Great library, very nice APIs.

I notice there is currently no Maven artifact for the library, which would make 
it much easier for many projects to use. Is this something you'd be interested 
in pursuing? I am happy to create a POM file and possibly take up organising 
publishing to the central repository through on of the open source forges, e.g. 
Sonatype (I have set this up before on my own OSS projects). 

(Sadly I won't be able to use your tool in my current project anyway, as the 
GPL license you've chosen won't let me use it -- Apache would be much more 
business-friendly, if that's a concern of yours. However I'm still happy to 
help set up + publish repos to let you distribute this more effectively)

Original issue reported on code.google.com by funk...@gmail.com on 23 Jul 2010 at 3:33

[GoogleCodeExporter]

Hi

Thanks for comments.

I have plan to support Maven aftifact to this project and appriciate any help. 
If it is not difficult, you can go ahead and create a pom file (note: you 
should check out 1.1. branch). I will publish it to repo when 1.2. release will 
be ready.

About license: I think we can go with apache license, because I am really do 
not care to much about it. 

Original comment by dm.naume...@gmail.com on 23 Jul 2010 at 5:32

[GoogleCodeExporter]

Hi there,

I've attached a POM file. I've made a few assumptions about the project which 
I'll just list here to be clear:

1) I've set the compilation target to Java 1.5 -- you use generics so this is 
obviously the minimum, can set the target to 1.6 if you prefer (see lines 40/41 
of the pom) but it compiles fine under 1.5 so probably no reason to exclude 
people using 1.5 from using the library.

2) For Maven you need a group id/project name/description, I have used 
'com.googlecode.java-diff-utils' for the groupId (this is the traditional way 
of generating a groupId for a Google Code project), 'diffutils' as the name, 
and have used the Google Code tagline ('The DiffUtils library for computing...')

3) I have kept the existing directory layout -- Maven generally recommends 
projects keep the 'standard' directory layout but as there's an ant build.xml 
there I didn't want to change that. This can happen later if you like (lines 
28-34 of the POM can be removed if this changes)

The only other possible problem is that using just 'diffutils' as the package 
name for the Java code may be frowned on by the Maven central repository 
maintainers, not sure if they expect a more traditional Java package name. I 
can check into this for you.

Very glad to see the license change, looking forward to using this at work 
already. :)

How far away do you think the 1.2 release will be? As I said I'm happy to help 
publish it to the central repo when it's ready (I have an oss.sonatype.org 
account set up)

Original comment by funk...@gmail.com on 26 Jul 2010 at 12:04

Attachments:

• pom.xml

[GoogleCodeExporter]

Thanks a lot!

1.2. is already released. I will review and maybe make changes as soon as I get 
free time for this (today-tomorrow). 

Original comment by dm.naume...@gmail.com on 26 Jul 2010 at 5:30

[GoogleCodeExporter]

Excellent... just to clarify since 1.2 is out then the version in the POM 
should change from "1.2.0-SNAPSHOT" to "1.3.0-SNAPSHOT"

Original comment by funk...@gmail.com on 26 Jul 2010 at 6:04

[GoogleCodeExporter]

A quick update - i've created a sonatype account and hope to finish all steps 
as soon as they prepare repo.

Original comment by dm.naume...@gmail.com on 1 Aug 2010 at 2:07

[GoogleCodeExporter]

Hey Dmitry,

Any update on the maven artifact publishing? Let me know if there's anything I 
can do to help.

Cheers,

Paul

Original comment by funk...@gmail.com on 24 Aug 2010 at 6:44

[GoogleCodeExporter]

Hey,

This is a really cool.

I really wish the artifact was in the maven repo.

Any progress?

Original comment by vijay...@gmail.com on 9 Sep 2010 at 9:37

[GoogleCodeExporter]

Sorry guys, but I will be not available for next Monday for sure. I will make 
it 1st priority when return.

Original comment by dm.naume...@gmail.com on 9 Sep 2010 at 9:43

[GoogleCodeExporter]

Hey,

there does not seems to be any way to access diffutils artifact through any 
well-known maven repository (and furthermore, there is absolutely no 
documentation on how to incorporate diffutils in a maven project).

So, Sonatype provides free OSS maven hosting through a dedicated nexus 
instance. If one wish to make diffutils more visible in the maven ecosystem, 
there is a complete how-to available in Sonatype wiki : 
https://docs.sonatype.org/display/repository/sonatype+oss+maven+repository+usage
+guide

I would advise you to follow these guidelines to have diffutils available with 
the maximum ease.

Original comment by nicolas.delsaux on 24 Sep 2010 at 8:06

[GoogleCodeExporter]

Thanks. I just released artifacts as described a document you provide. Waiting 
for activating a sync with a central repo. You can check status via JIRA ticket 
- 
https://issues.sonatype.org/browse/OSSRH-674?focusedCommentId=118336#action_1183
36

Original comment by dm.naume...@gmail.com on 24 Sep 2010 at 10:55

[GoogleCodeExporter]

Done. 
http://mvnrepository.com/artifact/com.googlecode.java-diff-utils/diffutils/1.2

Original comment by dm.naume...@gmail.com on 27 Sep 2010 at 12:45

• Changed state: Fixed