This story provides a list of discovered issues for missing items, POM problems, configuration problems in the new APEX repo.

Runtime

• Help on APEX engine (main) prints options twice

Module Packages

• full package does not create etc/app-version.txt - this resource is missing from model/utilities

Module Plugins

• plugins-event-protocol does not build YAML (pom module error)

Test Data and Javadoc:

• "com.ericsson.apex" package names still remain in cli-editor.stg, test data and in Javadoc comments. A full grep on all source files is required to remove them all.

Unit and Integration Tests:

• Check that all integration tests have been transferred correctly.

Naming problem for apex-pdp/plugins/plugins-context

• All sub projects here should be named “plugin“ but only the test one is named so (all other plugin projects are ok)-

Metrics

• Tidy up metrics tests

Example code (SampleDomain not being copied into build example directory)

• JRuby related tests in integration-executor-test are failing in windows environment

Either we need to upgrade the jruby core version to 9.1.3.0 or use jruby-complete jar instead of jruby core used currently.

• Tests inside integration-uservice-test keeps failing at some or other point

The tests are mostly failing because of timing issues. It expects the work to be finished by certain amount of time but that varies depending on the system performance. Which makes the test to fail.

There are 2 problems with org.onap.policy.apex.apps.uservice.test.adapt.kafka.TestKafka2Kafka.java:

1- The Kafka broker cannot delete the log files after the configured time. That only happes in Windows environment (https://issues.apache.org/jira/browse/KAFKA-1194), and it seems that it hasn't fixed. In Ubuntu 16.04 that Jenkins are using, there is no such problem. 

2- Most of the times, tests failed at testKafkaEvents() with error: "testKafkaEvents:140 expected:<100> but was:<99>"  That require many re-checks to Jenkins Job Builder. Need to find out where that problem happens and fix it.

• Packaging of apex tools

We need to decide about packaging of apex tools. Should it be part of apex-pdp full package tarball or separate?

should be in package full, otherwise documentation does not work - consider different package and rewrite docs, or reoder module in build

• Packaging of apex clients

We need to decide about packaging of apex clients. Should they be part of the same apex-pdp full package and run in the same docker container or it has to be packaged separately and deployed in a separate docker container (obviously then we need to have inter communication between these 2 containers).

should be in package full, otherwise documentation does not work, consider: different package and rewrite docs, add pyhon code that does not require full Java compile (and rewrite docs) or change moudle sequence in build
 
After installing the latest tarball, apexConfigConverter  is missing under bin folder

• apexConfigConverter missing in tarball
  config converter is obsolete for ONAP release, was only important for earlier APEX versions.-