Publish artifacts into public maven repo

[vasilievip]

http://mvnrepository.com/artifact/net.sf.jsqlparser/jsqlparser
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

Maven pom example:
https://code.google.com/p/sqlsheet/source/browse/trunk/pom.xml#229

P.S.:
https://code.google.com/p/sqlsheet/issues/detail?id=10&can=1

[wumpz]

At the moment only the described repository is supported. Are there any problems with it?

[vasilievip]

1. https://raw.github.com/wumpz/maven_repo/master/snapshots Gives 404
2. Its quite simple to add library into public repo so there is no need to support custom repo

[wumpz]

Ooops. I was using this repository a while. Maybe github has restricted its access. I will look into it.

[wumpz]

You are right, that a direct http access is not possible, but the repository itself works using maven. The developers at sourceforge, which are publishing to mvncentral I think, are discussing to merge all source stuff together. Meanwhile this fork does exist parallel and so I do not really want to interfere there.

[vasilievip]

Sorry, but artifact was published into public repo not by developers at sourceforge, but by developer who hosts sonar which configured to analyze this project. I would recommend to reopen and implement this issue.
Plus, if you take a look at last update http://sourceforge.net/p/jsqlparser/code/HEAD/tree/ you would notice that this fork is more active than original.

[wumpz]

So you did already the necessary steps?

[vasilievip]

No, my colleague published jsqlparser, but as dependency of https://code.google.com/p/sqlsheet/ and not as project from source. You may need to go over steps and publish new version by compiling from source.

[wumpz]

Ok. I will into it.

[alessiostalla]

I would be interested by this as well. Having the latest jsqlparser on Maven Central would be really nice.
FWIW, we're using JSqlParser in our product, Portofino.

[wumpz]

Meanwhile use my maven repo.

[wumpz]

This one is a fork of the original project. Are there any objections to change the groupid to "com.github.jsqlparser" instead of "net.sf.jsqlparser". This is due to existence of maven artifacts of the original project. Sure this is not actively developed, but as I said I don't want to interfere there.

[vasilievip]

Are there any objections to change the groupid to

no objections:)

[alessiostalla]

I think changing the groupid is the right thing to do, even if AFAIK the original project was never published on Maven Central by its author, it was done by some user.