Automatic collecting of maven artifacts for http data list should be identified.

Current procedure is very cumbersome and consists of some manual policy compilations in policy pods.

Scope/DoD:

1) identify what maven artifacts are still required in Dublin scope,

see discussion in POLICY-1576 - it looks that some policy artifacts are no longer needed to be provided by our offline platform .... (are goal is to get rid also of the others) 

2) for the remaining artifacts find some simplified way of creating data list

https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=build/data_lists/onap_3.0.x-http_files.list;h=42d5b1026bf0ae41c1275f8e9e50507fb463b95d;hb=HEAD

Few hints were discussed during planning session:

• evaluate dependencies collecting from pom files
• evaluate maven dependencies plugin
• collect commands for triggering compilation 

Problem is that different dependencies might be relevant for different usecases ...