You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Collins Solutions <Co...@austin.rr.com> on 2013/11/30 06:16:04 UTC
Upgrade to 3.1.1 causes problems
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]
------------------------------------------------------------------------
Exception in thread "pool-1-thread-3" java.lang.LinkageError:
org.apache.maven.wagon.PathUtils
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
at
java.security.AccessController.doPrivileged(AccessController.java:366)
at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:143)
at
org.apache.maven.wagon.repository.Repository.<init>(Repository.java:91)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector.<init>(WagonRepositoryConnector.java:146)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnectorFactory.newInstance(WagonRepositoryConnectorFactory.java:159)
at
org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:139)
at
org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:613)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:804)
Exception in thread "pool-2-thread-1" java.lang.LinkageError:
org.eclipse.aether.transfer.TransferEvent$RequestType
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
at
java.security.AccessController.doPrivileged(AccessController.java:366)
at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:613)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:804)
Exception in thread "pool-1-thread-1" java.lang.LinkageError:
org.eclipse.aether.transfer.TransferEvent$RequestType
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
at
java.security.AccessController.doPrivileged(AccessController.java:366)
at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:613)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:804)
Downloading:
http://tyrone:2727/nexus/content/repositories/releases/org/apache/maven/plugins/maven-javadoc-plugin/maven-metadata.xml
---------------------------------------------------
constituent[0]: file:/opt/maven-3.1.1/lib/maven-aether-provider-3.1.1.jar
constituent[1]: file:/opt/maven-3.1.1/lib/aether-spi-0.9.0.M2.jar
constituent[2]: file:/opt/maven-3.1.1/lib/cdi-api-1.0.jar
constituent[3]: file:/opt/maven-3.1.1/lib/maven-model-builder-3.1.1.jar
constituent[4]:
file:/opt/maven-3.1.1/lib/maven-repository-metadata-3.1.1.jar
constituent[5]: file:/opt/maven-3.1.1/lib/maven-model-3.1.1.jar
constituent[6]:
file:/opt/maven-3.1.1/lib/aether-connector-wagon-0.9.0.M2.jar
constituent[7]: file:/opt/maven-3.1.1/lib/maven-compat-3.1.1.jar
constituent[8]: file:/opt/maven-3.1.1/lib/maven-settings-builder-3.1.1.jar
constituent[9]: file:/opt/maven-3.1.1/lib/sisu-guice-3.1.3-no_aop.jar
constituent[10]: file:/opt/maven-3.1.1/lib/guava-11.0.2.jar
constituent[11]:
file:/opt/maven-3.1.1/lib/org.eclipse.sisu.inject-0.0.0.M5.jar
constituent[12]:
file:/opt/maven-3.1.1/lib/org.eclipse.sisu.plexus-0.0.0.M5.jar
constituent[13]: file:/opt/maven-3.1.1/lib/slf4j-api-1.7.5.jar
constituent[14]: file:/opt/maven-3.1.1/lib/wagon-http-2.4-shaded.jar
constituent[15]: file:/opt/maven-3.1.1/lib/aether-impl-0.9.0.M2.jar
constituent[16]: file:/opt/maven-3.1.1/lib/jsr305-1.3.9.jar
constituent[17]: file:/opt/maven-3.1.1/lib/wagon-file-2.4.jar
constituent[18]: file:/opt/maven-3.1.1/lib/maven-artifact-3.1.1.jar
constituent[19]: file:/opt/maven-3.1.1/lib/plexus-cipher-1.7.jar
constituent[20]: file:/opt/maven-3.1.1/lib/commons-cli-1.2.jar
constituent[21]: file:/opt/maven-3.1.1/lib/plexus-interpolation-1.19.jar
constituent[22]: file:/opt/maven-3.1.1/lib/maven-settings-3.1.1.jar
constituent[23]: file:/opt/maven-3.1.1/lib/javax.inject-1.jar
constituent[24]: file:/opt/maven-3.1.1/lib/maven-plugin-api-3.1.1.jar
constituent[25]: file:/opt/maven-3.1.1/lib/plexus-utils-3.0.15.jar
constituent[26]: file:/opt/maven-3.1.1/lib/jsr250-api-1.0.jar
constituent[27]: file:/opt/maven-3.1.1/lib/plexus-sec-dispatcher-1.3.jar
constituent[28]: file:/opt/maven-3.1.1/lib/maven-embedder-3.1.1.jar
constituent[29]:
file:/opt/maven-3.1.1/lib/plexus-component-annotations-1.5.5.jar
constituent[30]: file:/opt/maven-3.1.1/lib/wagon-provider-api-2.4.jar
constituent[31]: file:/opt/maven-3.1.1/lib/slf4j-simple-1.7.5.jar
constituent[32]: file:/opt/maven-3.1.1/lib/aether-util-0.9.0.M2.jar
constituent[33]: file:/opt/maven-3.1.1/lib/aopalliance-1.0.jar
constituent[34]: file:/opt/maven-3.1.1/lib/maven-core-3.1.1.jar
constituent[35]: file:/opt/maven-3.1.1/lib/aether-api-0.9.0.M2.jar
constituent[36]: file:/opt/maven-3.1.1/conf/logging/
---------------------------------------------------
Exception in thread "main" java.lang.LinkageError:
org.apache.maven.wagon.PathUtils
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
at
java.security.AccessController.doPrivileged(AccessController.java:366)
at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:143)
at
org.apache.maven.wagon.repository.Repository.<init>(Repository.java:91)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnector.<init>(WagonRepositoryConnector.java:146)
at
org.eclipse.aether.connector.wagon.WagonRepositoryConnectorFactory.newInstance(WagonRepositoryConnectorFactory.java:159)
at
org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:139)
at
org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:613)
at
org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
at java.lang.Thread.run(Thread.java:804)
What am I missing here?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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, it would be greatly appreciated. Thanks.
On 11/29/2013 11:16 PM, Collins Solutions wrote:
> 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]
> ------------------------------------------------------------------------
> Exception in thread "pool-1-thread-3" java.lang.LinkageError:
> org.apache.maven.wagon.PathUtils
> at java.lang.ClassLoader.defineClassImpl(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
> at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
> at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
> at
> java.security.AccessController.doPrivileged(AccessController.java:366)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> at
> org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:143)
> at
> org.apache.maven.wagon.repository.Repository.<init>(Repository.java:91)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector.<init>(WagonRepositoryConnector.java:146)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnectorFactory.newInstance(WagonRepositoryConnectorFactory.java:159)
> at
> org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:139)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:613)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
> at java.lang.Thread.run(Thread.java:804)
> Exception in thread "pool-2-thread-1" java.lang.LinkageError:
> org.eclipse.aether.transfer.TransferEvent$RequestType
> at java.lang.ClassLoader.defineClassImpl(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
> at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
> at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
> at
> java.security.AccessController.doPrivileged(AccessController.java:366)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:613)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
> at java.lang.Thread.run(Thread.java:804)
> Exception in thread "pool-1-thread-1" java.lang.LinkageError:
> org.eclipse.aether.transfer.TransferEvent$RequestType
> at java.lang.ClassLoader.defineClassImpl(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
> at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
> at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
> at
> java.security.AccessController.doPrivileged(AccessController.java:366)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:613)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
> at java.lang.Thread.run(Thread.java:804)
> Downloading:
> http://tyrone:2727/nexus/content/repositories/releases/org/apache/maven/plugins/maven-javadoc-plugin/maven-metadata.xml
> ---------------------------------------------------
> constituent[0]: file:/opt/maven-3.1.1/lib/maven-aether-provider-3.1.1.jar
> constituent[1]: file:/opt/maven-3.1.1/lib/aether-spi-0.9.0.M2.jar
> constituent[2]: file:/opt/maven-3.1.1/lib/cdi-api-1.0.jar
> constituent[3]: file:/opt/maven-3.1.1/lib/maven-model-builder-3.1.1.jar
> constituent[4]:
> file:/opt/maven-3.1.1/lib/maven-repository-metadata-3.1.1.jar
> constituent[5]: file:/opt/maven-3.1.1/lib/maven-model-3.1.1.jar
> constituent[6]:
> file:/opt/maven-3.1.1/lib/aether-connector-wagon-0.9.0.M2.jar
> constituent[7]: file:/opt/maven-3.1.1/lib/maven-compat-3.1.1.jar
> constituent[8]:
> file:/opt/maven-3.1.1/lib/maven-settings-builder-3.1.1.jar
> constituent[9]: file:/opt/maven-3.1.1/lib/sisu-guice-3.1.3-no_aop.jar
> constituent[10]: file:/opt/maven-3.1.1/lib/guava-11.0.2.jar
> constituent[11]:
> file:/opt/maven-3.1.1/lib/org.eclipse.sisu.inject-0.0.0.M5.jar
> constituent[12]:
> file:/opt/maven-3.1.1/lib/org.eclipse.sisu.plexus-0.0.0.M5.jar
> constituent[13]: file:/opt/maven-3.1.1/lib/slf4j-api-1.7.5.jar
> constituent[14]: file:/opt/maven-3.1.1/lib/wagon-http-2.4-shaded.jar
> constituent[15]: file:/opt/maven-3.1.1/lib/aether-impl-0.9.0.M2.jar
> constituent[16]: file:/opt/maven-3.1.1/lib/jsr305-1.3.9.jar
> constituent[17]: file:/opt/maven-3.1.1/lib/wagon-file-2.4.jar
> constituent[18]: file:/opt/maven-3.1.1/lib/maven-artifact-3.1.1.jar
> constituent[19]: file:/opt/maven-3.1.1/lib/plexus-cipher-1.7.jar
> constituent[20]: file:/opt/maven-3.1.1/lib/commons-cli-1.2.jar
> constituent[21]: file:/opt/maven-3.1.1/lib/plexus-interpolation-1.19.jar
> constituent[22]: file:/opt/maven-3.1.1/lib/maven-settings-3.1.1.jar
> constituent[23]: file:/opt/maven-3.1.1/lib/javax.inject-1.jar
> constituent[24]: file:/opt/maven-3.1.1/lib/maven-plugin-api-3.1.1.jar
> constituent[25]: file:/opt/maven-3.1.1/lib/plexus-utils-3.0.15.jar
> constituent[26]: file:/opt/maven-3.1.1/lib/jsr250-api-1.0.jar
> constituent[27]: file:/opt/maven-3.1.1/lib/plexus-sec-dispatcher-1.3.jar
> constituent[28]: file:/opt/maven-3.1.1/lib/maven-embedder-3.1.1.jar
> constituent[29]:
> file:/opt/maven-3.1.1/lib/plexus-component-annotations-1.5.5.jar
> constituent[30]: file:/opt/maven-3.1.1/lib/wagon-provider-api-2.4.jar
> constituent[31]: file:/opt/maven-3.1.1/lib/slf4j-simple-1.7.5.jar
> constituent[32]: file:/opt/maven-3.1.1/lib/aether-util-0.9.0.M2.jar
> constituent[33]: file:/opt/maven-3.1.1/lib/aopalliance-1.0.jar
> constituent[34]: file:/opt/maven-3.1.1/lib/maven-core-3.1.1.jar
> constituent[35]: file:/opt/maven-3.1.1/lib/aether-api-0.9.0.M2.jar
> constituent[36]: file:/opt/maven-3.1.1/conf/logging/
> ---------------------------------------------------
> Exception in thread "main" java.lang.LinkageError:
> org.apache.maven.wagon.PathUtils
> at java.lang.ClassLoader.defineClassImpl(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:306)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:711)
> at java.net.URLClassLoader.access$400(URLClassLoader.java:92)
> at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1159)
> at
> java.security.AccessController.doPrivileged(AccessController.java:366)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:594)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> at
> org.apache.maven.wagon.repository.Repository.setUrl(Repository.java:143)
> at
> org.apache.maven.wagon.repository.Repository.<init>(Repository.java:91)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnector.<init>(WagonRepositoryConnector.java:146)
> at
> org.eclipse.aether.connector.wagon.WagonRepositoryConnectorFactory.newInstance(WagonRepositoryConnectorFactory.java:159)
> at
> org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:139)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:613)
> at
> org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
> at java.lang.Thread.run(Thread.java:804)
>
>
> What am I missing here?
>
>
> ---------------------------------------------------------------------
> 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
Re: Upgrade to 3.1.1 causes problems
Posted by Manfred Moser <ma...@mosabuam.com>.
> On 2 Dec 2013, at 9:35 am, Wayne Fay <wa...@gmail.com> 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 absolutely definitive, so I'd like
>> confirmation of it. Also, what version?
>>
>> Wayne
>
> Indeed.
>
> We migrated from Artifactory to Nexus here, but stuck with the same
> repository URLS, which all have artifactory in the path
You can run Nexus in any context ... including artifactory even that would
be a bit weird ;-)
More info here
http://books.sonatype.com/nexus-book/reference/install-sect-proxy.html
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Stephen Coy <st...@me.com>.
On 2 Dec 2013, at 9:35 am, Wayne Fay <wa...@gmail.com> 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 absolutely definitive, so I'd like
> confirmation of it. Also, what version?
>
> Wayne
Indeed.
We migrated from Artifactory to Nexus here, but stuck with the same repository URLS, which all have “artifactory” in the path…
Steve C
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by sachi <sa...@yahoo.com>.
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.SecureClassLoader.defineClass(SecureClassLoader.java:154)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:777)
at java.net.URLClassLoader.access$400(URLClassLoader.java:96)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1225)
at java.security.AccessController.doPrivileged(AccessController.java:366)
at java.net.URLClassLoader.findClass(URLClassLoader.java:660)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389)
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:159)
I am using maven 3.1.1 and IBM JDK 1.7.1.
I replaced
maven-3.1.1/boot/plexus-classworlds-2.5.1.jar
with
maven-3.0.5/boot/plexus-classworlds-2.4.jar
ran few builds and there are no issues.
FYI
Sachi
--
View this message in context: http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-tp5776875p5792944.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Dan Tran <da...@gmail.com>.
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.rosenvold@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 <an...@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.rosenvold@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 <Co...@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
> > > >
> > > >
> > >
> >
>
Re: Upgrade to 3.1.1 causes problems
Posted by Kristian Rosenvold <kr...@gmail.com>.
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 <an...@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.rosenvold@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 <Co...@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
> > >
> > >
> >
>
Re: Upgrade to 3.1.1 causes problems
Posted by Anders Hammar <an...@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.rosenvold@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 <Co...@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
> >
> >
>
Re: Upgrade to 3.1.1 causes problems
Posted by Kristian Rosenvold <kr...@gmail.com>.
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 <Co...@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
>
>
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@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 <Co...@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
Re: Upgrade to 3.1.1 causes problems
Posted by Stuart McCulloch <mc...@gmail.com>.
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 <Co...@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
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
> ...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
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
...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 problem would be cleaned up. This did not help the situation. I
eventually downgraded my maven instance to version 3.0.5 and this worked
without the way it used to before the upgrade. I do no know why version
3.1.1 does not like me so I will stick with version 3.0.5 for now.
On 12/03/2013 09:52 PM, Wayne Fay wrote:
> 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 "maven linkageerror" and find this
> thread, then follow your steps & resolve it themselves!
>
> Wayne
>
> On Tue, Dec 3, 2013 at 6:09 PM, Collins Solutions
> <Co...@austin.rr.com> wrote:
>> 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
>> building fine again.
>>
>>
>> On 12/02/2013 07:08 PM, Collins Solutions wrote:
>>> 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:/home/rcollins/bin:/usr/lib/jvm/ibm-jdk7.0-6.0/bin:/opt/maven-3.1.1/bin:/opt/ant-1.9.2/bin
>>>
>>> It doesn't look like there is anything out of place. I will let you know
>>> the results of my test on the other machine.
>>>
>>> On 12/02/2013 06:03 PM, Wayne Fay wrote:
>>>>>>>>>> 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
>>>> between some of these jars/classes. But the log shows all your jars
>>>> are under /opt/maven-3.1.1/lib and you're the first person using 3.1.1
>>>> to report any such problem here on the Maven Users list. So it seems
>>>> this is specific to your machine/environment.
>>>>
>>>> Is there maybe something in your PATH or CLASSPATH or another
>>>> environment variable which might be causing your JVM to "see" some
>>>> older/newer jars? Did you install anything in the JVM/JDK itself
>>>> 3.1.0? Is this repeatable on another machine in your environment, or
>>>> specific to just 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
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 "maven linkageerror" and find this
thread, then follow your steps & resolve it themselves!
Wayne
On Tue, Dec 3, 2013 at 6:09 PM, Collins Solutions
<Co...@austin.rr.com> wrote:
> 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
> building fine again.
>
>
> On 12/02/2013 07:08 PM, Collins Solutions wrote:
>>
>> 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:/home/rcollins/bin:/usr/lib/jvm/ibm-jdk7.0-6.0/bin:/opt/maven-3.1.1/bin:/opt/ant-1.9.2/bin
>>
>> It doesn't look like there is anything out of place. I will let you know
>> the results of my test on the other machine.
>>
>> On 12/02/2013 06:03 PM, Wayne Fay wrote:
>>>>>>>>>
>>>>>>>>> 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
>>> between some of these jars/classes. But the log shows all your jars
>>> are under /opt/maven-3.1.1/lib and you're the first person using 3.1.1
>>> to report any such problem here on the Maven Users list. So it seems
>>> this is specific to your machine/environment.
>>>
>>> Is there maybe something in your PATH or CLASSPATH or another
>>> environment variable which might be causing your JVM to "see" some
>>> older/newer jars? Did you install anything in the JVM/JDK itself
>>> 3.1.0? Is this repeatable on another machine in your environment, or
>>> specific to just 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
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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 building fine again.
On 12/02/2013 07:08 PM, Collins Solutions wrote:
> 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:/home/rcollins/bin:/usr/lib/jvm/ibm-jdk7.0-6.0/bin:/opt/maven-3.1.1/bin:/opt/ant-1.9.2/bin
>
>
> It doesn't look like there is anything out of place. I will let you
> know the results of my test on the other machine.
>
> On 12/02/2013 06:03 PM, Wayne Fay wrote:
>>>>>>>> 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
>> between some of these jars/classes. But the log shows all your jars
>> are under /opt/maven-3.1.1/lib and you're the first person using 3.1.1
>> to report any such problem here on the Maven Users list. So it seems
>> this is specific to your machine/environment.
>>
>> Is there maybe something in your PATH or CLASSPATH or another
>> environment variable which might be causing your JVM to "see" some
>> older/newer jars? Did you install anything in the JVM/JDK itself
>> 3.1.0? Is this repeatable on another machine in your environment, or
>> specific to just 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
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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:/home/rcollins/bin:/usr/lib/jvm/ibm-jdk7.0-6.0/bin:/opt/maven-3.1.1/bin:/opt/ant-1.9.2/bin
It doesn't look like there is anything out of place. I will let you
know the results of my test on the other machine.
On 12/02/2013 06:03 PM, Wayne Fay wrote:
>>>>>>> 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
> between some of these jars/classes. But the log shows all your jars
> are under /opt/maven-3.1.1/lib and you're the first person using 3.1.1
> to report any such problem here on the Maven Users list. So it seems
> this is specific to your machine/environment.
>
> Is there maybe something in your PATH or CLASSPATH or another
> environment variable which might be causing your JVM to "see" some
> older/newer jars? Did you install anything in the JVM/JDK itself
> 3.1.0? Is this repeatable on another machine in your environment, or
> specific to just 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
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
>>>>>> 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
between some of these jars/classes. But the log shows all your jars
are under /opt/maven-3.1.1/lib and you're the first person using 3.1.1
to report any such problem here on the Maven Users list. So it seems
this is specific to your machine/environment.
Is there maybe something in your PATH or CLASSPATH or another
environment variable which might be causing your JVM to "see" some
older/newer jars? Did you install anything in the JVM/JDK itself
3.1.0? Is this repeatable on another machine in your environment, or
specific to just one?
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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 this is not absolutely definitive, so I'd like
> confirmation of it. Also, what version?
>
> 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
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
>>>> 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. Also, what version?
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Michael-O <19...@gmx.net>.
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/...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Upgrade to 3.1.1 causes problems
Posted by Collins Solutions <Co...@austin.rr.com>.
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:
<repositories>
<repository>
<id>collins-releases</id>
<name>Collins Releases Repository</name>
<url>http://tyrone:2727/nexus/content/repositories/releases</url>
</repository>
<repository>
<id>collins-snapshots</id>
<name>Collins Snapshot Repository</name>
<url>http://tyrone:2727/nexus/content/repositories/snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>java-net</id>
<name>Java.net Repository</name>
<url>http://download.java.net/maven/2/</url>
</repository>
<repository>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>Apache Repos</id>
<name>Apache Repos</name>
<url>https://repository.apache.org/content/groups/public</url>
</repository>
<repository>
<id>prime-repo</id>
<name>PrimeFaces Maven Repository</name>
<url>http://repository.primefaces.org</url>
<layout>default</layout>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>Apache</id>
<name>Apache Repos</name>
<url>https://repository.apache.org/content/groups/public</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</pluginRepository>
<pluginRepository>
<id>collins-plugin</id>
<name>Collins Internal Plugin Repository</name>
<url>http://tyrone:2727/nexus/content/repositories/releases</url>
</pluginRepository>
<pluginRepository>
<id>Codehaus Snapshots</id>
<url>http://snapshots.repository.codehaus.org/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</pluginRepository>
<pluginRepository>
<id>Apache Snapshots</id>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</pluginRepository>
</pluginRepositories>
Am I missing a repository?
On 11/30/2013 07:40 PM, Wayne Fay wrote:
>> 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
>
> ---------------------------------------------------------------------
> 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
Re: Upgrade to 3.1.1 causes problems
Posted by Wayne Fay <wa...@gmail.com>.
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org