Yeah let's just remove that specific standalone JAR. It was only added to the Pom file for local testing, and not really intended for final release, so no worries. We still have the standalone zip/tar releases as well.
-- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On May 25, 2016, at 1:54 PM, Deron Eriksson <deroneriks...@gmail.com> wrote: > > Hi Luciano, > > 10 of the 11 artifacts look good to me for LICENSE and NOTICE (as far as I > can tell they reflect the artifact contents). However the standalone > uberjar (systemml-0.10.0-incubating-standalone.jar) does not have the > correct LICENSE and NOTICE (one of my commits in the last week must have > affected this, since it worked last week such as at commit e2cb4db...). > > Can we remove this artifact from the release candidate, or is this a > showstopper? I have not heard of anyone using this uberjar. > > Deron > > > On Wed, May 25, 2016 at 1:16 PM, Luciano Resende <luckbr1...@gmail.com> > wrote: > >>> On Wed, May 25, 2016 at 12:47 PM, <dusenberr...@gmail.com> wrote: >>> >>> +1 >>> >>> I ran scripts in Jupyter and Zeppelin using both the Scala and Python >>> MLContext APIs in order to test our notebook integration. >>> >>> One thing to note is that our Python API file, `SystemML.py`, is not >>> included with the main distribution. We can work around this, and it >> should >>> not block this release, but we'll want to it add it for the next release. >> Please raise a jira for this. >> >> >> >> -- >> Luciano Resende >> http://twitter.com/lresende1975 >> http://lresende.blogspot.com/ >>
