-
Bug
-
Resolution: Unresolved
-
Major
-
Host: Linux version 2.6.18-308.4.1.el5 (mockbuild@hs20-bc2-4.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52))
Slave: Windows XP
I need to run a Maven 2 job on a Windows slave, but I need to be able to tell Maven what settings.xml file to use. (In this case it is under a certain user directory) The problem is, the maven core plugin for Jenkins parses the pom.xml to verify it and we are using Nexus as our Maven repository, which the settings are defined in the settings.xml file. Since I can't tell maven core plugin for Jenkins the location of the settings.xml file, it is unable to download the parent pom of the project we are building, so it fails.
The workaround I am using is to create the job using the freestyle template and pass in the settings.xml file location in my maven goal, bypassing the maven core plugin for Jenkins.
In Jenkins 1.519, I see a "Settings file" field, in the advanced build section below the "Goals and options" field of the configuration page of a Maven project.
This settings file for the project can be a path on the filesystem, either relative to the workspace or absolute on the filesystem.
So it seems to me that you can define the settings file to use for your job and that this issue is already fixed.