Generally in this case I would add a profile to the settings.xml on your bamboo server that specifies to use your nexus repository. Then if you are building other maven built projects that you don't want to change their pom.xml (i.e adding your nexus repo in there as well) then just specify the profile in the build setup in bamboo for that project. i.e. -P ProfileName
It should then find the profile defined in your settings.xml and use the maven servers there to fetch dependencies
Yes, This is more or less what I do.
But here, I'm talking about the import of a Maven project feature .
When I point the import process to our maven project (which builds fine when creating the maven task manually), the import process fails and in the errors I see it tried to connect directly to maven cerntral and other external maven repositories.
The question is then, why doesn't he use the maven settings ?
Specifically, use an EBS Snapshot attached to your image, as described here:
It even automatically will copy over the .m2/settings.xml for you.
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot