I ran into the same issue with OpenSuse 11+ IBM JDK 1.7. Looks like there is no good progress on this
-D On Mon, Dec 9, 2013 at 11:55 AM, Kristian Rosenvold < kristian.rosenv...@gmail.com> wrote: > I answered to their 5 page questionaire and did not read their 200 page > license agreement, which all allowed me download their JDK (This probably > means IBM now own any further kids I may choose to have...) > > The IBM jdk does appear to support concurrent classloading. There is > probably some subtle difference in internal synchronization mechanisms that > is causing this to bork out on IBM JDK. The appropriate path of action here > would probably be to simply compare the two different java.lang.ClassLoader > implementations and find the difference. > > I will try to get around to this fairly quickly; if someone wants to do a > side-by side walkthrough (maybe comparing with > http://www.docjar.com/html/api/java/lang/ClassLoader.java.html), it should > be fairly easy to track. Concurrency/synchronization is the thing to check > here. > > Kristian > > > > 2013/12/6 Anders Hammar <and...@hammar.net> > > > Maybe we should set up a core IT build job with IBM JDK? > > > > /Anders > > > > > > On Fri, Dec 6, 2013 at 10:17 AM, Kristian Rosenvold < > > kristian.rosenv...@gmail.com> wrote: > > > > > 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-soluti...@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-soluti...@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-unsubscr...@maven.apache.org > > > >>>> For additional commands, e-mail: users-h...@maven.apache.org > > > >>>> > > > >>>> > > > >>>> > > > >>> > --------------------------------------------------------------------- > > > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > >>> For additional commands, e-mail: users-h...@maven.apache.org > > > >>> > > > >>> > > > >> > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > >> For additional commands, e-mail: users-h...@maven.apache.org > > > >> > > > >> > > > >> > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > >
