Maven Job on Windows Repository Path

613 views
Skip to first unread message

Michael Ruepp

unread,
Sep 18, 2015, 6:23:41 AM9/18/15
to Jenkins Users
Hi,

I recently set up a new Jenkins System with a Windows 64 Bit Slave over JNLP.

In my System Configuration, I set the Maven Repository Location be relative to the executor, because I had the error and assume it has to do with too long pathnames:

[ERROR] Failed to execute goal com.akathist.maven.plugins.launch4j:launch4j-maven-plugin:1.7.8:launch4j (l4j-clui) on project complsa: Failed to build the executable; please verify your configuration. net.sf.launch4j.ExecException: Exec failed (1): C:\Windows\system32\config\systemprofile\.m2\repository\net\sf\launch4j\launch4j\3.8.0\launch4j-3.8.0-workdir-win32\bin\ld.exe -mi386pe --oformat pei-i386 --dynamicbase --nxcompat --no-seh --subsystem windows -s C:\Windows\system32\config\systemprofile\.m2\repository\net\sf\launch4j\launch4j\3.8.0\launch4j-3.8.0-workdir-win32\w32api\crt2.o C:\Windows\system32\config\systemprofile\.m2\repository\net\sf\launch4j\launch4j\3.8.0\launch4j-3.8.0-workdir-win32\head\guihead.o C:\Windows\system32\config\systemprofile\.m2\repository\net\sf\launch4j\launch4j\3.8.0\launch4j-3.8.0-workdir-win32\head\head.o 
...


on my previous builds, where I had set the maven repos to Default ~/.m2/repository, so the repo was set up in C:\Windows\system32\config\systemprofile\.m2\repository. Why I don´t know, I have no settings.xml, only the pom file of my project which will not specify the local repo so it should go to jenkins defaults.

My jenkins root path in the node is set to c:\build


So either setting has no effect on the location of the maven repository on windows, is this a bug?


Best regards,
Mike

Michael Ruepp

unread,
Oct 4, 2015, 11:08:55 AM10/4/15
to Jenkins Users
Bump, anyone?

Victor Martinez

unread,
Oct 4, 2015, 11:48:54 AM10/4/15
to Jenkins Users
Although I'm not 100% sure if i can help you. It looks like you are using an admin user which it is not based in the default home, doesn't it?
Have you tried to override those default parameters adding the settings.xml and your M2_HOME environment variable accordingly? Maybe that version of the maven plugin or the maven installation itself are buggy but likely you could fix that issue if you override the M2 variable
I hope it helps

Cheers

Reply all
Reply to author
Forward
0 new messages