Maybe replacing it with html 5, I am not saying it's 5 min work of course. But this way it will allow including it in the main line - develop / trunk branch and continue being apache license 2 - without any dependency issues. Again, it's not 5min solution of course. Dor
-----Original Message----- From: Jacob Barrett [mailto:[email protected]] Sent: יום ג 10 מאי 2016 19:47 To: [email protected] Subject: Re: MultiAxisChartFX and jvsd Do you have a suggestion for a better graphing package in Java? JavaFX graphing library is very fast and extensible. On Tue, May 10, 2016 at 9:45 AM Dor Ben Dov <[email protected]> wrote: > Any news on the jVSD and when it will be merged to the main branch ? > Any thought maybe to replace the javafx with different solution maybe ? > > Thanks > Dor > -----Original Message----- > From: Daniel Farcovich > Sent: יום ג 10 מאי 2016 08:37 > To: Jacob Barrett > Cc: [email protected] > Subject: RE: MultiAxisChartFX and jvsd > > Hi Jake, > Do you know when is jVSD going to be merged into the develop branch? > > Thanks, > Daniel > > -----Original Message----- > From: Jacob Barrett [mailto:[email protected]] > Sent: Monday, May 09, 2016 6:09 PM > To: [email protected] > Subject: Re: MultiAxisChartFX and jvsd > > A complete rewrite of MultiAxisChartFX is not planned. The > MultiAxisChartFX is derived from the OpenJDK XYChart and carries the > same GPL with class path exception that the JDK does. The plan is to > merge jVSD into the develop branch with the dependency as is. The > binary distribution will not contain the dependency. On first > execution of jVSD it will prompt and download the dependency. > > -Jake > > > On Sun, May 8, 2016 at 8:10 AM Daniel Farcovich < > [email protected]> > wrote: > > > Hi, > > > > Is jvsd going to be merged to the main branch anytime soon? > > > > Will MultiAxisChartFX class be replaced by another class which > > complies with Apache 2.0 license? > > > > > > > > Thanks, > > > > Daniel > > > > > > > > *From:* Juan José Ramos [mailto:[email protected] > > <[email protected]>] > > *Sent:* יום ד 06 אפריל 2016 10:56 > > *To:* [email protected] > > *Subject:* Re: geode in maven repository > > > > > > > > Hey Dor, > > > > > > > > According to Jens (from the mail list history): > > > > *The MultiAxisChartFX class is GPL code and cannot have an Apache > > 2.0 license attached to it. This is the reason this code was in a > > separate repo. A* > > > > *user would need to build that separately and then reference it in > > this > > project."* > > > > > > > > Hope this helps. > > > > Best regards. > > > > > > > > > > > > On Wed, Apr 6, 2016 at 8:36 AM, Dor Ben Dov <[email protected]> > > wrote: > > > > Do you remember which dep’ is preventing it from being Apache license 2 ? > > > > Maybe it’s something –we as community can do ? > > > > > > > > Dor > > > > > > > > *From:* Juan José Ramos [mailto:[email protected]] > > *Sent:* יום ד 06 אפריל 2016 10:30 > > *To:* [email protected] > > *Subject:* Re: geode in maven repository > > > > > > > > Hi Dor, > > > > > > > > As my understanding, the project MultiAxisChart doesn't use the > > apache license and that's the reason is not even included in the > > development branch, so we shouldn't modify the project and include > > it as part of > Geode. > > In the short term we should get rid of the dependency to that > > project and right now we are only using it as it is. > > > > Cheers. > > > > > > > > > > > > On Tue, Apr 5, 2016 at 6:19 PM, Dor Ben Dov <[email protected]> > > wrote: > > > > Jens, > > > > Why does the gradle of geode-jvsd have an internal execution of > > maven pom ? > > > > Better replacing the pom with gradle no ? > > > > > > > > Dor > > > > > > > > *From:* Jens Deppe [mailto:[email protected]] > > *Sent:* יום ג 05 אפריל 2016 19:32 > > > > > > *To:* [email protected] > > *Subject:* Re: geode in maven repository > > > > > > > > Gal, > > > > > > > > Also, if you're building Geode from source, the 'install' task will > > create artifacts in your local maven repository. > > > > > > > > --Jens > > > > > > > > On Tue, Apr 5, 2016 at 8:49 AM, Gregory Chase <[email protected]> wrote: > > > > Hi Gal, > > > > There's never a specific "time" for a next Apache release. You will > > see the voting activity in the dev mail list when its time to push a > release. > > > > > > > > You can also track status here: > > https://cwiki.apache.org/confluence/display/GEODE/Release+Management > > > > > > > > You should also join our Geode Clubhouse community call tomorrow, > > 9AM Pacific Daylight Time: > > http://markmail.org/message/2ylydxxlo7zsax6y > > > > > > > > We will likely be discussing the status of the next release towards > > the end. > > > > > > > > On Tue, Apr 5, 2016 at 8:44 AM, Gal Palmery <[email protected]> > > wrote: > > > > Thanks Anthony, > > And when is the next planned release ? > > > > > > -----Original Message----- > > From: Anthony Baker [mailto:[email protected]] > > Sent: Tuesday, April 05, 2016 17:56 > > To: [email protected] > > Subject: Re: geode in maven repository > > > > Hi Gal, > > > > Maven Central only contains official releases approved by the PPMC: > > http://search.maven.org/#search%7Cga%7C1%7Cgeode > > > > The nightly development snapshot versions can be found here: > > https://repository.apache.org/content/repositories/snapshots/ > > > > For gradle you would use: > > > > repositories { > > maven { url " > > https://repository.apache.org/content/repositories/snapshots"; } } > > > > dependencies { > > compile 'org.apache.geode:geode-core:1.0.0-incubating.M2-SNAPSHOT' > > } > > > > Anthony > > > > > On Apr 5, 2016, at 1:41 AM, Gal Palmery <[email protected]> > wrote: > > > > > > Hi, > > > > > > I noticed that the maven repository isn’t updated with the new > > > geode jars, how often do you update it? and to which repository > > > are you > > uploading the jars? > > > > > > Thanks, > > > Gal > > > > > > This message and the information contained herein is proprietary > > > and confidential and subject to the Amdocs policy statement, you > > > may review at http://www.amdocs.com/email_disclaimer.asp > > > > > > This message and the information contained herein is proprietary and > > confidential and subject to the Amdocs policy statement, you may > > review at http://www.amdocs.com/email_disclaimer.asp > > > > > > > > > > > > -- > > > > Greg Chase > > > > > > > > Global Head, Big Data Communities > > > > http://www.pivotal.io/big-data > > > > > > > > Pivotal Software > > > > http://www.pivotal.io/ > > > > > > > > 650-215-0477 > > > > @GregChase > > > > Blog: http://geekmarketing.biz/ > > > > > > > > > > > > > > > > > > > > -- > > > > Juan José Ramos Cassella > > > > Senior Technical Support Engineer > > > > *Email:* [email protected] > > > > *Office#*: +353 21 4238611 > > > > *Mobile#*: +353 87 2074066 > > > > *After Hours Contact#*: 877 477 2269 > > > > *Working Hours*: Monday to Friday 08:30 - 17:00 GMT > > > > *How to upload artifacts:* > > https://support.pivotal.io/hc/en-us/articles/204369073 > > > > *How to escalate a ticket:* > > https://support.pivotal.io/hc/en-us/articles/203809556 > > <https://support.pivotal.io/hc/en-us/articles/203809556-Pivotal-How- > > do > > -I-escalate-an-existing-case-> > > > > > > > > [image: Image removed by sender.] > > > > > > > > > > > > -- > > > > Juan José Ramos Cassella > > > > Senior Technical Support Engineer > > > > *Email:* [email protected] > > > > *Office#*: +353 21 4238611 > > > > *Mobile#*: +353 87 2074066 > > > > *After Hours Contact#*: 877 477 2269 > > > > *Working Hours*: Monday to Friday 08:30 - 17:00 GMT > > > > *How to upload artifacts:* > > https://support.pivotal.io/hc/en-us/articles/204369073 > > > > *How to escalate a ticket:* > > https://support.pivotal.io/hc/en-us/articles/203809556 > > <https://support.pivotal.io/hc/en-us/articles/203809556-Pivotal-How- > > do > > -I-escalate-an-existing-case-> > > > > > > > > [image: Image removed by sender.] > > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, you may > review at http://www.amdocs.com/email_disclaimer.asp > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
