On 16.03.2015 18:02, Dmitriy Setrakyan wrote: > I am not sure it is OK for the Ignite project to depend on some personal > GitHub repo. What will it take to make it into Ignite module?
I seem to remember that access to TCKs is restricted in some way? IIUC one needs permission from Oracle to get and use them; if that's the case, publishing it on GitHub is "funny". This one seems to be licensed under ALv2, so those access restrictions don't apply.* * Re: where this is hosted: It's always better to have source in ASF repos; after all Github might (and probably someday will) go away. It's fine to create another repository for this, doesn't have to be part of the main Ignite repo. -- Brane > On Mon, Mar 16, 2015 at 9:59 AM, Sergey Evdokimov <[email protected]> > wrote: > >> You have checkout TCK project configured to use Ignite >> https://github.com/sevdokimov-gg/jsr107tck , and run "mvn -o -P >> !run_tests_from_ide" in the root. >> Don't forget to install latest version of ignite to local repository. >> >> >> On Mon, Mar 16, 2015 at 7:46 PM, Dmitriy Setrakyan <[email protected]> >> wrote: >> >>> Igniters, >>> >>> Can I get the command to run TCK compliance test from Maven? >>> >>> Thanks, >>> D. >>>
