Closed twinforces closed 11 years ago
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.
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 reply@reply.github.com 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: https://github.com/t0xa/gelfj/issues/18#issuecomment-4838044
When you are planning putting gelfj on maven central? If not, it will complicate deployment for me :(
+1 on using sonatype (or anything that ends up in maven central) as it makes deployment a lot easier :)
+1 please consider maven central, saves having to setup another repo location
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.
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? :)
And that's why Github and opensource rocks!
Thank you gentlemen and please forgive me my laziness on this matter.
Hi Lennart,
The best thing would probably be for t0xa to add the OSS requirements to his pom file:-
<scm>
<connection>scm:git:ssh://git@github.com/t0xa/gelfj.git</connection>
<developerConnection>scm:git:ssh://git@github.com/t0xa/gelfj.git</developerConnection>
<url>git@github.com: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 :-
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.
I'm happy to do this. Thank you gilesw!
+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.
Excited for gelfj to come to a maven repository near me!
Sent renminder to Lennart.
@t0xa: AFAIK the Sonatype people have given you access to push to org.graylog2 - Is anything missing for you? Am I wrong?
Thanks!
@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 :(
Thanks for the update! :)
@lennartkoopmann: Issue https://issues.sonatype.org/browse/OSSRH-7084 create. Could you please approve. Thanks!
Approved by @lennartkoopmann. Pushed v1.1 to central maven repo. Available immediately.
Thanks for patience.
Thank you very much. :relaxed:
Instructions on using github to provide a maven repository for your project here:
http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/