[jira] [Commented] (MSCMPUB-51) Api incompatibility issue using maven-scm-provider-gitexe 2.0.0-M2
[ https://issues.apache.org/jira/browse/MSCMPUB-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626645#comment-17626645 ] Eric Barboni commented on MSCMPUB-51: - Failed to execute goal org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm (default-cli) on project parent: Execution default-cli of goal org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm: java.lang.NoSuchMethodError: org.apache.maven.scm.util.AbstractConsumer: method 'void ()' not found - realm = plugin>org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0 strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy urls[0] = file:/C:/mavenreponobackup2/org/apache/maven/plugins/maven-scm-publish-plugin/3.1.0/maven-scm-publish-plugin-3.1.0.jar urls[1] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-gitexe/2.0.0-M2/maven-scm-provider-gitexe-2.0.0-M2.jar urls[2] = file:/C:/mavenreponobackup2/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar urls[3] = file:/C:/mavenreponobackup2/org/codehaus/plexus/plexus-utils/3.4.2/plexus-utils-3.4.2.jar urls[4] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-git-commons/2.0.0-M2/maven-scm-provider-git-commons-2.0.0-M2.jar urls[5] = file:/C:/mavenreponobackup2/org/apache/maven/release/maven-release-manager/2.5.3/maven-release-manager-2.5.3.jar urls[6] = file:/C:/mavenreponobackup2/org/apache/maven/release/maven-release-api/2.5.3/maven-release-api-2.5.3.jar urls[7] = file:/C:/mavenreponobackup2/org/eclipse/aether/aether-util/1.0.0.v20140518/aether-util-1.0.0.v20140518.jar urls[8] = file:/C:/mavenreponobackup2/junit/junit/3.8.1/junit-3.8.1.jar urls[9] = file:/C:/mavenreponobackup2/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-6/plexus-interactivity-api-1.0-alpha-6.jar urls[10] = file:/C:/mavenreponobackup2/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar urls[11] = file:/C:/mavenreponobackup2/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar urls[12] = file:/C:/mavenreponobackup2/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar urls[13] = file:/C:/mavenreponobackup2/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar urls[14] = file:/C:/mavenreponobackup2/org/apache/maven/shared/maven-invoker/2.2/maven-invoker-2.2.jar urls[15] = file:/C:/mavenreponobackup2/commons-lang/commons-lang/2.4/commons-lang-2.4.jar urls[16] = file:/C:/mavenreponobackup2/commons-cli/commons-cli/1.2/commons-cli-1.2.jar urls[17] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-providers-standard/1.9.4/maven-scm-providers-standard-1.9.4.pom urls[18] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-accurev/1.9.4/maven-scm-provider-accurev-1.9.4.jar urls[19] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-bazaar/1.9.4/maven-scm-provider-bazaar-1.9.4.jar urls[20] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-clearcase/1.9.4/maven-scm-provider-clearcase-1.9.4.jar urls[21] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-cvsexe/1.9.4/maven-scm-provider-cvsexe-1.9.4.jar urls[22] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.9.4/maven-scm-provider-cvs-commons-1.9.4.jar urls[23] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-cvsjava/1.9.4/maven-scm-provider-cvsjava-1.9.4.jar urls[24] = file:/C:/mavenreponobackup2/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar urls[25] = file:/C:/mavenreponobackup2/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar urls[26] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-hg/1.9.4/maven-scm-provider-hg-1.9.4.jar urls[27] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-perforce/1.9.4/maven-scm-provider-perforce-1.9.4.jar urls[28] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-starteam/1.9.4/maven-scm-provider-starteam-1.9.4.jar urls[29] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-synergy/1.9.4/maven-scm-provider-synergy-1.9.4.jar urls[30] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-vss/1.9.4/maven-scm-provider-vss-1.9.4.jar urls[31] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-tfs/1.9.4/maven-scm-provider-tfs-1.9.4.jar urls[32] = file:/C:/mavenreponobackup2/org/apache/maven/scm/maven-scm-provider-integrity/1.9.4/maven-scm-provider-integrity-1.9.4.jar urls[33] = file:/C:/mavenreponobackup2/com/mks/api/mksapi-jar/4.10.9049/mksapi-jar-4.10.9049.jar urls[34] = file:/C:/mavenreponobackup2/org/codeha
[jira] [Created] (MSCMPUB-51) Api incompatibility issue using maven-scm-provider-gitexe 2.0.0-M2
Eric Barboni created MSCMPUB-51: --- Summary: Api incompatibility issue using maven-scm-provider-gitexe 2.0.0-M2 Key: MSCMPUB-51 URL: https://issues.apache.org/jira/browse/MSCMPUB-51 Project: Maven SCM Publish Plugin Issue Type: Bug Affects Versions: 3.1.0 Reporter: Eric Barboni Hi, just tested the provider maven-scm-provider-gitexe:2.0.0-M2 and I get the following issue Execution default-cli of goal org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm: java.lang.NoSuchMethodError: org.apache.maven.scm.util.AbstractConsumer: method 'void ()' not found The version 2.0.0-M1 of maven-scm-provider-gitexe works well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MSHARED-786) jdk8 incompatibility at runtime (NoSuchMethodError)
[ https://issues.apache.org/jira/browse/MSHARED-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725105#comment-16725105 ] Eric Barboni commented on MSHARED-786: -- No I didn't, I just compile Analyzer with the pom provided on a jdk11. And use the resulting running on jdk8. . > jdk8 incompatibility at runtime (NoSuchMethodError) > --- > > Key: MSHARED-786 > URL: https://issues.apache.org/jira/browse/MSHARED-786 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-dependency-analyzer >Affects Versions: maven-dependency-analyzer-1.11.0 >Reporter: Eric Barboni >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Using the maven-dependencies-analyzer 1.11.0 that is compiled with jdk9 lead > to a error if used in jdk8: > java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer > ByteBuffer need to be cast at Buffer for some method. > I'm not sure if it possible to detect that at compile time > Others get the issue too see: https://github.com/apache/felix/pull/114/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-786) jdk8 incompatibility at runtime (NoSuchMethodError)
[ https://issues.apache.org/jira/browse/MSHARED-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MSHARED-786: - Flags: Patch > jdk8 incompatibility at runtime (NoSuchMethodError) > --- > > Key: MSHARED-786 > URL: https://issues.apache.org/jira/browse/MSHARED-786 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-dependency-analyzer >Affects Versions: maven-dependency-analyzer-1.11.0 >Reporter: Eric Barboni >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Using the maven-dependencies-analyzer 1.11.0 that is compiled with jdk9 lead > to a error if used in jdk8: > java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer > ByteBuffer need to be cast at Buffer for some method. > I'm not sure if it possible to detect that at compile time > Others get the issue too see: https://github.com/apache/felix/pull/114/ > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-786) jdk8 incompatibility at runtime (NoSuchMethodError)
Eric Barboni created MSHARED-786: Summary: jdk8 incompatibility at runtime (NoSuchMethodError) Key: MSHARED-786 URL: https://issues.apache.org/jira/browse/MSHARED-786 Project: Maven Shared Components Issue Type: Bug Components: maven-dependency-analyzer Affects Versions: maven-dependency-analyzer-1.11.0 Reporter: Eric Barboni Using the maven-dependencies-analyzer 1.11.0 that is compiled with jdk9 lead to a error if used in jdk8: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer ByteBuffer need to be cast at Buffer for some method. I'm not sure if it possible to detect that at compile time Others get the issue too see: https://github.com/apache/felix/pull/114/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6385) Windows mvn.cmd fail with incorrect command syntax.
Eric Barboni created MNG-6385:
-
Summary: Windows mvn.cmd fail with incorrect command syntax.
Key: MNG-6385
URL: https://issues.apache.org/jira/browse/MNG-6385
Project: Maven
Issue Type: Bug
Components: Command Line
Affects Versions: 3.5.3, 3.5.2, 3.5.0
Reporter: Eric Barboni
Hi, during some test using Apache Netbeans on windows it appears that some cli
can lead to failure of executing mvn.cmd
It was working before on 3.3.9 version.
In the code example (below) if space are removed from path in agentpath section
it works.
Otherwise the arguments are cut during evaluation
and the following syntax incorrect will happen
if not "-agentpath:\"E:\opensource\space" == "" (
Best Regards
{code}
e:\outils\apache-maven-3.5.3\bin\mvn
-Dexec.args="-agentpath:\"E:\opensource\space
netbeans\netbeans\profiler\lib\deployed\jdk16\windows-amd64\profilerinterface.dll\"=\"E:\opensource\space
netbeans\netbeans\profiler\lib\",5140,10 -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=C:\Users\barboni\AppData\Local\NetBeans\Cache\dev\mavencachedirs\2080072884\org-netbeans-modules-profiler
-classpath %classpath com.mycompany.mavenproject23.newClass"
-Dexec.executable="C:\Program Files\Java\jdk1.8.0_162\bin\java.exe"
-Dexec.classpathScope=runtime -DskipTests=true
-Dmaven.ext.class.path="E:\opensource\space
netbeans\netbeans\java\maven-nblib\netbeans-eventspy.jar" -Dfile.encoding=UTF-8
org.codehaus.mojo:exec-maven-plugin:1.5.0:exec
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244169#comment-16244169
]
Eric Barboni commented on MINDEXER-106:
---
[~sewe]
after cloning use the following maven command (-DnexusIndexDirectory must be
configured according to your will and os)
{noformat}
mvn clean install org.codehaus.mojo:nb-repository-plugin:1.4-SNAPSHOT:download
-DnexusIndexDirectory=/tmp/test -DrepositoryUrl=https://repo1.maven.org/maven2
{noformat}
With maven 3.0.5 it works (but it take time)
With maven 3.5.2
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.sonatype.aether.version.VersionScheme
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass
(SelfFirstStrategy.java:50)
at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass
(ClassRealm.java:271)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass
(ClassRealm.java:247)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass
(ClassRealm.java:239)
at org.apache.maven.index.context.IndexUtils.constructArtifactInfo
(IndexUtils.java:111)
at org.apache.maven.index.context.IndexUtils.updateDocument
(IndexUtils.java:135)
at org.apache.maven.index.updater.IndexDataReader.readIndex
(IndexDataReader.java:92)
at org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData
(DefaultIndexUpdater.java:509)
at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory
(DefaultIndexUpdater.java:197)
at org.apache.maven.index.updater.DefaultIndexUpdater.access$300
(DefaultIndexUpdater.java:76)
at
org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile
(DefaultIndexUpdater.java:642)
at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex
(DefaultIndexUpdater.java:862)
at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex
(DefaultIndexUpdater.java:157)
at org.codehaus.mojo.nbm.repository.DownloadIndexMojo.execute
(DownloadIndexMojo.java:152)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.jvnet.hudson.maven3.launcher.Maven35Launcher.main
(Maven35Launcher.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at jenkins.maven3.agent.Maven35Main.launch (Maven35Main.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:139)
at hudson.maven.Maven3Builder.call (Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform (UserRequest.java:205)
at hudson.remoting.UserRequest.perform (UserRequest.java:52)
at hudson.remoting.Request$2.run (Request.java:356)
at hudson.remoting.InterceptingExecutorService$1.call
(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)
at java.lang.Thread.run (Thread.java:748)
{noformat}
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
[jira] [Comment Edited] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241769#comment-16241769
]
Eric Barboni edited comment on MINDEXER-106 at 11/7/17 10:13 AM:
-
Hi, is it an ad hoc plugin you have issue with?
I have issue with this plugin yet:
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
was (Author: skygo):
Hi, is it an hadoc plugin you have issue with?
I have issue with this plugin yet.
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
>
> Key: MINDEXER-106
> URL: https://issues.apache.org/jira/browse/MINDEXER-106
> Project: Maven Indexer
> Issue Type: Bug
>Affects Versions: 5.1.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
>Reporter: Andreas Sewe
>
> It is impossible to use the latest released {{indexer-core}} (version 5.1.1)
> in a mojo executing under a recent version of Maven (3.5.0):
> {noformat}
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/version/InvalidVersionSpecificationException
> at
> org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
> at
> org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
> at
> org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.version.InvalidVersionSpecificationException
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINDEXER-106) ClassNotFoundException (org.sonatype.aether.version.InvalidVersionSpecificationException) under recent Maven versions
[
https://issues.apache.org/jira/browse/MINDEXER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241769#comment-16241769
]
Eric Barboni commented on MINDEXER-106:
---
Hi, is it an hadoc plugin you have issue with?
I have issue with this plugin yet.
https://github.com/mojohaus/nb-repository-plugin
If I use index-core 6.0 SNAPSHOT it works but break with the previous maven
3.0.5.
> ClassNotFoundException
> (org.sonatype.aether.version.InvalidVersionSpecificationException) under
> recent Maven versions
> -
>
> Key: MINDEXER-106
> URL: https://issues.apache.org/jira/browse/MINDEXER-106
> Project: Maven Indexer
> Issue Type: Bug
>Affects Versions: 5.1.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
>Reporter: Andreas Sewe
>
> It is impossible to use the latest released {{indexer-core}} (version 5.1.1)
> in a mojo executing under a recent version of Maven (3.5.0):
> {noformat}
> Caused by: java.lang.NoClassDefFoundError:
> org/sonatype/aether/version/InvalidVersionSpecificationException
> at
> org.apache.maven.index.context.IndexUtils.constructArtifactInfo(IndexUtils.java:111)
> at
> org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:135)
> at
> org.apache.maven.index.updater.IndexDataReader.readIndex(IndexDataReader.java:92)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexData(DefaultIndexUpdater.java:509)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:197)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:76)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:642)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:862)
> at
> org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:157)
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.sonatype.aether.version.InvalidVersionSpecificationException
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MPIR-352) use protocol agnostic url for gravatar
[
https://issues.apache.org/jira/browse/MPIR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Barboni updated MPIR-352:
--
Attachment: gravatar3.diff
I was thinking of the scm:... like url but this is limited for distribution url.
It's better to use {{starsWith()}}
> use protocol agnostic url for gravatar
> ---
>
> Key: MPIR-352
> URL: https://issues.apache.org/jira/browse/MPIR-352
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: team
>Affects Versions: 2.9
>Reporter: Eric Barboni
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 2.10
>
> Attachments: gravatar2.diff, gravatar3.diff, gravatarpir.diff
>
>
> Hi,
> Team page deployed on https server use http scheme for gravatar image that
> lead to partial secure page.
> According to the followin page:
> https://fr.gravatar.com/site/implement/images/ section "Secure Requests"
> I made a little patch to use the protocol agnostic scheme for Team page
> Regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MPIR-352) use protocol agnostic url for gravatar
[ https://issues.apache.org/jira/browse/MPIR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MPIR-352: -- Attachment: gravatar2.diff Another attemp with precomputing of protocol according to project model URL. Fallback to http if https not found in the site url. This make possible to test offline the gravatar images. > use protocol agnostic url for gravatar > --- > > Key: MPIR-352 > URL: https://issues.apache.org/jira/browse/MPIR-352 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: team >Affects Versions: 2.9 >Reporter: Eric Barboni >Assignee: Michael Osipov >Priority: Minor > Fix For: 2.10 > > Attachments: gravatar2.diff, gravatarpir.diff > > > Hi, > Team page deployed on https server use http scheme for gravatar image that > lead to partial secure page. > According to the followin page: > https://fr.gravatar.com/site/implement/images/ section "Secure Requests" > I made a little patch to use the protocol agnostic scheme for Team page > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPIR-352) use protocol agnostic url for gravatar
Eric Barboni created MPIR-352: - Summary: use protocol agnostic url for gravatar Key: MPIR-352 URL: https://issues.apache.org/jira/browse/MPIR-352 Project: Maven Project Info Reports Plugin Issue Type: Improvement Components: team Affects Versions: 2.9 Reporter: Eric Barboni Priority: Minor Fix For: 2.10 Attachments: gravatarpir.diff Hi, Team page deployed on https server use http scheme for gravatar image that lead to partial secure page. According to the followin page: https://fr.gravatar.com/site/implement/images/ section "Secure Requests" I made a little patch to use the protocol agnostic scheme for Team page Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1277) Exceptions stacktrace in test are limited to the test class in 2.19
[ https://issues.apache.org/jira/browse/SUREFIRE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni closed SUREFIRE-1277. -- Resolution: Not A Problem Thanks for the information. Previous behaviour was not respecting parameters usage. > Exceptions stacktrace in test are limited to the test class in 2.19 > > > Key: SUREFIRE-1277 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1277 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.19, 2.19.1 > Environment: Windows 10, java 8 >Reporter: Eric Barboni >Assignee: Tibor Digana > Attachments: surefiretest.zip > > > Hi, > Previous to 2.19, if an execption was raised in tested method the stacktrace > contains trace from the test and tested method. > Now the stacktrace contains only trace from test method, making it > complicated to find the root cause. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1277) Exceptions stacktrace in test are limited to the test class in 2.19
[
https://issues.apache.org/jira/browse/SUREFIRE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Barboni updated SUREFIRE-1277:
---
Attachment: surefiretest.zip
Minimalistic project where you have to change the version of surefire plugin in
the pom.
As a result for Surefire 2.19.2-SNAPSHOT
{code}
testException(com.dummy.surefiretest.DummyTest) Time elapsed: 0 s <<< ERROR!
java.lang.RuntimeException: Failure
at com.dummy.surefiretest.DummyTest.testException(DummyTest.java:22)
{code}
As a result Surefire 2.18.1
{code}
testException(com.dummy.surefiretest.DummyTest) Time elapsed: 0 sec <<< ERROR!
java.lang.RuntimeException: Failure
at com.dummy.surefiretest.Dummy.exception(Dummy.java:15)
at com.dummy.surefiretest.DummyTest.testException(DummyTest.java:22)
{code}
surefire 2.19 make it harder to find root cause
> Exceptions stacktrace in test are limited to the test class in 2.19
>
>
> Key: SUREFIRE-1277
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1277
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.19, 2.19.1
> Environment: Windows 10, java 8
>Reporter: Eric Barboni
> Attachments: surefiretest.zip
>
>
> Hi,
> Previous to 2.19, if an execption was raised in tested method the stacktrace
> contains trace from the test and tested method.
> Now the stacktrace contains only trace from test method, making it
> complicated to find the root cause.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1277) Exceptions stacktrace in test are limited to the test class in 2.19
Eric Barboni created SUREFIRE-1277: -- Summary: Exceptions stacktrace in test are limited to the test class in 2.19 Key: SUREFIRE-1277 URL: https://issues.apache.org/jira/browse/SUREFIRE-1277 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.19.1, 2.19 Environment: Windows 10, java 8 Reporter: Eric Barboni Hi, Previous to 2.19, if an execption was raised in tested method the stacktrace contains trace from the test and tested method. Now the stacktrace contains only trace from test method, making it complicated to find the root cause. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DOXIASITETOOLS-106) Set language for customizable resources
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138103#comment-15138103 ] Eric Barboni commented on DOXIASITETOOLS-106: - Hi, for example in fluido skin maven-themes.css .search-query if I alter the url to the english one: https://www.google.com/cse/static/en/google_custom_search_watermark.gif I may want to generate with the site with french resource https://www.google.com/cse/static/fr/google_custom_search_watermark.gif I'm not sure what strategy may be good to generalize the concept. > Set language for customizable resources > --- > > Key: DOXIASITETOOLS-106 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-106 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site renderer >Affects Versions: 1.6 >Reporter: Eric Barboni > > This idea came from issue MSKINS-118. Because any locale you have the gif > file for google cse will allways be the english one and it may be nice to > have the possibilty to use the locale for customizing resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-314) checkstyle:check should invoke the execution of this plugin's goal "checkstyle" prior to executing itself
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045939#comment-15045939 ] Eric Barboni commented on MCHECKSTYLE-314: -- Hi, I've been mentioned by Michael Osipov on this issue, but I did not see anything on the comment. An issue on jira ? > checkstyle:check should invoke the execution of this plugin's goal > "checkstyle" prior to executing itself > - > > Key: MCHECKSTYLE-314 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-314 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.17 >Reporter: Roman Ivanov >Assignee: Michael Osipov > > I run into problem with using checkstyles goal "checkstyle:check" in > sevntu.checkstyle project > (https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checks/pom.xml#L75) > as it always use default Sun config when I run "checkstyle:check", It took > me a while to figure out why that does not work. > I had a habit and convenience to run in such a ways pmd and findbug, just > "mvn pmd:check", "mvn findbug:check" it is human friendly. > PMD and Findbugs plugins already do this: > http://gleclaire.github.io/findbugs-maven-plugin/check-mojo.html > https://maven.apache.org/plugins/maven-pmd-plugin/check-mojo.html > search for "Invokes the execution of this plugin's goal" > vs > http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html > Problem was also raised at : > http://stackoverflow.com/questions/11106767/maven-checkstylecheck-not-working > Please add support of this, most users are not professionals in Maven. I use > Maven for many years and it took me too much time to find a reason why it > does not work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DOXIASITETOOLS-107) Fix link to plexus page in the doxia-site-renderer web page
[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020975#comment-15020975 ] Eric Barboni commented on DOXIASITETOOLS-107: - yes that's it. I just see that additional to plexus there is a missing link to former codehaus wiki showing a list of skins and tutorial (maybe outdated) https://web.archive.org/web/20150520185520/https://docs.codehaus.org/display/MAVENUSER/Maven+Skins > Fix link to plexus page in the doxia-site-renderer web page > --- > > Key: DOXIASITETOOLS-107 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-107 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Site renderer >Affects Versions: 1.6 > Environment: Web page >Reporter: Eric Barboni >Assignee: Michael Osipov >Priority: Trivial > Fix For: 1.7 > > > Plexus website change and the site-renderer webpage need an update. > Plexus i18n is no more at the level in plexus website; > Plexus utils javadoc need to be generated first see > (https://github.com/codehaus-plexus/plexus-utils/issues/6) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DOXIASITETOOLS-107) Fix link to plexus page in the doxia-site-renderer web page
Eric Barboni created DOXIASITETOOLS-107: --- Summary: Fix link to plexus page in the doxia-site-renderer web page Key: DOXIASITETOOLS-107 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-107 Project: Maven Doxia Sitetools Issue Type: Bug Components: Site renderer Affects Versions: 1.6 Environment: Web page Reporter: Eric Barboni Priority: Trivial Plexus website change and the site-renderer webpage need an update. Plexus i18n is no more at the level in plexus website; Plexus utils javadoc need to be generated first see (https://github.com/codehaus-plexus/plexus-utils/issues/6) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSKINS-118) avoid mixed content block for google search
[
https://issues.apache.org/jira/browse/MSKINS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011224#comment-15011224
]
Eric Barboni commented on MSKINS-118:
-
DOXIASITETOOLS-106 created but not sure of the technical wording.
> avoid mixed content block for google search
> ---
>
> Key: MSKINS-118
> URL: https://issues.apache.org/jira/browse/MSKINS-118
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.4
> Environment: browser
>Reporter: Eric Barboni
> Attachments: firefox-38-https.png, firefox-42-https.png, https.diff,
> https1.diff
>
>
> I see that site using google search and https have content blocked because of
> mixed content.
> {code}
> Blocked loading mixed active content
> "http://cse.google.com/coop/cse/brand?form=search-form";
> {code}
> I tested patch and it solve this issue for cse watermark and script that are
> no more blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (DOXIASITETOOLS-106) Set language for customizable resources
Eric Barboni created DOXIASITETOOLS-106: --- Summary: Set language for customizable resources Key: DOXIASITETOOLS-106 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-106 Project: Maven Doxia Sitetools Issue Type: Improvement Components: Site renderer Affects Versions: 1.6 Reporter: Eric Barboni This idea came from issue MSKINS-118. Because any locale you have the gif file for google cse will allways be the english one and it may be nice to have the possibilty to use the locale for customizing resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSKINS-118) avoid mixed content block for google search
[
https://issues.apache.org/jira/browse/MSKINS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Barboni updated MSKINS-118:
Attachment: https1.diff
Thanks for review, I try to slove the mixed content and I did not even see the
url mismatch. As there is a redirection to
https://cse.google.com/cse/intl/en/images/google_custom_search_watermark.gif, I
guess it's better to use it.
Updated diff file attached
> avoid mixed content block for google search
> ---
>
> Key: MSKINS-118
> URL: https://issues.apache.org/jira/browse/MSKINS-118
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.4
> Environment: browser
>Reporter: Eric Barboni
> Attachments: firefox-38-https.png, firefox-42-https.png, https.diff,
> https1.diff
>
>
> I see that site using google search and https have content blocked because of
> mixed content.
> {code}
> Blocked loading mixed active content
> "http://cse.google.com/coop/cse/brand?form=search-form";
> {code}
> I tested patch and it solve this issue for cse watermark and script that are
> no more blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSKINS-118) avoid mixed content block for google search
[
https://issues.apache.org/jira/browse/MSKINS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Barboni updated MSKINS-118:
Attachment: https.diff
path to site.vm and css
> avoid mixed content block for google search
> ---
>
> Key: MSKINS-118
> URL: https://issues.apache.org/jira/browse/MSKINS-118
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.4
> Environment: browser
>Reporter: Eric Barboni
> Attachments: https.diff
>
>
> I see that site using google search and https have content blocked because of
> mixed content.
> {code}
> Blocked loading mixed active content
> "http://cse.google.com/coop/cse/brand?form=search-form";
> {code}
> I tested patch and it solve this issue for cse watermark and script that are
> no more blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MSKINS-118) avoid mixed content block for google search
Eric Barboni created MSKINS-118:
---
Summary: avoid mixed content block for google search
Key: MSKINS-118
URL: https://issues.apache.org/jira/browse/MSKINS-118
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-1.4
Environment: browser
Reporter: Eric Barboni
I see that site using google search and https have content blocked because of
mixed content.
{code}
Blocked loading mixed active content
"http://cse.google.com/coop/cse/brand?form=search-form";
{code}
I tested patch and it solve this issue for cse watermark and script that are no
more blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNGSITE-244) google custom search search on $sitesearchValue instead of maven.apache.org
[ https://issues.apache.org/jira/browse/MNGSITE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MNGSITE-244: - Attachment: site.xml.patch trivial patch to the issue > google custom search search on $sitesearchValue instead of maven.apache.org > --- > > Key: MNGSITE-244 > URL: https://issues.apache.org/jira/browse/MNGSITE-244 > Project: Maven Project Web Site > Issue Type: Bug > Environment: browser > >Reporter: Eric Barboni >Priority: Trivial > Attachments: site.xml.patch > > > The custom search is not searching into maven site. > seems that site.xml is not complete and should contains > maven.apache.org because the skin is looking for the > value. > Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNGSITE-244) google custom search search on $sitesearchValue instead of maven.apache.org
Eric Barboni created MNGSITE-244: Summary: google custom search search on $sitesearchValue instead of maven.apache.org Key: MNGSITE-244 URL: https://issues.apache.org/jira/browse/MNGSITE-244 Project: Maven Project Web Site Issue Type: Bug Environment: browser Reporter: Eric Barboni Priority: Trivial The custom search is not searching into maven site. seems that site.xml is not complete and should contains maven.apache.org because the skin is looking for the value. Regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MSHARED-409) maven-shared-jar fail to analyse jar containing "new" jdk8 code
Eric Barboni created MSHARED-409: Summary: maven-shared-jar fail to analyse jar containing "new" jdk8 code Key: MSHARED-409 URL: https://jira.codehaus.org/browse/MSHARED-409 Project: Maven Shared Components Issue Type: Bug Components: maven-shared-jar Affects Versions: maven-shared-jar-1.1 Environment: windows 8.1 jdk 8.31 Reporter: Eric Barboni Attachments: jdk8jar.zip, jdk8.patch Maven shared jar fail to analyse jdk8 artifact (containing jdk8 stream ). Apache BCEL raise an exception. I discover this issue by using maven project info report plugin (dependencies section) jdk8.patch contains a unit test expecting to have a true answer to isDebugPresent (as maven compiler generate debug info by default). jdk8jar.zip is a multimode project to reproduce the jar used in the tests. upgrading to bcel 6.0 SNAPSHOT works but as it's not release yet I guess I have to wait :p -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
[ https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated WAGON-409: --- Patch Submitted: Yes > Wagon-webdav-jackrabbit throws Class Not Found Exception. > - > > Key: WAGON-409 > URL: https://jira.codehaus.org/browse/WAGON-409 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.5, 2.6 > Environment: Maven 3.1.1, fedora, jenkins >Reporter: Eric Barboni >Priority: Critical > Attachments: dependenciesfix.patch, log.txt > > > I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy > working project (with version 2.4). > During instantiation of MultiThreadedHttpConnectionManager the LogFactory > class is not available and break deploy. > The removal of dependencies wagon-http-shared after 2.4 seems to be the cause > of the issue. http-shared was providing commons logging as transitive > dependencies ofr jackrabbit. > Best Regards > I copy paste extract from the jenkins logs in attachement. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
[ https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated WAGON-409: --- Attachment: dependenciesfix.patch patch file to add commons log as dependency of webdav > Wagon-webdav-jackrabbit throws Class Not Found Exception. > - > > Key: WAGON-409 > URL: https://jira.codehaus.org/browse/WAGON-409 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.5, 2.6 > Environment: Maven 3.1.1, fedora, jenkins >Reporter: Eric Barboni >Priority: Critical > Attachments: dependenciesfix.patch, log.txt > > > I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy > working project (with version 2.4). > During instantiation of MultiThreadedHttpConnectionManager the LogFactory > class is not available and break deploy. > The removal of dependencies wagon-http-shared after 2.4 seems to be the cause > of the issue. http-shared was providing commons logging as transitive > dependencies ofr jackrabbit. > Best Regards > I copy paste extract from the jenkins logs in attachement. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
[ https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni reopened WAGON-409: Thanks for the information. https://github.com/apache/maven-wagon/blob/master/wagon-providers/wagon-webdav-jackrabbit/pom.xml looking to the pom.xml in the trunk version both org.apache.jackrabbit:jackrabbit-webdav:2.5.2 commons-httpclient:commons-httpclient:3.1 excludes commons logging to avoid classloader conflict webdab-jackrabbit <2.5 the wagon-http-shared was declared in dependencies and had a transitive dependencies to commons loggings. webdav-jackrabbit >= 2.5 wagon-http-shared dep is droped so it miss the commons loggings dep; > Wagon-webdav-jackrabbit throws Class Not Found Exception. > - > > Key: WAGON-409 > URL: https://jira.codehaus.org/browse/WAGON-409 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.5, 2.6 > Environment: Maven 3.1.1, fedora, jenkins >Reporter: Eric Barboni >Priority: Critical > Attachments: log.txt > > > I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy > working project (with version 2.4). > During instantiation of MultiThreadedHttpConnectionManager the LogFactory > class is not available and break deploy. > The removal of dependencies wagon-http-shared after 2.4 seems to be the cause > of the issue. http-shared was providing commons logging as transitive > dependencies ofr jackrabbit. > Best Regards > I copy paste extract from the jenkins logs in attachement. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-386) Documentation links to oracle web site are broken
[ https://jira.codehaus.org/browse/MJAVADOC-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MJAVADOC-386: -- Attachment: fixurl.patch Hi, a patch fixing reference to jdk documentation new url scheme. In site files and also in javadoc of mojo file I use jdk 7 as reference, all previous changes (i.e. whatsnew-1.4.1) can be retrieved. Sun DocCheck is no more available so I link to the generic page. > Documentation links to oracle web site are broken > - > > Key: MJAVADOC-386 > URL: https://jira.codehaus.org/browse/MJAVADOC-386 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.9.1 >Reporter: Benson Margulies > Attachments: fixurl.patch > > > Many links to oracle are not working. > The first example on the javadoc:javadoc page: > http://docs.oracle.com/javase/1.4.2/docs/tooldocs/windows/javadoc.html#J -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINDEXER-77) Upgrade to Lucene 4.1
[ https://jira.codehaus.org/browse/MINDEXER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342089#comment-342089 ] Eric Barboni commented on MINDEXER-77: -- (I'm not having the commit power) Discussion in Apache Archiva dev ML http://www.mail-archive.com/dev@archiva.apache.org/msg02061.html Discussion in Apache Maven dev ML (the thread is a bit hidden by traffic ) http://www.mail-archive.com/dev@maven.apache.org/msg99829.html Sounds interesting for apache archiva and also for Netbeans IDE Is it possible to have more detail on benchmark you use for 50% gain ? I guess, it may help acceptance. > Upgrade to Lucene 4.1 > - > > Key: MINDEXER-77 > URL: https://jira.codehaus.org/browse/MINDEXER-77 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Emmanuel Hugonnet > > Lucene has made a great effort in being quicker and smaller in the 4.x > versions. > Moving to this new version would make maven indexer better -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
[ https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni closed WAGON-409. -- Resolution: Not A Bug Pierre url reformat make it work. This is a hard to find convention in the wagon docs. > Wagon-webdav-jackrabbit throws Class Not Found Exception. > - > > Key: WAGON-409 > URL: https://jira.codehaus.org/browse/WAGON-409 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.5, 2.6 > Environment: Maven 3.1.1, fedora, jenkins >Reporter: Eric Barboni >Priority: Critical > Attachments: log.txt > > > I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy > working project (with version 2.4). > During instantiation of MultiThreadedHttpConnectionManager the LogFactory > class is not available and break deploy. > The removal of dependencies wagon-http-shared after 2.4 seems to be the cause > of the issue. http-shared was providing commons logging as transitive > dependencies ofr jackrabbit. > Best Regards > I copy paste extract from the jenkins logs in attachement. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
[ https://jira.codehaus.org/browse/WAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340562#comment-340562 ] Eric Barboni commented on WAGON-409: Thanks for the informations. It is working now. > Wagon-webdav-jackrabbit throws Class Not Found Exception. > - > > Key: WAGON-409 > URL: https://jira.codehaus.org/browse/WAGON-409 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.5, 2.6 > Environment: Maven 3.1.1, fedora, jenkins >Reporter: Eric Barboni >Priority: Critical > Attachments: log.txt > > > I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy > working project (with version 2.4). > During instantiation of MultiThreadedHttpConnectionManager the LogFactory > class is not available and break deploy. > The removal of dependencies wagon-http-shared after 2.4 seems to be the cause > of the issue. http-shared was providing commons logging as transitive > dependencies ofr jackrabbit. > Best Regards > I copy paste extract from the jenkins logs in attachement. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-409) Wagon-webdav-jackrabbit throws Class Not Found Exception.
Eric Barboni created WAGON-409: -- Summary: Wagon-webdav-jackrabbit throws Class Not Found Exception. Key: WAGON-409 URL: https://jira.codehaus.org/browse/WAGON-409 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 2.6, 2.5 Environment: Maven 3.1.1, fedora, jenkins Reporter: Eric Barboni Priority: Critical Attachments: log.txt I try to upgrade to the 2.6 version of jackrabbit wagon on a previoulsy working project (with version 2.4). During instantiation of MultiThreadedHttpConnectionManager the LogFactory class is not available and break deploy. The removal of dependencies wagon-http-shared after 2.4 seems to be the cause of the issue. http-shared was providing commons logging as transitive dependencies ofr jackrabbit. Best Regards I copy paste extract from the jenkins logs in attachement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-182) [site] download page consistency
[ https://jira.codehaus.org/browse/MNGSITE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MNGSITE-182: - Attachment: download.xml.vm.patch updated to last commited changes > [site] download page consistency > > > Key: MNGSITE-182 > URL: https://jira.codehaus.org/browse/MNGSITE-182 > Project: Maven Project Web Site > Issue Type: Improvement > Environment: n/a >Reporter: Eric Barboni >Priority: Minor > Attachments: download.xml.vm.patch, download.xml.vm.patch > > > a little patch to make download page more consistent in 3 operation > 1) remove the duplicated row for both > maven 3.1.0-alpha1 and 3.0.5 (binary tar.gz) > 2)section 3.1 series the same as others series. > 3) add a paragraph for 3.1 and 3.0.5 as it was for 2.2 and 2.0. Text is to > be reviewed I guess) > regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNGSITE-182) [site] download page consistency
Eric Barboni created MNGSITE-182: Summary: [site] download page consistency Key: MNGSITE-182 URL: https://jira.codehaus.org/browse/MNGSITE-182 Project: Maven Project Web Site Issue Type: Improvement Environment: n/a Reporter: Eric Barboni Priority: Minor Attachments: download.xml.vm.patch a little patch to make download page more consistent in 3 operation 1) remove the duplicated row for both maven 3.1.0-alpha1 and 3.0.5 (binary tar.gz) 2)section 3.1 series the same as others series. 3) add a paragraph for 3.1 and 3.0.5 as it was for 2.2 and 2.0. Text is to be reviewed I guess) regards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-70) external.png is used in css but not present in code base
Eric Barboni created MSKINS-70: -- Summary: external.png is used in css but not present in code base Key: MSKINS-70 URL: https://jira.codehaus.org/browse/MSKINS-70 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.1 Reporter: Eric Barboni Priority: Trivial Attachments: maven-theme.css.patch Proposed patch is to remove reference in css. But can be the other way around adding external.png to code base. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-68) clean for in footer
Eric Barboni created MSKINS-68: -- Summary: clean for in footer Key: MSKINS-68 URL: https://jira.codehaus.org/browse/MSKINS-68 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.1 Environment: web Reporter: Eric Barboni Priority: Minor Attachments: footerxmlclean.patch There are some ugly shown in the generated page. Patch to make output nicer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-55) Website layout broken when browser width is small.
[ https://jira.codehaus.org/browse/MSKINS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305594#comment-305594 ] Eric Barboni commented on MSKINS-55: Hi, is your issue related to the fact that if browser is small the main content is below the left bar ? For that you should remove the following in the css: width: 170px; in the #leftColum of the hama/site/trunk/css/site.css > Website layout broken when browser width is small. > -- > > Key: MSKINS-55 > URL: https://jira.codehaus.org/browse/MSKINS-55 > Project: Maven Skins > Issue Type: Bug > Components: Fluido Skin >Reporter: Edward J. Yoon > > I use new fluido skin for http://hama.apache.org/ > But, there's small layout problem when browser width is small. > Please fix this, and let me know how can I fix this problem urgently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-57) '' in generated head
[ https://jira.codehaus.org/browse/MSKINS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MSKINS-57: --- Attachment: xmlremove.patch add a fix for missing and put meta on top of html output seems now to be html 5 compliant > '' in generated head > -- > > Key: MSKINS-57 > URL: https://jira.codehaus.org/browse/MSKINS-57 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.2.2 >Reporter: Eric Barboni >Priority: Minor > Attachments: xmlremove.patch, xmlremove.patch > > > is generated in final web page. Quick > fix to make it like in stylus skin DOXIA-150. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-57) '' in generated head
Eric Barboni created MSKINS-57: -- Summary: '' in generated head Key: MSKINS-57 URL: https://jira.codehaus.org/browse/MSKINS-57 Project: Maven Skins Issue Type: Improvement Components: Fluido Skin Affects Versions: fluido-1.2.2 Reporter: Eric Barboni Priority: Minor Attachments: xmlremove.patch is generated in final web page. Quick fix to make it like in stylus skin DOXIA-150. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-56) Incoherent doctype and content
Eric Barboni created MSKINS-56: -- Summary: Incoherent doctype and content Key: MSKINS-56 URL: https://jira.codehaus.org/browse/MSKINS-56 Project: Maven Skins Issue Type: Improvement Components: Fluido Skin Affects Versions: fluido-1.2.2 Reporter: Eric Barboni Priority: Minor Attachments: fluidohtml5.patch Hi, fluido is using * some html 5 custom attribute like data-toggle * new html 5 element like footer but fluido still use xhtml as doctype. Fluido skin deserve the new doctype. fix for charset fix a missing type for twitter script -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (WAGON-352) webdav deployment fail with "directory self reference" error on high security firewall
[ https://jira.codehaus.org/browse/WAGON-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated WAGON-352: --- Attachment: webdav1.patch patch to have a property to remove leading .// Allows webdav to work with strong firewall no allowing this: http://target/url/.//file1 > webdav deployment fail with "directory self reference" error on high security > firewall > -- > > Key: WAGON-352 > URL: https://jira.codehaus.org/browse/WAGON-352 > Project: Maven Wagon > Issue Type: Bug > Components: wagon-webdav >Affects Versions: 2.0 > Environment: Windows 7 > or linux fedora >Reporter: Eric Barboni > Attachments: webdav1.patch > > > Hi, > I cannot deploy with webdav on a domain lock by a "super secure" firewall. > It seems related to another issue (Wagon-319) with the ./ in the begining of > the uploaded file > Best Regards > PS: logs > INFO: basic authentication scheme selected > Uploading: .//distribution-management.html to > http://www.irit.fr/ICS/softwares/hamsters/ > Sep 30, 2011 3:10:17 AM org.apache.commons.httpclient.HttpMethodDirector > executeWithRetry > INFO: I/O exception (java.net.SocketException) caught when processing > request: Connection reset -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-134) Update to PMD 4.3 -- allow target to java 7
[ https://jira.codehaus.org/browse/MPMD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287608#comment-287608 ] Eric Barboni commented on MPMD-134: --- Hi Dennis, 2.7-SNAPSHOT working well with 1.7. Thanks a lot > Update to PMD 4.3 -- allow target to java 7 > --- > > Key: MPMD-134 > URL: https://jira.codehaus.org/browse/MPMD-134 > Project: Maven 2.x PMD Plugin > Issue Type: Wish > Components: PMD >Reporter: Eric Barboni >Assignee: Dennis Lundberg > Fix For: 2.7 > > Attachments: CpdReportGenerator.java > > > After patching some source file with new Java 7 diamond operator (i.e. new > HashMap<>()) all reports on this files are broken due to parsing error. > It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all > Java version grammar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-134) Update to PMD 4.3 -- allow target to java 7
[
https://jira.codehaus.org/browse/MPMD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285893#comment-285893
]
Eric Barboni edited comment on MPMD-134 at 12/14/11 8:55 AM:
-
Hi Dennis,
The previous file remove the fail in junit for default configuration.
There is a failing test remaining in CpdReportTest line 132-133:
str = readFile( new File( getBasedir(),
"target/test/unit/custom-configuration/target/site/cpd.html" ) );
assertTrue( str.toLowerCase().indexOf( "private String unusedMethod( String
unusedParam )".toLowerCase() ) != -1 );
I do some testing
with default pmd 4.2.5 UI report contains "private String unusedMethod( String
unusedParam )"
with default pmd 4.3 UI report contains "private String unusedMethod()"
As this configuration is based on a 25 minimumTokens check I would change the
assertion by
assertTrue( str.toLowerCase().indexOf( "private String
unusedMethod(".toLowerCase() ) != -1 );
because we are not checking the duplication of parameter is "out of bounds"
was (Author: skygolanur):
Hi Dennis,
The previous file remove the fail in junit for default configuration.
There is a failing test remaining in CpdReportTest line 132-133:
{{str = readFile( new File( getBasedir(),
"target/test/unit/custom-configuration/target/site/cpd.html" ) );
assertTrue( str.toLowerCase().indexOf( "private String unusedMethod( String
unusedParam )".toLowerCase() ) != -1 );}}
I do some testing
with default pmd 4.2.5 UI report contains * "private String unusedMethod(
String unusedParam )" *
with default pmd 4.3 UI report contains * "private String unusedMethod()" *
> Update to PMD 4.3 -- allow target to java 7
> ---
>
> Key: MPMD-134
> URL: https://jira.codehaus.org/browse/MPMD-134
> Project: Maven 2.x PMD Plugin
> Issue Type: Wish
> Components: PMD
>Reporter: Eric Barboni
> Attachments: CpdReportGenerator.java
>
>
> After patching some source file with new Java 7 diamond operator (i.e. new
> HashMap<>()) all reports on this files are broken due to parsing error.
> It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all
> Java version grammar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-134) Update to PMD 4.3 -- allow target to java 7
[
https://jira.codehaus.org/browse/MPMD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285893#comment-285893
]
Eric Barboni commented on MPMD-134:
---
Hi Dennis,
The previous file remove the fail in junit for default configuration.
There is a failing test remaining in CpdReportTest line 132-133:
{{str = readFile( new File( getBasedir(),
"target/test/unit/custom-configuration/target/site/cpd.html" ) );
assertTrue( str.toLowerCase().indexOf( "private String unusedMethod( String
unusedParam )".toLowerCase() ) != -1 );}}
I do some testing
with default pmd 4.2.5 UI report contains * "private String unusedMethod(
String unusedParam )" *
with default pmd 4.3 UI report contains * "private String unusedMethod()" *
> Update to PMD 4.3 -- allow target to java 7
> ---
>
> Key: MPMD-134
> URL: https://jira.codehaus.org/browse/MPMD-134
> Project: Maven 2.x PMD Plugin
> Issue Type: Wish
> Components: PMD
>Reporter: Eric Barboni
> Attachments: CpdReportGenerator.java
>
>
> After patching some source file with new Java 7 diamond operator (i.e. new
> HashMap<>()) all reports on this files are broken due to parsing error.
> It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all
> Java version grammar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPMD-134) Update to PMD 4.3 -- allow target to java 7
[ https://jira.codehaus.org/browse/MPMD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Barboni updated MPMD-134: -- Attachment: CpdReportGenerator.java new CPDReport generator based on iterator on TokenEntry instead of getFirstMark and getSecondMark Allows more than two duplicate mark. Compatible with 4.2.5 > Update to PMD 4.3 -- allow target to java 7 > --- > > Key: MPMD-134 > URL: https://jira.codehaus.org/browse/MPMD-134 > Project: Maven 2.x PMD Plugin > Issue Type: Wish > Components: PMD >Reporter: Eric Barboni > Attachments: CpdReportGenerator.java > > > After patching some source file with new Java 7 diamond operator (i.e. new > HashMap<>()) all reports on this files are broken due to parsing error. > It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all > Java version grammar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPMD-134) Update to PMD 4.3 -- allow target to java 7
[ https://jira.codehaus.org/browse/MPMD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285054#comment-285054 ] Eric Barboni commented on MPMD-134: --- Hi Dennis According to pmd change logs the CPD algorithm has been rewritten in 4.2.6. Updating the trunk with 4.2.6 break unit test as 4.3 does. Modify (and hopefully fixed)"CPD algorithm thanks to a patch from Juan Jesús García de Soria" impacted class by this patch http://pmd.svn.sourceforge.net/viewvc/pmd?view=revision&revision=7107 Hope it may help. > Update to PMD 4.3 -- allow target to java 7 > --- > > Key: MPMD-134 > URL: https://jira.codehaus.org/browse/MPMD-134 > Project: Maven 2.x PMD Plugin > Issue Type: Wish > Components: PMD >Reporter: Eric Barboni > > After patching some source file with new Java 7 diamond operator (i.e. new > HashMap<>()) all reports on this files are broken due to parsing error. > It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all > Java version grammar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-134) Update to PMD 4.3 -- allow target to java 7
Update to PMD 4.3 -- allow target to java 7 --- Key: MPMD-134 URL: https://jira.codehaus.org/browse/MPMD-134 Project: Maven 2.x PMD Plugin Issue Type: Wish Components: PMD Reporter: Eric Barboni After patching some source file with new Java 7 diamond operator (i.e. new HashMap<>()) all reports on this files are broken due to parsing error. It would be nice to patch the next 2.7 plug-in with 4.3 PMD to support all Java version grammar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (WAGON-352) webdav deployment fail with "directory self reference" error on high security firewall
webdav deployment fail with "directory self reference" error on high security firewall -- Key: WAGON-352 URL: https://jira.codehaus.org/browse/WAGON-352 Project: Maven Wagon Issue Type: Bug Components: wagon-webdav Affects Versions: 2.0 Environment: Windows 7 or linux fedora Reporter: Eric Barboni Hi, I cannot deploy with webdav on a domain lock by a "super secure" firewall. It seems related to another issue (Wagon-319) with the ./ in the begining of the uploaded file Best Regards PS: logs INFO: basic authentication scheme selected Uploading: .//distribution-management.html to http://www.irit.fr/ICS/softwares/hamsters/ Sep 30, 2011 3:10:17 AM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry INFO: I/O exception (java.net.SocketException) caught when processing request: Connection reset -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
