I'm seeing a couple potential bugs, definitely at least a typo in
`bin/mahout` where there was some commented out nested ifs; when I comment
out the dangling fi on line 257 I still see some problems. Am I missing a
step?
$ ./bin/mahout spark-shell
Adding lib/ to CLASSPATH
./bin/mahout: line 257: s
n the stuff that’s in SVN.
>
>
>
> Chris
>
>
>
>
>
> *Von: *Andrew Musselman
> *Datum: *Dienstag, 30. Juni 2020 um 16:57
> *An: *Mahout Dev List , Christofer Dutz <
> christofer.d...@c-ware.de>
> *Betreff: *Re: RC1 for 14.1
>
>
>
> (1) We&#x
Von: Andrew Musselman
Datum: Dienstag, 30. Juni 2020 um 16:57
An: Mahout Dev List , Christofer Dutz
Betreff: Re: RC1 for 14.1
(1) We've always done it through Nexus, not married to the approach
(2) Agreed, https://issues.apache.org/jira/browse/MAHOUT-2109
(3) Agreed, https://issues.apach
(1) We've always done it through Nexus, not married to the approach
(2) Agreed, https://issues.apache.org/jira/browse/MAHOUT-2109
(3) Agreed, https://issues.apache.org/jira/browse/MAHOUT-2110
(4) Also https://issues.apache.org/jira/browse/MAHOUT-2110
(5) @Christofer Dutz where are KEYS normally
ke
1. Interesting on the Nexux- who knows who set that up- what are the
pro/cons of nexus v SVN?
2. make sure this gets added to docs
3. let's make a jira for this.
4. just drop them then.
5. https://github.com/apache/mahout/blob/trunk/distribution/KEYS
On Tue, Jun 30, 2020 at 2:42 AM Christofer Du
Hi folks,
some things I noticed:
1) You're using the Nexus Staging Repo ... I know most Apache projects use the
apache SVN for officially staging the release
2) The source-repo is missing the RELEASE_NOTES which usually goes alongside
the source bundle.
3) (this might be the most serious issue)
