Bamboo: import a Maven project not using settings.xml ?!

[Julien Tognazzi]

Hi, I have a bamboo server behind a proxy. Maven on this server is configured to use our nexus repository as configured in the system wide settings.xml. But if I try to import a maven project. It fails trying to connect to extern maven repositories. So it seems to me it doesn't take the settings.xml into account... If I create the plan manually, setting a maven task, it builds ok. Is it the normal behavior ? thanks.

[Ben]

Specifically, use an EBS Snapshot attached to your image, as described here:
https://confluence.atlassian.com/display/BAMBOO/Configuring+elastic+instances+to+use+the+EBS

It even automatically will copy over the .m2/settings.xml for you.

[Colin Goudie]

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

[Julien Tognazzi]

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 ?