FYI, email thread below is why 3.11 beta 3 isn't on maven yet
If someone fancies trying to replace mvn-deploy.sh with the tomcat script
referenced below, or some other tweak to talk to nexus, that'd be great.
If not, I'll try to look later today or tomorrow
I've also asked Infra to set us up an area in the Nexus repo, see
INFRA-8623
Nick
---------- Forwarded message ----------
Date: Fri, 14 Nov 2014 09:53:30 +0000
From: Mark Thomas <[email protected]>
To: Nick Burch <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Maven Central <-> m2-ibiblio-rsync-repository sync broken?
On 14/11/2014 09:49, Nick Burch wrote:
On Fri, 14 Nov 2014, David Nalley wrote:
This was apparently deprecated in March 2012[1] with EOS purportedly
set for Jan 2013.
Obviously the service was never dismantled, and it's apparently not
functioning now.
Is there a reason not to use repository.a.o?
We're an Ant based project, so we just use the "push voted on release
artifacts to Maven" script that was set up years ago without really
knowing too much about how it works, just that it does/did
Is using one of the processes documented on
http://www.apache.org/dev/publishing-maven-artifacts.html the only
supported way to publish things to maven central now? Or are there other
options we can look at? We're after the simplest way to go from Jar +
minimal Pom + Hashes + Signatures to something Maven users can get at!
Tomcat has some scripts to upload the Tomcat JARs to Nexus that you can
probably borrow some ideas from:
http://svn.eu.apache.org/viewvc/tomcat/trunk/res/maven/mvn-pub.xml?view=annotate
The POMs etc are in the same directory. I suspect POIs requirements will
be simpler.
(Given the email from Joe, I suspect that it's not something that Infra
will want to un-break now...)
Correct. Nexus is your only option for this.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
