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 <strub...@yahoo.de> 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 <ansgar.konerm...@googlemail.com> wrote:
>
>> From: Ansgar Konermann <ansgar.konerm...@googlemail.com>
>> Subject: Re: non-reproducible issues on CI
>> To: "Maven Developers List" <dev@maven.apache.org>
>> 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" <denn...@apache.org>:
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
