Migration stage 3 - migrate script module

[javiertuya]

Start this ONLY when #5 and #6 are closed:

• Migrate the script module source code
• Update the poms with the required dependencies
• Now you have two test levels, each must run in a separate job. Therefore, change the test-java job name to test-ut to run only unit tests in both modules
• Add a job to run the integration tests (name: test-it)

Afther closing this, all development must be made in this repository. I will archive the old on-premises repository

[giis-qabot]

@suarezgpablo This is a reminder about this issue because it has not been updated for 10 days

[giis-qabot]

@suarezgpablo This is a reminder about this issue because it has not been updated for 10 days

[suarezgpablo]

There are some issues regarding the class TestUtils from the package test4giis.modevo from the transform module. Currently I cannot access the methods from this class in the testclass TestExecutionScript from the script module. I can access the methods from the main folder of the transform module without any issue in the testclass TestExecutionScript. I am currently looking into it.

[javiertuya]

@suarezgpablo Test classes are independent from the main classes, so, it is normal that you can't access the tests of a module from the tests of another module. This is because dependencies between modules rely on the jar artifacts. By default only main jars are created. You have to create a test jar in the transform module

[suarezgpablo]

@suarezgpablo Test classes are independent from the main classes, so, it is normal that you can't access the tests of a module from the tests of another module. This is because dependencies between modules rely on the jar artifacts. By default only main jars are created. You have to create a test jar in the transform module

Would it be similar to how I created the jar for the ATL compiler?

[javiertuya]

@suarezgpablo I think so, using the maven jar plugin as usually. If I remember well, I did that in qabot or tdrules