Re: Upgrade to 3.1.1 causes problems

2014-08-07 Thread Dan Tran
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, wh

Re: Upgrade to 3.1.1 causes problems

2014-05-12 Thread sachi
Hi Kristian, I was also getting the following error Exception in thread "Thread-7" java.lang.LinkageError: org.codehaus.plexus.util.IOUtil at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:364) at java.security.Se

Re: Upgrade to 3.1.1 causes problems

2013-12-09 Thread Kristian Rosenvold
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 d

Re: Upgrade to 3.1.1 causes problems

2013-12-06 Thread Anders Hammar
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 fea

Re: Upgrade to 3.1.1 causes problems

2013-12-06 Thread Kristian Rosenvold
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 fixa

Re: Upgrade to 3.1.1 causes problems

2013-12-05 Thread Collins Solutions
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-classworld

Re: Upgrade to 3.1.1 causes problems

2013-12-05 Thread Stuart McCulloch
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 So

Re: Upgrade to 3.1.1 causes problems

2013-12-05 Thread Collins Solutions
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 upgrad

Re: Upgrade to 3.1.1 causes problems

2013-12-04 Thread Wayne Fay
> ...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 --

Re: Upgrade to 3.1.1 causes problems

2013-12-04 Thread Collins Solutions
...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 nexus server to version 2.7.0-04 from 2.6.4-02 to see if the proble

Re: Upgrade to 3.1.1 causes problems

2013-12-03 Thread Wayne Fay
Weird and I'm glad you sorted it out, but I wish we had a little more information (root cause) on what was causing the issue, just so we could try to prevent it in the future or provide documentation somewhere to help the next person who runs into this issue. Hopefully they search Google for "mave

Re: Upgrade to 3.1.1 causes problems

2013-12-03 Thread Collins Solutions
As it turns out, there was something that was not correct in my repository directory. On a clean machine, I had no problems performing a successful build. However, I was still seeing the errors on my dev machine. When I removed all of the jar files in my repository directory, everything was b

Re: Upgrade to 3.1.1 causes problems

2013-12-02 Thread Collins Solutions
I will put this on another machine and see if I am getting the same thing. My PATH is as follows: /usr/lib64/qt-3.3/bin:/usr/libexec/lightdm:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/usr/lib/jvm/ibm-jdk7.0-6.0/bin:/opt/maven-3.1.1/bin:/opt/ant-1.9.2/bin:/home/rcollins/.local/bin:/

Re: Upgrade to 3.1.1 causes problems

2013-12-02 Thread Wayne Fay
>> What software is listening on HTTP port 2727 of the machine named >> "tyrone" and version? ... > Sorry about that. Sonatype Nexus 2.6.4-02 OK, I just wanted to know but I doubt that has much impact on this issue... IIUC java.lang.LinkageError means there's a binary incompatability betw

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Manfred Moser
> On 2 Dec 2013, at 9:35 am, Wayne Fay wrote: > >> What software is listening on HTTP port 2727 of the machine named >> "tyrone" and version? Is this Nexus? Artifactory? Archiva? Plain Apache? What version? >>> >>> ...guess what, the URL says /nexus/... >> >> Good point, but this

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Stephen Coy
On 2 Dec 2013, at 9:35 am, Wayne Fay wrote: > What software is listening on HTTP port 2727 of the machine named > "tyrone" and version? >>> >>> Is this Nexus? Artifactory? Archiva? Plain Apache? What version? >> >> ...guess what, the URL says /nexus/... > > Good point, but this is not

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Collins Solutions
Sorry about that. Sonatype Nexus 2.6.4-02 On 12/01/2013 04:35 PM, Wayne Fay wrote: What software is listening on HTTP port 2727 of the machine named "tyrone" and version? Is this Nexus? Artifactory? Archiva? Plain Apache? What version? ...guess what, the URL says /nexus/... Good point, but t

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Wayne Fay
What software is listening on HTTP port 2727 of the machine named "tyrone" and version? >> >> Is this Nexus? Artifactory? Archiva? Plain Apache? What version? > > ...guess what, the URL says /nexus/... Good point, but this is not absolutely definitive, so I'd like confirmation of it. Als

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Michael-O
Am 2013-12-01 18:36, schrieb Wayne Fay: I'll ask my question again... What software is listening on HTTP port 2727 of the machine named "tyrone" and version? Is this Nexus? Artifactory? Archiva? Plain Apache? What version? ...guess what, the URL says /nexus/... --

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Wayne Fay
I'll ask my question again... >> What software is listening on HTTP port 2727 of the machine named >> "tyrone" and version? Is this Nexus? Artifactory? Archiva? Plain Apache? What version? Wayne - To unsubscribe, e-mail: users-

Re: Upgrade to 3.1.1 causes problems

2013-12-01 Thread Collins Solutions
That is a machine that is local to my network. It is up and functioning. I have other repositories listed in my pom. Here are the repos: collins-releases Collins Releases Repository http://tyrone:2727/nexus/content/repositories/releases

Re: Upgrade to 3.1.1 causes problems

2013-11-30 Thread Wayne Fay
> Downloading: > http://tyrone:2727/nexus/content/repositories/releases/org/apache/maven/plugins/maven-javadoc-plugin/maven-metadata.xml What software is listening on HTTP port 2727 of the machine named "tyrone" and version? Wayne -

Re: Upgrade to 3.1.1 causes problems

2013-11-30 Thread Collins Solutions
Update. I am able to do an "mvn clean install" and everything works fine. However, doing an "mvn clean install -U" causes the issues and I am getting the linkage errors. The main cause seems to be with the org.eclipse.aether.transfer.* classes. If anyone can point me in the right direction,

Upgrade to 3.1.1 causes problems

2013-11-29 Thread Collins Solutions
A maven build that was working fine in version 3.1.0, now errors out with the following message. [INFO] [INFO] Building acc-eao 1.0.0-SNAPSHOT [INFO] --