Parse in module

Don't review yet.
Actually, I would like the kore.k file to be somewhere in the /include
directory.

On Thu, Oct 30, 2014 at 8:48 PM, Cosmin Radoi <notifications@github.com>
wrote:

> In kernel/src/test/java/org/kframework/parser/utils/KoreIT.java:
>
> > +import org.apache.commons.io.FileUtils;
> > +import org.junit.Test;
> > +import org.kframework.kil.Definition;
> > +import org.kframework.kil.ProductionReference;
> > +import org.kframework.kil.Sort;
> > +import org.kframework.kil.Sources;
> > +import org.kframework.parser.outer.Outer;
> > +import org.kframework.utils.BaseTestCase;
> > +import org.kframework.utils.errorsystem.ParseFailedException;
> > +import org.kframework.utils.file.JarInfo;
> > +
> > +import java.io.File;
> > +
> > +/**
> > + * Test a the kore definition using the new parser.
> > + * KoreIT has to be run after the distribution has been built (apparently), therefore the name IT at the end.
>
> This is not really an integration test. I say we move the definitions to
> test/resources and allow the test to run along with the other unit tests.
> Also, we do want kore.k in the main tool, not in some samples directory.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kframework/k/pull/1115/files#r19647872>.
>