peter-lawrey / Java-Chronicle

Java Indexed Record Chronicle
1.22k stars 193 forks source link

Publish java-chronicle artifacts to Maven Central #15

Closed mingfang closed 11 years ago

peter-lawrey commented 11 years ago

That a good idea. Any idea how to do that?

mingfang commented 11 years ago

I haven't done it myself but I believe the easiest route is to use sonatype as described here http://www.sonatype.com/people/2011/10/publishing-your-artifacts-to-the-central-repository/

utsengar commented 11 years ago

+1 Would love to use java-chronicle but since its not in maven central repo, its hard to use it for a project (not a personal project) which completely relies on maven.

pathikrit commented 11 years ago

Or, atleast create a downloadable jar in the "Downloads" section of GitHub e.g https://github.com/adobe/brackets/downloads

peter-lawrey commented 11 years ago

Good suggestion. I am about to do a release 1.4 and will add it.

On 29 January 2013 23:22, Pathikrit Bhowmick notifications@github.comwrote:

Or, atleast create a downloadable jar in the "Downloads" section of GitHub e.g https://github.com/adobe/brackets/downloads

— Reply to this email directly or view it on GitHubhttps://github.com/peter-lawrey/Java-Chronicle/issues/15#issuecomment-12864818.

peter-lawrey commented 11 years ago

Version 1.4 has been released into a staging area https://oss.sonatype.org/content/repositories/central_bundles-628/ I don't know what the process is from here but I hope it will be in maven central in a day or two.

peter-lawrey commented 11 years ago

This is finally done for version 1.5 Unfortunately it meant changing the base package to match a new groupId

        <dependency>
            <groupId>com.higherfrequencytrading</groupId>
            <artifactId>chronicle</artifactId>
            <version>1.5</version>
        </dependency>
mingfang commented 11 years ago

Thank you!

Sent from my iPad

On Feb 5, 2013, at 3:23 AM, Peter Lawrey notifications@github.com wrote:

This is finally done for version 1.5 Unfortunately it meant changing the base package to match a new groupId

    <dependency>
        <groupId>com.higherfrequencytrading</groupId>
        <artifactId>chronicle</artifactId>
        <version>1.5</version>
    </dependency>

— Reply to this email directly or view it on GitHub.