On Nov 11, 2009, at 5:29 PM, Grant Ingersoll wrote:
On Nov 11, 2009, at 3:42 PM, Jukka Zitting wrote:
It should be possible to deploy the missing artifacts like this:
mvn gpg:sign-and-deploy-file \
-Durl=https://repository.apache.org/service/local/staging/
deploy/maven2
\
-DrepositoryId=apache.releases.https \
-DgroupId=org.apache.mahout.xxx -DartifactId=xxx \
-Dversion=xxx -Dpackaging=jar -Dfile=core/lib/xxx.jar
Some further thoughts on this:
Perhaps we should do this upfront for any/all deps we use that
aren't in Maven that we need, regardless of a release. Then we
don't have to have users do a "mvn install" first, since all
artifacts will be resolvable.
As Jukka said, then we just need to deploy them once whenever we
upgrade them. The release process should also get a lot easier.
Any reason not to?
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". Artifacts being
signed and uploaded now.
-Grant
