GeezerVison is showing github.com — Publish artifacts into public maven repo · Issue #8 · JSQLParser/JSqlParser
Publish artifacts into public maven repo #8Activitywumpz commented on Jun 9, 2013 At the moment only the described repository is supported. Are there any problems with it? vasilievip commented on Jun 10, 2013 wumpz commented on Jun 12, 2013 Ooops. I was using this repository a while. Maybe github has restricted its access. I will look into it. wumpz commented on Jun 12, 2013 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 commented on Jun 12, 2013 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 commented on Jul 14, 2013 So you did already the necessary steps? vasilievip commented on Jul 14, 2013 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 commented on Jul 14, 2013 alessiostalla commented on Sep 13, 2013 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 commented on Sep 13, 2013 Meanwhile use my maven repo. wumpz commented on Sep 16, 2013 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 commented on Sep 16, 2013
Are there any objections to change the groupid to
no objections:) alessiostalla commented on Sep 16, 2013 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. wumpz commented on Sep 17, 2013 So be it. Sonatype already aprooved the project. I need some time to polish the deployment. wumpz commented on Sep 17, 2013 0.8.5-SNAPSHOT successfully deployed at sonatype. Configuration details at the readme. alessiostalla commented on Sep 24, 2013 Thanks! Do you plan to release non-snapshot versions as well? Sonatype can automatically push those to Central, if you tell it to. IIRC you have to do some manual configuration the first time, but for subsequent releases it's fully automatic. wumpz commented on Sep 24, 2013 I know. I wanted to put some more features into 0.8.5 release. But it seems to take longer than I thought.
So release versions are going to sonatype as well and should be automatically published to maven central. Thats the plan. wumpz commented on Oct 6, 2013 So finally it should be there. Sorry about taking so much time. The release is done at sonatype and should now be synched to maven central. The first version is 0.8.5. I skipped all planned additions for this release and moved them to the next one. vasilievip commented on Oct 25, 2013 alessiostalla commented on Oct 25, 2013 vasilievip commented on Oct 25, 2013 added a commit that references this issue on Jun 15, 2023This issue will close once commit a815f5f is merged into the 'master' branch.a815f5f
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|