If you check a settings.xml into the tree where this job can fetch it, I will try to go from there.
On Sun, Jul 31, 2011 at 10:58 AM, Mark Struberg <[email protected]> wrote: > Hi Benson! > > Thanks for this information! > > I don't have much clue about jenkins (apart from reading the build messages), > nor any detailed info about the setup at the ASF. > > Did you understand Dennis' problem description and do have mojo + knowledge > how to fix this on our CI? Our problem is most probably that the current > build uses the -Dmaven.repo.local property to separate local repos for > different builds. > I proposed to use a different maven installation just for being able to set > the localRepository. The settings option might as well do, at least worth a > try. > > Would be really appreciated and a big help if you could take the time and > help us fixing our CI build! > > txs and LieGrue, > strub > > > --- On Sun, 7/31/11, Benson Margulies <[email protected]> wrote: > >> From: Benson Margulies <[email protected]> >> Subject: Re: non-reproducible issues on CI >> To: "Maven Developers List" <[email protected]> >> Date: Sunday, July 31, 2011, 2:49 PM >> Mark, >> >> THe problem is this: jenkins gets going using information >> from the >> global settings.xml before any command-line args are >> processed. So >> you've created a monster, as it were. Luckily, there's a >> job option to >> use an alternative settings so long as it's in the svn real >> estate >> that the job knows about. So while you can have infra >> deploy a >> 'special' maven, you don't have to. >> >> --benson >> >> >> On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg <[email protected]> >> wrote: >> > That's fine, but I fear only as long as you don't use >> -Dmaven.repo.local on your commandline. And exactly that's >> how our jenkins was configured. >> > >> > LieGrue, >> > strub >> > >> > --- On Sun, 7/31/11, Ansgar Konermann <[email protected]> >> wrote: >> > >> >> From: Ansgar Konermann <[email protected]> >> >> Subject: Re: non-reproducible issues on CI >> >> To: "Maven Developers List" <[email protected]> >> >> Date: Sunday, July 31, 2011, 12:42 PM >> >> Had a similar if not same issue while >> >> developing a plugin. Fixed it by >> >> adding >> >> >> >> <systemProperties> >> >> >> >> >> <localRepository>${repository.integrationtests}<localRepository> >> >> <systemProperties> >> >> >> >> to surefire plugin configuration in IT phase. >> >> >> >> Works for me with surefire-plugin 2.9 and >> invoker-plugin >> >> 1.5 >> >> >> >> Regards, >> >> >> >> Ansgar >> >> Am 31.07.2011 13:50 schrieb "Dennis Lundberg" >> <[email protected]>: >> >> >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
