Skip to content
This repository has been archived by the owner on Oct 3, 2022. It is now read-only.

Push to Maven repository #15

Closed
sparty02 opened this issue Feb 7, 2014 · 4 comments
Closed

Push to Maven repository #15

sparty02 opened this issue Feb 7, 2014 · 4 comments

Comments

@sparty02
Copy link

sparty02 commented Feb 7, 2014

Its great that somebody picked this up and is updating it to comply with the latest version of the spec. Do you have plans to release this to a Maven repo soon (even in SNAPSHOT form)?

@alexsnaps
Copy link
Member

While there is a couple of things I'd like to address, and 107 to be final soonish, you're probably right that pushing a -SNAPSHOT, would be a neat way of getting feedback, while waiting for spec to final.
I'll see what can be done.

@sparty02
Copy link
Author

sparty02 commented Feb 7, 2014

Thanks! I appreciate the quick response in trying to get this pushed out. I agree that it can help drive adoption and assist in evolving the implementation if need be. Great work so far!

ljacomet added a commit to ljacomet/ehcache-jcache that referenced this issue Feb 25, 2014
 - Add missing information to poms
 - Clean up redundant information in poms
 - TCK runner
   - Fix dependency issue
   - Break pom parent link with TCK pom
   - Skip deployment
alexsnaps added a commit that referenced this issue Feb 25, 2014
Issue #15 Prepare for deployment to Sonatype OSS maven repository
@ljacomet
Copy link
Member

Ehcache JCache implementation has been published to Sonatype OSS Snapshot repository:
https://oss.sonatype.org/content/repositories/snapshots/org/ehcache/

You need to add the following repository section to you maven pom to be able to get to it:

<repository>
    <id>sonatype-nexus-snapshots</id>
    <name>Sonatype Nexus Snapshots</name>
    <url>https://oss.sonatype.org/content/repositories/snapshots</url>
    <releases>
        <enabled>false</enabled>
    </releases>
    <snapshots>
        <enabled>true</enabled>
    </snapshots>
</repository>

@alexsnaps
Copy link
Member

Closing, we'll create a new one for 1.0.0 final... as there will probably other related work to be done anyways

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants