As far as I can tell the recommended approach for using maven with Bamboo OnDemand is to keep the maven repository in an EBS volume (https://confluence.atlassian.com/display/AOD/Configuring+elastic+instances+to+use+the+EBS). You have to manually update the EBS snapshot to add new binaries to the repository.
That approach sounds reasonable for 3rd party dependencies that might not change much once you have them. But it doesn't work for deploying the result of your own builds and making them available to others in your organisation. More than just a maven repository the question really is how to integrate Bamboo OnDemand with a repository manager like Artifactory, Nexus or Archiva.
The only solution I could find was to point Bamboo back to your own repository manager (https://answers.atlassian.com/questions/35548/can-i-point-ondemand-bamboo-to-my-maven-repository). That requires creating an unsupported custom elastic image.
A JIRA issue was created more than 3 years ago (https://jira.atlassian.com/browse/AOD-2305) to provide a repository manager with the OnDemand stack. Since that is not getting much traction there must be good solutions people have found for working with repository managers.
So what's the current state of play? What are people doing to integrate with repository managers? What is Attlassian's recommendation?
Thanks
Lionel.
