Hi Chris,

Thanks! Pip should work. In fact, we were hoping you'd say that :)

Best,

Josh

-----Original Message-----
From: Mattmann, Chris A (3010) [mailto:chris.a.mattm...@jpl.nasa.gov]
Sent: Tuesday, April 4, 2017 6:11 PM
To: dev@senssoft.incubator.apache.org
Cc: Mcgibbney, Lewis J (398M) <lewis.j.mcgibb...@jpl.nasa.gov>
Subject: Re: Maven alternatives for Analyzing Builds in JS and Python

Hey Josh, how about setuptools, and pip?

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Principal Data Scientist, Engineering Administrative Office (3010) Manager, NSF 
& Open Source Projects Formulation and Development Offices (8212) NASA Jet 
Propulsion Laboratory Pasadena, CA 91109 USA
Office: 180-503E, Mailstop: 180-503
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate 
Professor, Computer Science Department University of Southern California, Los 
Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


On 4/4/17, 2:31 PM, "Poore, Joshua C." <jpo...@draper.com> wrote:

    Lewis,


    We're looking into build tools for our releases. None of our projects are 
currently in Java, so we'll need guidance as to your favorite approaches to 
analyzing JavaScript and Python. See  
https://issues.apache.org/jira/browse/SENSSOFT-165



    We are currently investigating the PMD plugin for Maven, and Pip, PyBuilder 
and Distutils. Please let us know if we're going down the Apache-compliant 
track for analyzing builds given our needs.

    ________________________________
    Notice: This email and any attachments may contain proprietary (Draper 
non-public) and/or export-controlled information of Draper. If you are not the 
intended recipient of this email, please immediately notify the sender by 
replying to this email and immediately destroy all copies of this email.
    ________________________________


________________________________
 Notice: This email and any attachments may contain proprietary (Draper 
non-public) and/or export-controlled information of Draper. If you are not the 
intended recipient of this email, please immediately notify the sender by 
replying to this email and immediately destroy all copies of this email.
________________________________

Reply via email to