When building OODT, the following code in assembly.xml (in filemgr/src/main/assembly) copies the contents of the filemgr/src/main/resources/examples directory to the filemgr/policy directory in the build target:
It also copies subdirectories and their contents too. This means that the newly created core and geo subdirectories will be copied over along with any files they contain. I've checked the documentation for the maven assembly plugin and this is by design rather than by accident:
"When <include> subelements are present, they define a set of project coordinates to include. If none is present, then <includes> represents all valid values..."
I've tested this by building the latest OODT trunk and confirming that the core and geo directories and contents were copied over to the target policy directory, as expected.
This means that in the future we could add more example configurations as subdirectories and these would automatically be picked up.
Therefore, to complete this task, a committer would need to perform svn moves for the three core files and commit the changes. As a newly appointed OODT committer I'd be happy to move and commit the files if the OODT team are happy for me to go ahead.
Following the changes, to access the core files the filemgr.properties file can be updated reference the policy/core subdirectory rather than the policy directory, for example as follows: