Updating the pom.xml repositories (which will also reduce build time)
Updating the pom.xml distribution management (to publish the artifacts publicly)
In implementing this I found a surprise:
Many sections of the build avoid dependencies entirely and instead copy content between directories.
Use of maven-resources-plugin:copy-resources to copy directories needs to be replaced with maven-dependency-plugin:unpack to copy content out of artifacts (zip or jar).
For the above to work several things that are currently pom packaging will need to change to zip or jar (so that their contents are available in the maven repository to download and unpack.
The build server is deploying releases / snapshots
We can test when this activity is completed the transition to artifacts by starting wot empty local maven repository cd into any geonetwork folder and build.
As I do not have commit access this is going to be difficult to do via careful individual PRs. I would like to ask for a small work party (on gitter?) explore these topics, make the changes to master, and try them out locally and on the build server.
I have been keeping the proposal up to date to reflect state of work, I know that does not directly reflect what was reviewed/approved but it is good to have a summary of activities.
Updating the pom.xml repositories
this did not go completely smoothly, some odd dependencies from core-maven-repo are available no where else…
some like globes are somehow invalid and nexus refuses to let me upload them!
rather than be blocked I setup geonetwork-cache as a temporary measure which will lazily pull from core-maven-repo
a side benefit is you can visit the above url and see only the third-party jars we are responsible for
