Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
Sender: kristian.rosenvold@zenior.no
In-Reply-To: <52A0DE55.6090404@austin.rr.com>
References: <52997494.5070801@austin.rr.com>
	<CALy+7Unni9LdK1hTj+Lq-jr=0y0etj_6hatbkLhFAoRdPv+i=A@mail.gmail.com>
	<529B6C91.6000202@austin.rr.com>
	<CALy+7Uk4Ehn3whXR5DpT6MMGZwAp8FjKb-px8o2omAy2+S=Q7A@mail.gmail.com>
	<529B7582.3070104@gmx.net>
	<CALy+7U=KQz2G96621jF6wVBp1az1hY0F5R6gVhCYan7J6J8WWA@mail.gmail.com>
	<529BBFE9.1060209@austin.rr.com>
	<CALy+7UmYJk9q+tKoVSBFyB2fNY=NbpLPPWCVBhQWz10y3kMjfQ@mail.gmail.com>
	<529D2F15.40005@austin.rr.com>
	<529E72A1.5040407@austin.rr.com>
	<CALy+7UkUByz_oHOqYqs2jeC0DpmOehji7rWzSx3n7Uge-qd4Zg@mail.gmail.com>
	<529FB75A.3040305@austin.rr.com>
	<CALy+7U=gLrQH-MzWSN7NB_AdKGaRC+c=6JnQYVhmCbZ5ySUamQ@mail.gmail.com>
	<52A0AA95.9060008@austin.rr.com>
	<77187BF5-8F6D-473D-900B-DBFDE15CF6A8@gmail.com>
	<52A0DE55.6090404@austin.rr.com>
Date: Fri, 6 Dec 2013 10:17:32 +0100
Message-ID: 
 <CAJZRQKwm-pUpDsF77rd5w-X4C2f+f442W7MCZ24_FEZ-RW-YSA@mail.gmail.com>
Subject: Re: Upgrade to 3.1.1 causes problems
From: Kristian Rosenvold <kristian.rosenvold@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1efccc08c2204ecda1d3a

--001a11c1efccc08c2204ecda1d3a
Content-Type: text/plain; charset=ISO-8859-1

This is probably because you are using the IBM JDK which might have a
slightly different take on the whole concurrent class loading feature. It
might be that we need to adjust the toggle that we use to activate
concurrent class loading slightly.

Do let us know how this turns out; it should be fixable.

Kristian


2013/12/5 Collins Solutions <Collins-Solutions@austin.rr.com>

> I have made the replacement that you have suggested.  I have ran through
> several builds with maven 3.1.1 and have not seen the error come back.  I
> will continue to monitor this.
>
>
> On 12/05/2013 12:17 PM, Stuart McCulloch wrote:
>
>> You could try replacing:
>>
>>         maven-3.1.1/boot/plexus-classworlds-2.5.1.jar
>>
>> with:
>>
>>         maven-3.0.5/boot/plexus-classworlds-2.4.jar
>>
>> in case the change to use unsynchronised class loading in classworlds 2.5
>> when running on Java 1.7 is causing the issue.
>>
>> On 5 Dec 2013, at 16:32, Collins Solutions <Collins-Solutions@austin.rr.
>> com> wrote:
>>
>>  It is happening on more than one machine.
>>>
>>> On 12/04/2013 10:14 PM, Wayne Fay wrote:
>>>
>>>> ...well, it looks as though this is only a temporary solution. After I
>>>>> got
>>>>> everything to build successfully once I cleaned out my repository, I
>>>>> got the
>>>>> same error when I ran the build a second time. I tried upgraded my
>>>>> Maven
>>>>>
>>>> Is this only happening on one machine, or more than one?
>>>>
>>>> Wayne
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001a11c1efccc08c2204ecda1d3a--