For the record, here's what I did:
1016 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -
DgroupId=org.apache.mahout.kosmosfs -DartifactId=kfs -Dversion=0.3 -
Dpackaging=jar -Dfile=kfs-0.3.jar
1017 hg sign-and
1018 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -
DgroupId=org.apache.mahout.kosmosfs -DartifactId=kfs -Dversion=0.3 -
Dpackaging=jar -Dfile=kfs-0.3.jar
1019 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.hbase -
DartifactId=hbase -Dversion=0.20.0 -Dpackaging=jar -
Dfile=hbase-0.20.0.jar
1020 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.jets3t
-DartifactId=jets3t -Dversion=0.7.1 -Dpackaging=jar -
Dfile=jets3t-0.7.1.jar
1021 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -DgroupId=org.apache.mahout.hadoop
-DartifactId=hadoop-core -Dversion=0.20.1 -Dpackaging=jar -
Dfile=hadoop-core-0.20.1.jar
1022 mvn gpg:sign-and-deploy-file -Durl=https://
repository.apache.org/service/local/staging/deploy/maven2 -
DrepositoryId=apache.releases.https -
DgroupId=org.apache.mahout.kosmofs -DartifactId=kfs -Dversion=0.3 -
Dpackaging=jar -Dfile=kfs-0.3.jar
I then went into Nexus and closed and then promoted the staging
repository, such that these are now available. I will commit the POM
changes shortly.
On Nov 11, 2009, at 5:46 PM, Jukka Zitting wrote:
Hi,
On Thu, Nov 12, 2009 at 12:37 AM, Grant Ingersoll
<[email protected]> wrote:
I'm going forward with this, since I see no difference between
doing it up
front and doing it during a release. This clearly falls under the
category
of "why didn't we do this sooner".
Exactly. Maven assumes that all non-SNAPSHOT dependencies are already
available in the repository, and Just Works (TM) when that's the case.
No need for custom install/deploy steps.
BTW, this is also Maven users are so eager to see things like Lucene
jars on Maven central, and why having the Hadoop project deploy their
jars is better than each downstream project deploying their own
copies.
BR,
Jukka Zitting
