spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-4816) Maven profile netlib-lgpl does not work
Date Mon, 14 Dec 2015 18:13:46 GMT


Sean Owen commented on SPARK-4816:

I'm on Maven 3.3.x. I wonder if that could be a difference -- can you try 3.3.x just to check?

If you're correct, this is already fixed for the next 1.4 which should be 1.4.2. I don't know
if/when that will be released though. (I also don't know why the branch shows 1.4.3-SNAPSHOT)
It's as fixed as it would be for this branch though. But then yes it would be listed as fixed
as part of any release notes, automatically.

I think finding a relevant JIRA may be as good as it gets in the general case for finding
whether something's already known as an issue and fixed. This one ought to be easy to find
by keyword. Of course -- if there is a problem -- just having it work in later releases is
even better.

I'm not aware of any additional fix that needs to be made though. As I say I can't even reproduce

> Maven profile netlib-lgpl does not work
> ---------------------------------------
>                 Key: SPARK-4816
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.1.0
>         Environment: maven 3.0.5 / Ubuntu
>            Reporter: Guillaume Pitel
>            Priority: Minor
>             Fix For: 1.1.1
> When doing what the documentation recommends to recompile Spark with Netlib Native system
binding (i.e. to bind with openblas or, in my case, MKL), 
> mvn -Pnetlib-lgpl -Pyarn -Phadoop-2.3 -Dhadoop.version=2.3.0 -DskipTests clean package
> The resulting assembly jar still lacked the netlib-system class. (I checked the content
of spark-assembly...jar)
> When forcing the netlib-lgpl profile in MLLib package to be active, the jar is correctly
> So I guess it's a problem with the way maven passes profiles activitations to children
> Also, despite the documentation claiming that if the job's jar contains netlib with necessary
bindings, it should works, it does not. The classloader must be unhappy with two occurrences
of netlib ?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message