Hi,
our developers use Maven for their (local) builds which stores artifacts in the local filesystem (~/.m2/repository)
The build server uses the same build - and uploads artifact to a repository server (Nexus), which is a quite common setup I guess.
Now we have introduced Ansible - for deployment purposes, which works quite good.
It´s accessing the Nexus URL - and downloads the needed artifacts.
From developement side it would be useful to be also able to use the local filesystem repository (~/.m2/repository) first,
before looking in the remote repository (Nexus).
Of course we can “wrap” this inside a role, introduce some properties to switch between local and remote repository and so on,
but for me this looks like re-inventing the wheel.
Much more smarter may be to use “Aether” as the API to access the artifact repository, because than we can rely on it´s functionality
to cache downloaded artifacts, to handle updated SNAPSHOT versions and so on.
Another benefit would be, that whenever a Maven build has already downloaded an artifact to the (local) repository, the Ansible run
can use this, too, so the Maven repository behaves like a “Ansible get_url cache”.
Has anyone setup this already? Or other ideas to integrate Maven´s repository with Ansible ?
Thanx for any advice,
Torsten