Export to GitHub

maven-annotation-plugin - issue #23

Pls Publish to Maven Central


Posted on Jun 20, 2010 by Happy Horse

It would really be great to have your project available in Maven Central as we cannot use java.net with most of our components.

Here is how you sign up: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

Comment #1

Posted on Jun 21, 2010 by Quick Rabbit

thx for feedback

i've already submit a request to sonatype

Comment #2

Posted on Jun 23, 2010 by Quick Rabbit

i've deployed release 1.3.6 in staging repository

http://oss.sonatype.org/service/local/staging/deploy/maven2

Comment #3

Posted on Apr 12, 2011 by Grumpy Dog

bartolomeo, where are we with this? i would like to help. i need to get a couple of annotation processors into maven central and cannot because their poms contain def...

Comment #4

Posted on Apr 12, 2011 by Quick Rabbit

hi igor

the issue https://issues.sonatype.org/browse/OSSRH-560 has been closed

i've deployed the release in sonatype staging repo. Is it enough?

Comment #5

Posted on Apr 12, 2011 by Grumpy Dog

no, once the deploy plugin creates and uploads a staged repo you have to log into the nexus ui close the repo (telling nexus the upload is complete) and then promote it (move it from staging to releases). and then after about an hour it will get replicated to central mirrors.

is there an option for you to add me as a user in the nexus ui? if so i can help.

Comment #6

Posted on Apr 12, 2011 by Grumpy Dog

ps my username on there is igor.vaynberg

Comment #7

Posted on Apr 12, 2011 by Quick Rabbit

Hi Igor ... i've just closed&released version 2.0.2 (same of 2.0.1 created just for central repo)

we'll wait one hour and ... hope it will be published

Comment #8

Posted on Apr 13, 2011 by Quick Rabbit

the artifact is available in

https://oss.sonatype.org/content/repositories/releases

Comment #9

Posted on Apr 13, 2011 by Grumpy Dog

looks like there is one more step:

  1. Activate Central Sync The first time you promote a release, you need to comment on the OSSRH JIRA ticket you created in Section 3 so we can know you are ready to be synced. We will review your promoted artifacts. If no problem found, we will activate Central Sync for you and close your JIRA ticket.

After Central Sync is activated, your future promotion will be synced automatically. The sync process runs hourly.

Comment #10

Posted on Apr 13, 2011 by Grumpy Dog

also looks like the artifacts in /releases are corrupt. the jar has the same size as the pom...

Comment #11

Posted on Apr 14, 2011 by Quick Rabbit

thx for feedback

i've sent a request to remove the release 2.0.2 because during certification phase (i.e. ASC generation) the Jar has been corrupted

if it will be not possible ... i will setup a new release 2.0.3 ... accomplishing also 'Activate Central Sync' step

Comment #12

Posted on Apr 14, 2011 by Grumpy Dog

cheers. pelase drop a line here when you take the next step.

Comment #13

Posted on Apr 18, 2011 by Quick Rabbit

finally the artifact has been deployed in central repo

http://repo2.maven.org/maven2

Status: Fixed

Labels:
Type-Task Priority-Medium