Thoughts:
-The Mahout parent POM should probably be called mahout-parent or
something like that, it's kind of confusing in the Maven structure at http://people.apache.org/~kalle/staging-area/mahout0.1rc2/maven/org/apache/lucene/mahout/
-Maven artifacts need to be signed. See https://issues.apache.org/jira/browse/SOLR-776
for an ANT task to do this. Of course, Maven may take care of this
for you. We might consider using Maven for building release
artifacts. Of course, maybe we should just bite the bullet and use
Maven. If we need anything sophisticated, we could always punt out to
Ant via the Ant goal in Maven. Separate conversation, I suppose. How
hard would it be in Maven to build the release artifacts?
- Karl, you need to publish your code signing key: http://www.apache.org/dev/release-signing.html
Currently, verification of the signatures fails.
-The NOTICE.txt is not up to date with what is checked in on
branch-0.1. Nor is the README.
- I checked in some updates that put in proper ASL headers on files.
I'll keep checking
-Grant
On Sep 21, 2008, at 1:33 PM, Karl Wettin wrote:
I just created the second release candidate for 0.1, here:
http://people.apache.org/~kalle/staging-area/mahout0.1rc2
Please download and report back on any issues you encounter.
There is virtually no difference between the tar/zip balls in rc1
and rc2, just the name change and some additions to the Ant and
Maven build files. No code or docs changes.
It now contains Maven artifacts. I'm pretty sure there are problems
with these artifacts as the POM files contains some rather whacky ad
hoc stuff to handle dependencies that's not distributed via Maven,
notably Hadoop and several of its dependencies. There is also the
fact that we use multiple modules with a parent POM, I'm not sure if
that is set up as it should. I'll have to ask around a bit in Maven
fora and see what people there think of it and how they ususally go
about that stuff.
So there will probably be an rc3 too.
karl
