Closed GoogleCodeExporter closed 9 years ago
thx for feedback
i've already submit a request to sonatype
Original comment by bartolom...@gmail.com
on 21 Jun 2010 at 10:11
i've deployed release 1.3.6 in staging repository
http://oss.sonatype.org/service/local/staging/deploy/maven2
Original comment by bartolom...@gmail.com
on 23 Jun 2010 at 7:37
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 <pluginrepository> def...
Original comment by igor.vay...@gmail.com
on 12 Apr 2011 at 3:13
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?
Original comment by bartolom...@gmail.com
on 12 Apr 2011 at 7:21
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.
Original comment by igor.vay...@gmail.com
on 12 Apr 2011 at 3:19
ps my username on there is igor.vaynberg
Original comment by igor.vay...@gmail.com
on 12 Apr 2011 at 3:19
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
Original comment by bartolom...@gmail.com
on 12 Apr 2011 at 8:35
the artifact is available in
https://oss.sonatype.org/content/repositories/releases
Original comment by bartolom...@gmail.com
on 13 Apr 2011 at 7:43
looks like there is one more step:
9. 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.
Original comment by igor.vay...@gmail.com
on 13 Apr 2011 at 9:48
also looks like the artifacts in /releases are corrupt. the jar has the same
size as the pom...
Original comment by igor.vay...@gmail.com
on 13 Apr 2011 at 10:36
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
Original comment by bartolom...@gmail.com
on 14 Apr 2011 at 9:08
cheers. pelase drop a line here when you take the next step.
Original comment by igor.vay...@gmail.com
on 14 Apr 2011 at 3:10
finally the artifact has been deployed in central repo
http://repo2.maven.org/maven2
Original comment by bartolom...@gmail.com
on 18 Apr 2011 at 12:46
Original issue reported on code.google.com by
joachim.kainz
on 20 Jun 2010 at 7:40