Minor Issues while building Mahout

[Aditya]

Hey everyone,

While working on the issue MAHOUT-1967 I came across something weird. While
building Flink and Viennacl (separately) I came across an error that read:

The project org.apache.mahout:mahout-hdfs:0.13.1-SNAPSHOT
(/home/shikharv/Aditya_079/Personal/GSoC/mahout/hdfs/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for
org.apache.hadoop:hadoop-client:jar must be a valid version but is
'${hadoop.version}'. @ org.apache.mahout:mahout:0.13.1-SNAPSHOT,
/home/shikharv/Aditya_079/Personal/GSoC/mahout/pom.xml, line 258, column 18

This error only occurs when I try to do a *mvn install -Pviennacl* (say)
but doesn't occur when I do a *mvn** install -Pviennacl -Phadoop2*

On a cursory glance, it seems that on line number 258 where
${hadoop.version} is first being used, there is no declaration of
*hadoop.version.
*The declaration only comes in the profiles section when -Phadoop2 flag is
used.

Are there other instances of this error that occur while building other
modules? (If others have faced a similar issue)

Should I open a JIRA issue to fix these bugs (all similar ones)?

Regards,
Aditya

[Andrew Musselman]

Hey Aditya, yes please open a JIRA ticket for this.

Post by Aditya
Hey everyone,
While working on the issue MAHOUT-1967 I came across something weird. While
The project org.apache.mahout:mahout-hdfs:0.13.1-SNAPSHOT
(/home/shikharv/Aditya_079/Personal/GSoC/mahout/hdfs/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for
org.apache.hadoop:hadoop-client:jar must be a valid version but is
/home/shikharv/Aditya_079/Personal/GSoC/mahout/pom.xml, line 258, column 18
This error only occurs when I try to do a *mvn install -Pviennacl* (say)
but doesn't occur when I do a *mvn** install -Pviennacl -Phadoop2*
On a cursory glance, it seems that on line number 258 where
${hadoop.version} is first being used, there is no declaration of
*hadoop.version.
*The declaration only comes in the profiles section when -Phadoop2 flag is
used.
Are there other instances of this error that occur while building other
modules? (If others have faced a similar issue)
Should I open a JIRA issue to fix these bugs (all similar ones)?
Regards,
Aditya