No maven repository! about gelfj HOT 20 CLOSED

Unnecessary to use GitHub as a Maven Repository when Sonatype offers free hosting for OSS projects.

Please see;
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

It would be great if gelf could be published there.

from gelfj.

Which is also preferred because it gets pushed to maven central from there.

Sent from my iPad

On Mar 30, 2012, at 12:59 AM, apalsson [email protected] wrote:

Unnecessary to use GitHub as a Maven Repository when Sonatype offers free hosting for OSS projects.

Please see;
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

It would be great if gelf could be published there.

---

Reply to this email directly or view it on GitHub:
#18 (comment)

from gelfj.

When you are planning putting gelfj on maven central? If not, it will complicate deployment for me :(

from gelfj.

+1 on using sonatype (or anything that ends up in maven central) as it makes deployment a lot easier :)

from gelfj.

+1 please consider maven central, saves having to setup another repo location

from gelfj.

I was trying to submit this oss nexus to help out but because the groupid matches graylog it needs the graylog developers go ahead. The other logback appender is under the authors own groupid.

from gelfj.

I'll take care to get this into OSS (which is synced to central).

@gilesw thanks for your efforts! That ticket does not ask for my go-ahead. Where should I give it? :)

from gelfj.

And that's why Github and opensource rocks!

Thank you gentlemen and please forgive me my laziness on this matter.

from gelfj.

Hi Lennart,

The best thing would probably be for t0xa to add the OSS requirements to his pom file:-

<scm>
    <connection>scm:git:ssh://[email protected]/t0xa/gelfj.git</connection>
    <developerConnection>scm:git:ssh://[email protected]/t0xa/gelfj.git</developerConnection>
    <url>[email protected]:t0xa/gelfj.git</url>
</scm>

<licenses>
    <license>
        <name>Personal</name>
        <url>https://github.com/t0xa/gelfj/blob/master/LICENSE</url>
        <distribution>repo</distribution>
    </license>
</licenses>

<parent>
    <groupId>org.sonatype.oss</groupId>
    <artifactId>oss-parent</artifactId>
    <version>7</version>
</parent>

Then to submit a new request to sonatype following this guide :-

https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-3.CreateaJIRAticket

With a note saying you are going to comment to allow him to deploy to that group id. Then you add a comment in jira and he should be able to deploy to your group id after updating his settings.xml file.

Someone has to be the gatekeeper for nexus releases and it should probably be t0xa, he can merge peoples improvements to his project back into his github account.

from gelfj.

I'm happy to do this. Thank you gilesw!

from gelfj.

+1 for @t0xa as gatekeeper for gelfj Nexus releases.

I'm already using OSS/Nexus for Graylog2 plugin interface releases and had no problems so far.

from gelfj.

Excited for gelfj to come to a maven repository near me!

from gelfj.

Sent renminder to Lennart.

from gelfj.

Any news on this? Meanwhile I've found this fork on maven central.

from gelfj.

@t0xa: AFAIK the Sonatype people have given you access to push to org.graylog2 - Is anything missing for you? Am I wrong?

Thanks!

from gelfj.

@lennartkoopmann: Hallo Lennart, long time no seen. They given deployed rights to @gilesw instead of me. I will reopen/create new issue on Monday, so it may require your additional approval. I've prepared everything for public repo. Thanks and sorry for being so lazy :(

from gelfj.

Thanks for the update! :)

from gelfj.

@lennartkoopmann: Issue https://issues.sonatype.org/browse/OSSRH-7084 create. Could you please approve. Thanks!

from gelfj.

Approved by @lennartkoopmann. Pushed v1.1 to central maven repo. Available immediately.

Thanks for patience.

from gelfj.

Thank you very much. ☺️

from gelfj.