mahout-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MAHOUT-2023) Drivers broken, scopt classes not found
Date Tue, 05 Dec 2017 01:07:00 GMT


ASF GitHub Bot commented on MAHOUT-2023:

Github user rawkintrevo commented on the issue:
    I seem to have validated my suspicion. 
    The viennacl's are being skipped because they are not in fact dependencies, so Maven skips
    You can verify this by first ensuring you have installed viennacl:
    `mvn clean install -Pviennacl`
    Then go back to `mahout/spark/pom.xml` and add the dependency:
    Now run `mvn clean package` and you will see
    [WARNING] The following patterns were never triggered in this artifact inclusion filter:
    o  'org.apache.mahout:mahout-native-viennacl-omp_2.10'
    Scopt is required by `mahout-math-scala` (which to me is silly, but there it is- my .02
is to move the drivers to examples). So vis-a-vis math-scala, `scopt` IS a dependency and
therefor will get picked up. ViennaCL is in NO way a dependency and therefor will never be
included in the dependeny reduced jar. 
    I am updating my PR to remove the two offending lines @pferrel noted, as they simply don't
belong at all.  The user will need to add those jars to the class path of the spark job they
run, this could stand to be documented better- I leave it as an exercise for @andrewpalumbo
or any passing contributor. 

> Drivers broken, scopt classes not found
> ---------------------------------------
>                 Key: MAHOUT-2023
>                 URL:
>             Project: Mahout
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.13.1
>         Environment: any
>            Reporter: Pat Ferrel
>            Assignee: Trevor Grant
>            Priority: Blocker
>             Fix For: 0.13.1
> Type `mahout spark-itemsimilarity` after Mahout is installed properly and you get a fatal
exception due to missing scopt classes.
> Probably a build issue related to incorrect versions of scopt being looked for.

This message was sent by Atlassian JIRA

View raw message