beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2460) Make python maven variables available elsewhere
Date Sun, 18 Jun 2017 19:17:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053296#comment-16053296
] 

Ahmet Altay commented on BEAM-2460:
-----------------------------------

+1 to moving findSupportedPython to a root level if it will be used by other components. [~tibor.kiss@gmail.com]
 is the author of the groovy file and at that we could not find another maven natural way
of discovering python/pip binaries.

> Make python maven variables available elsewhere
> -----------------------------------------------
>
>                 Key: BEAM-2460
>                 URL: https://issues.apache.org/jira/browse/BEAM-2460
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-java-core, sdk-py
>            Reporter: Stephen Sisk
>            Assignee: Stephen Sisk
>            Priority: Minor
>
> We're planning to start using perfkit to make it easy for users to run the IO ITs. Perfkit
is a python app, so we'll need to invoke the python interpreter. 
> findSupportedPython calculates this and sets the python.interpreter.bin variable. It
currently does so in the python project. 
> I believe the correct answer here is to move findSupportedPython so that's it's invoked
in the root pom. (but perhaps there's a more maven-y approach to this problem?) 
> cc [~altay] [~markflyhigh] [~jasonkuster] [~davor]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message