[jboss-jira] [JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen

[Edoardo Vacchi (Jira)]

     [ https://issues.jboss.org/browse/DROOLS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edoardo Vacchi updated DROOLS-4269:
-----------------------------------
    Sprint: 2019 Week 26-28


> kogito-codegen-tests: alternative testing strategy for codegen
> --------------------------------------------------------------
>
>                 Key: DROOLS-4269
>                 URL: https://issues.jboss.org/browse/DROOLS-4269
>             Project: Drools
>          Issue Type: Bug
>            Reporter: Edoardo Vacchi
>            Assignee: Edoardo Vacchi
>            Priority: Major
>              Labels: drools-core, kogito, submarine
>
> Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin.
> - create `kogito-codegen-tests`
> - write data/rules/process sources under src/main/{java,resources}
> - write tests under src/test/
> tests are now allowed to refer directly to codegenerated classes by name.
> just use mvn compile test to run the tests
> caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this



--
This message was sent by Atlassian Jira
(v7.12.1#712002)