[jira] [Commented] (MJAVADOC-485) Upgrade to commons-lang3
[
https://issues.apache.org/jira/browse/MJAVADOC-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063894#comment-16063894
]
Evgeny Mandrikov commented on MJAVADOC-485:
---
This seems to be useful for Java 9 - while plugin version 2.10.4 works with
b171, it fails with b175 as following:
{noformat}
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T21:39:06+02:00)
Maven home: /home/godin/applications/apache-maven-3.5.0
Java version: 9, vendor: Oracle Corporation
Java home: /home/godin/.java-select/versions/jdk-9+175_linux-x64_bin
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.1.15-gentoo-r1", arch: "amd64", family: "unix"
...
[WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocJar
java.lang.ExceptionInInitializerError
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:195)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
at
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
at
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133)
at
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
at
com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051)
at
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81)
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3116)
at java.base/java.lang.String.substring(String.java:1885)
at
org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1133)
at org.apache.commons.lang.SystemUtils.(SystemUtils.java:818)
at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:195)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at
com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
at
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
at
com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
at
com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:133)
at
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at
com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87)
at
com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
at
com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
[jira] [Commented] (MJAVADOC-485) Upgrade to commons-lang3
[
https://issues.apache.org/jira/browse/MJAVADOC-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077752#comment-16077752
]
Evgeny Mandrikov commented on MJAVADOC-485:
---
[~p_ansell] you're right - for me snapshot version (r1801122) also works with
Java 9 b175. Seems that this is a good side effect of [MJAVADOC-465]. And so
indeed, [~rfscholte], this is not entirely duplicate MJAVADOC-488. This also
means that workaround for version 2.10.4 for Java 9 >= b175 is
{noformat}
org.apache.maven.plugins
maven-javadoc-plugin
2.10.4
commons-lang
commons-lang
2.6
{noformat}
HTH.
> Upgrade to commons-lang3
>
>
> Key: MJAVADOC-485
> URL: https://issues.apache.org/jira/browse/MJAVADOC-485
> Project: Maven Javadoc Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 2.10.4
>Reporter: Philippe Marschall
>
> The plugin is currently on commons-lang 2.6, the most recent version is 3.6.
> [The upgrade |https://commons.apache.org/proper/commons-lang/article3_0.html]
> is fairly trivial expect one point, {{SystemUtils.JAVA_VERSION_FLOAT}} is no
> longer available. For some parts there are easy fixes but for
> {{AbstractJavadocMojo}} the simplest fix seemed to use
> {{JavadocUtil#parseJavadocVersion(String)}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (MJAVADOC-485) Upgrade to commons-lang3
[
https://issues.apache.org/jira/browse/MJAVADOC-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077752#comment-16077752
]
Evgeny Mandrikov edited comment on MJAVADOC-485 at 7/7/17 7:41 AM:
---
[~p_ansell] you're right - for me snapshot version (r1801122) also works with
Java 9 b175. Seems that this is a good side effect of [MJAVADOC-465]. And so
indeed, [~rfscholte], MJAVADOC-488 is not entirely duplicate of this. This also
means that workaround for version 2.10.4 for Java 9 >= b175 is
{noformat}
org.apache.maven.plugins
maven-javadoc-plugin
2.10.4
commons-lang
commons-lang
2.6
{noformat}
HTH.
was (Author: godin):
[~p_ansell] you're right - for me snapshot version (r1801122) also works with
Java 9 b175. Seems that this is a good side effect of [MJAVADOC-465]. And so
indeed, [~rfscholte], this is not entirely duplicate MJAVADOC-488. This also
means that workaround for version 2.10.4 for Java 9 >= b175 is
{noformat}
org.apache.maven.plugins
maven-javadoc-plugin
2.10.4
commons-lang
commons-lang
2.6
{noformat}
HTH.
> Upgrade to commons-lang3
>
>
> Key: MJAVADOC-485
> URL: https://issues.apache.org/jira/browse/MJAVADOC-485
> Project: Maven Javadoc Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 2.10.4
>Reporter: Philippe Marschall
>
> The plugin is currently on commons-lang 2.6, the most recent version is 3.6.
> [The upgrade |https://commons.apache.org/proper/commons-lang/article3_0.html]
> is fairly trivial expect one point, {{SystemUtils.JAVA_VERSION_FLOAT}} is no
> longer available. For some parts there are easy fixes but for
> {{AbstractJavadocMojo}} the simplest fix seemed to use
> {{JavadocUtil#parseJavadocVersion(String)}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSHADE-243) Java 8 type-use annotation breaks relocation
[
https://issues.apache.org/jira/browse/MSHADE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159430#comment-16159430
]
Evgeny Mandrikov commented on MSHADE-243:
-
FWIW the linked issue in ASM has been closed as "invalid", this is actually bug
in {{javac}} - see https://bugs.openjdk.java.net/browse/JDK-8144185 , there is
also more recent discussion in ASM -
http://forge.ow2.org/tracker/?func=detail&atid=100023&aid=317789&group_id=23
> Java 8 type-use annotation breaks relocation
>
>
> Key: MSHADE-243
> URL: https://issues.apache.org/jira/browse/MSHADE-243
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.4.3
>Reporter: Yegor Borovikov
> Labels: annotation, asm, java8
> Attachments: mshade-243.zip
>
>
> When relocation tries to examine a class with type-use annotation for
> remapping it fails in {{org.objectweb.asm.ClassReader.readLabel()}} (in some
> cases).
> This code can be used to reproduce the issue:
> {code:java}
> import org.jetbrains.annotations.Nullable;
> interface Foo { void foo(V x); }
> class FooImpl implements Foo> {
> public void foo(Iterable result) {
> if ("".equals(null)) {
> @Nullable Object o = null;
> o = null; // without a statement here errs at offset 65535
> instead of 11
> }
> }
> }
> {code}
> Running {{mvn package}} (with {{}} in shade configuration) yields:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project
> asm-bug: Error creating shaded jar: Error in ASM processing class
> FooImpl.class: 11 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on
> project asm-bug: Error creating shaded jar: Error in ASM processing class
> FooImpl.class
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 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:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Error in ASM processing class FooImpl.class
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:540)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM
> processing class FooImpl.class
> at
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:450)
> at
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:219)
> at
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:179)
> at
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:454)
> ... 22 more
>
[jira] [Created] (MJAVADOC-588) "includeDependencySources" doesn't work in maven-javadoc-plugin 3.1.0 when all modules have "Automatic-Module-Name"
Evgeny Mandrikov created MJAVADOC-588:
-
Summary: "includeDependencySources" doesn't work in
maven-javadoc-plugin 3.1.0 when all modules have "Automatic-Module-Name"
Key: MJAVADOC-588
URL: https://issues.apache.org/jira/browse/MJAVADOC-588
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Evgeny Mandrikov
Attachments: example.zip
Using
{noformat}
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T20:41:47+02:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 11.0.2, vendor: Oracle Corporation, runtime:
/Users/evgeny.mandrikov/.java-select/versions/openjdk-11.0.2_osx-x64_bin
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
{noformat}
execution of {{mvn package}} fails for attached example with following error
{noformat}
error: too many patched modules (org.example.b,org.example.a), use
--module-source-path
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Created: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging - Key: MNG-5135 URL: https://jira.codehaus.org/browse/MNG-5135 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0.3 Environment: Maven 3.0.3 Reporter: Evgeny Mandrikov As described in SONAR-2626 : aggregator mojo, which requires dependency resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to resolve dependencies, when executed from command-line and build extension with custom packaging declared in sub-module, but not in parent. Declaration of extension in parent allows to workaround problem as well as downgrade to Maven 2.2.1 and execution of "mvn verify sonar:sonar". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated MNG-5135: -- Description: As described in SONAR-2626 : aggregator mojo, which requires dependency resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to resolve dependencies, when executed from command-line and build extension with custom packaging declared in sub-module, but not in parent. Declaration of extension in parent allows to workaround problem as well as downgrade to Maven 2.2.1 and execution of "mvn validate sonar:sonar". (was: As described in SONAR-2626 : aggregator mojo, which requires dependency resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to resolve dependencies, when executed from command-line and build extension with custom packaging declared in sub-module, but not in parent. Declaration of extension in parent allows to workaround problem as well as downgrade to Maven 2.2.1 and execution of "mvn verify sonar:sonar".) > Regression: in some cases aggregator mojo is unable to resolve dependencies > with custom packaging > - > > Key: MNG-5135 > URL: https://jira.codehaus.org/browse/MNG-5135 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.3 > Environment: Maven 3.0.3 >Reporter: Evgeny Mandrikov > > As described in SONAR-2626 : aggregator mojo, which requires dependency > resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to > resolve dependencies, when executed from command-line and build extension > with custom packaging declared in sub-module, but not in parent. Declaration > of extension in parent allows to workaround problem as well as downgrade to > Maven 2.2.1 and execution of "mvn validate sonar:sonar". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-623) Add a configuration mode to be able to use git svn (at least for release plugin)
[ https://jira.codehaus.org/browse/SCM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274078#comment-274078 ] Evgeny Mandrikov commented on SCM-623: -- Seems that this issue is a duplicate of SCM-567 or vise-versa. > Add a configuration mode to be able to use git svn (at least for release > plugin) > > > Key: SCM-623 > URL: https://jira.codehaus.org/browse/SCM-623 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-git >Affects Versions: 1.5 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.6 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-626) TfsChangeLogCommand fails when ScmFileSet contains only basedir
TfsChangeLogCommand fails when ScmFileSet contains only basedir --- Key: SCM-626 URL: https://jira.codehaus.org/browse/SCM-626 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-tfs Affects Versions: 1.5 Reporter: Evgeny Mandrikov See SONARPLUGINS-1291 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5135) Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging
[ https://jira.codehaus.org/browse/MNG-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274373#comment-274373 ] Evgeny Mandrikov commented on MNG-5135: --- Benjamin, thank you! BTW, is there any plans for release of 3.0.4? > Regression: in some cases aggregator mojo is unable to resolve dependencies > with custom packaging > - > > Key: MNG-5135 > URL: https://jira.codehaus.org/browse/MNG-5135 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0.3 > Environment: Maven 3.0.3 >Reporter: Evgeny Mandrikov >Assignee: Benjamin Bentmann > Fix For: 3.0.4 > > > As described in SONAR-2626 : aggregator mojo, which requires dependency > resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to > resolve dependencies, when executed from command-line and build extension > with custom packaging declared in sub-module, but not in parent. Declaration > of extension in parent allows to workaround problem as well as downgrade to > Maven 2.2.1 and execution of "mvn validate sonar:sonar". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-483) Update SCM Perforce Provider to use P4Java
[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280254#comment-280254 ] Evgeny Mandrikov commented on SCM-483: -- Hi Brian, Indeed - this is an interesting info. BTW, do you know reasons why it can't be uploaded to Maven Central repository? > Update SCM Perforce Provider to use P4Java > -- > > Key: SCM-483 > URL: https://jira.codehaus.org/browse/SCM-483 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce >Affects Versions: 1.2 >Reporter: Tom Rodriguez > Fix For: future > > Attachments: maven-scm-perforce-p4java.jar > > > Perforce has developed a new Java Native API for access to perforce called > P4Java. You can access it here: > ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely > reworked API does not require that the p4 client be installed on the system. > The SCM Perforce Provider should be modified to use this new native java API > to eliminate the many issues involved with depending on the p4 executable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-483) Update SCM Perforce Provider to use P4Java
[ https://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280291#comment-280291 ] Evgeny Mandrikov commented on SCM-483: -- Cool! Thank you. > Update SCM Perforce Provider to use P4Java > -- > > Key: SCM-483 > URL: https://jira.codehaus.org/browse/SCM-483 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce >Affects Versions: 1.2 >Reporter: Tom Rodriguez > Fix For: future > > Attachments: maven-scm-perforce-p4java.jar > > > Perforce has developed a new Java Native API for access to perforce called > P4Java. You can access it here: > ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely > reworked API does not require that the p4 client be installed on the system. > The SCM Perforce Provider should be modified to use this new native java API > to eliminate the many issues involved with depending on the p4 executable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MSOURCES-30) Should not output INFO message when maven is run in quiet mode
[ https://jira.codehaus.org/browse/MSOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MSOURCES-30 started by Evgeny Mandrikov. > Should not output INFO message when maven is run in quiet mode > -- > > Key: MSOURCES-30 > URL: https://jira.codehaus.org/browse/MSOURCES-30 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Mauritz Lovgren >Assignee: Evgeny Mandrikov >Priority: Minor > > Currently, the source plugin produces INFO statement for created source jars > even if maven is run in quite mode. > This produces unwanted output to system.out during build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work stopped: (MSOURCES-30) Should not output INFO message when maven is run in quiet mode
[ https://jira.codehaus.org/browse/MSOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MSOURCES-30 stopped by Evgeny Mandrikov. > Should not output INFO message when maven is run in quiet mode > -- > > Key: MSOURCES-30 > URL: https://jira.codehaus.org/browse/MSOURCES-30 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Mauritz Lovgren >Assignee: Evgeny Mandrikov >Priority: Minor > > Currently, the source plugin produces INFO statement for created source jars > even if maven is run in quite mode. > This produces unwanted output to system.out during build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSOURCES-30) Should not output INFO message when maven is run in quiet mode
[
https://jira.codehaus.org/browse/MSOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283314#comment-283314
]
Evgeny Mandrikov commented on MSOURCES-30:
--
Seem that update of plexus-archiver to 2.0.1 (PLXCOMP-129) and plexus-utils to
3.0 doesn't solve this issue :
{noformat}
Apache Maven 2.2.1 (r801777; 2009-08-06 23:16:01+0400)
Java version: 1.6.0_29
Java home: /opt/sun-jdk-1.6.0.29/jre
Default locale: ru_RU, platform encoding: UTF-8
OS name: "linux" version: "2.6.39.3" arch: "i386" Family: "unix"
[INFO] Scanning for projects...
[INFO] snapshot org.apache.maven.plugins:maven-source-plugin:2.1.3-SNAPSHOT:
checking for updates from central
[INFO]
[INFO] Building Sonar :: Plugins :: Findbugs
[INFO]task-segment: [source:jar-no-fork]
[INFO]
[INFO] [source:jar-no-fork {execution: default-cli}]
[INFO] org already added, skipping
[INFO] org/sonar already added, skipping
[INFO] org/sonar/plugins already added, skipping
[INFO] org/sonar/plugins/findbugs already added, skipping
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 5 seconds
[INFO] Finished at: Sat Nov 12 00:54:35 MSK 2011
[INFO] Final Memory: 17M/117M
[INFO]
{noformat}
> Should not output INFO message when maven is run in quiet mode
> --
>
> Key: MSOURCES-30
> URL: https://jira.codehaus.org/browse/MSOURCES-30
> Project: Maven 2.x Source Plugin
> Issue Type: Bug
>Affects Versions: 2.0.4
>Reporter: Mauritz Lovgren
>Assignee: Evgeny Mandrikov
>Priority: Minor
>
> Currently, the source plugin produces INFO statement for created source jars
> even if maven is run in quite mode.
> This produces unwanted output to system.out during build.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-592) Error parsing blame for git
Error parsing blame for git --- Key: SCM-592 URL: http://jira.codehaus.org/browse/SCM-592 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Affects Versions: 1.4 Reporter: Evgeny Mandrikov Fixed version can be found here : http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/blame/ And unit test : http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/blame/FixedGitBlameConsumerTest.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-592) Error parsing blame for git
[ http://jira.codehaus.org/browse/SCM-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249735#action_249735 ] Evgeny Mandrikov commented on SCM-592: -- I'll come back to you with patch today. In fact it would be much simpler for me to have commit access to Maven SCM ;) > Error parsing blame for git > --- > > Key: SCM-592 > URL: http://jira.codehaus.org/browse/SCM-592 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.4 >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.5 > > > Fixed version can be found here : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/blame/ > And unit test : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/blame/FixedGitBlameConsumerTest.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-592) Error parsing blame for git
[ http://jira.codehaus.org/browse/SCM-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-592: - Attachment: SCM-592.patch Patch attached. > Error parsing blame for git > --- > > Key: SCM-592 > URL: http://jira.codehaus.org/browse/SCM-592 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.4 >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.5 > > Attachments: SCM-592.patch > > > Fixed version can be found here : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/blame/ > And unit test : > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/src/test/java/org/apache/maven/scm/provider/git/gitexe/command/blame/FixedGitBlameConsumerTest.java -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-591) Move to Java 1.5
[ http://jira.codehaus.org/browse/SCM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250156#action_250156 ] Evgeny Mandrikov commented on SCM-591: -- Hi Olivier, I've made modifications for Blame and CheckOut commands. Is it ok for you to grab changes from GitHub instead of patches ? If so, then : https://github.com/Godin/maven-scm/tree/SCM-591 > Move to Java 1.5 > > > Key: SCM-591 > URL: http://jira.codehaus.org/browse/SCM-591 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-api >Affects Versions: 1.4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.5 > > > As the main scm consumer is in 1.5 (release plugin), we can move this to 1.5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-595) Allow to use BASE in revision range for changelog command
Allow to use BASE in revision range for changelog command - Key: SCM-595 URL: http://jira.codehaus.org/browse/SCM-595 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-svn Reporter: Evgeny Mandrikov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-595) Allow to use BASE in revision range for changelog command
[ http://jira.codehaus.org/browse/SCM-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-595: - Attachment: SCM-595.patch Patch attached. > Allow to use BASE in revision range for changelog command > - > > Key: SCM-595 > URL: http://jira.codehaus.org/browse/SCM-595 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.5 > > Attachments: SCM-595.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255865#action_255865 ] Evgeny Mandrikov commented on SCM-532: -- Hi Mark, Author is responsible for creation of patch, whereas committer responsible for acceptance of patch, so from my point of view they both responsible for quality of commit. Which means that for quality measures in Sonar it would be better to have access to both values. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-532.diff > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255885#action_255885 ] Evgeny Mandrikov commented on SCM-532: -- Note that this relates not only to balme, but also to changelog, which should include both authors and committers. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-532.diff > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261816#action_261816
]
Evgeny Mandrikov commented on MRESOURCES-99:
I'm not sure that issue should be closed, because definition of a new property
- it's just a workaround for original problem.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SCM-616) Add the blame command to providers matrix
[ http://jira.codehaus.org/browse/SCM-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov closed SCM-616. Resolution: Fixed fixed [rev 1089635|http://svn.apache.org/viewvc?view=revision&revision=1089635] Thanks ! > Add the blame command to providers matrix > - > > Key: SCM-616 > URL: http://jira.codehaus.org/browse/SCM-616 > Project: Maven SCM > Issue Type: Task > Components: documentation >Reporter: Simon Brandhof >Assignee: Evgeny Mandrikov >Priority: Minor > Fix For: 1.6 > > Attachments: blame_site.diff > > > The blame command is not listed in http://maven.apache.org/scm/matrix.html > I checked the presence of GitCommand implementation to know if the command is > functional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGELOG-67) Add parameter to allow errors during build
[
http://jira.codehaus.org/browse/MCHANGELOG-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205356#action_205356
]
Evgeny Mandrikov commented on MCHANGELOG-67:
Is there a progress?
> Add parameter to allow errors during build
> --
>
> Key: MCHANGELOG-67
> URL: http://jira.codehaus.org/browse/MCHANGELOG-67
> Project: Maven 2.x Changelog Plugin
> Issue Type: New Feature
>Reporter: Shelley Baker
>Priority: Minor
>
> Adding a parameter to prevent BUILD ERRORs when an error occurs in the
> changelog plugin could be quite convenient in certain cases. For example,
> when a project is copied or branched temporarily (or initially created), the
> SCM URLs defined in the POM may not always be updated. When the SCM path is
> not found, it causes the entire build to fail.
> {noformat}
> [INFO] Generate "Change Log" report.
> [INFO] Generating changed sets xml to: C:\the-project\target\changelog.xml
> [INFO] Executing: svn --non-interactive log -v -r "{2007-06-25 15:25:29
> +}:{2007-07-26 15:25:29 +}"
> https://scm.url/svn/the.group.id/trunk/the-project/
> [INFO] Working directory: C:\the-project\src\main\java
> [ERROR] Provider message:
> [ERROR] The svn command failed.
> [ERROR] Command output:
> [ERROR] svn: REPORT request failed on
> '/svn/!svn/bc/28239/the.group.id/trunk/the-project'
> svn: '/svn/!svn/bc/28239/the.group.id/trunk/the-project' path not found
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error during page generation
> Embedded error: Error rendering Maven report: An error is occurred during
> changelog command :
> Command failed.
> {noformat}
> An optional boolean parameter such as ${maven.changelog.error.ignore} could
> be quite convenient in such cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209125#action_209125
]
Evgeny Mandrikov commented on MRESOURCES-99:
Workaroung: add following property
{code:title=pom.xml}
${maven.build.timestamp}
{code}
and after that you can reference it within resource.
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
>Affects Versions: 2.3, 2.4
>Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-532) Please add support for blame command
Please add support for blame command Key: SCM-532 URL: http://jira.codehaus.org/browse/SCM-532 Project: Maven SCM Issue Type: New Feature Components: maven-scm-api, maven-scm-provider-bazaar, maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial (hg), maven-scm-provider-svn Reporter: Evgeny Mandrikov I've made an extension for Maven SCM for blame command. This extension currently part of [Sonar SCM Activity Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all of these providers I made unit-tests. It would be nice to include these command into Maven SCM. Source code can be found here: http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209686#action_209686 ] Evgeny Mandrikov commented on SCM-532: -- General question - where I should send it? > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209764#action_209764 ] Evgeny Mandrikov commented on SCM-532: -- Sended. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210890#action_210890 ] Evgeny Mandrikov commented on SCM-532: -- Is there progress? Maybe I can help somehow? > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210895#action_210895 ] Evgeny Mandrikov commented on SCM-532: -- Ok, I'll try to prepare patch. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210897#action_210897 ] Evgeny Mandrikov commented on SCM-532: -- Yes, I know ;) > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210903#action_210903 ] Evgeny Mandrikov commented on SCM-532: -- Code in trunk now Java 1.4 compatible. Is it possible to create branch in maven-scm for me? If not, I'll attach huge patch here. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-532: - Attachment: SCM-532.diff Patch attached. > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-532.diff > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-532) Please add support for blame command
[ http://jira.codehaus.org/browse/SCM-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213574#action_213574 ] Evgeny Mandrikov commented on SCM-532: -- And I can't reproduce this on my Linux box with git 1.6.4.4 > Please add support for blame command > > > Key: SCM-532 > URL: http://jira.codehaus.org/browse/SCM-532 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-api, maven-scm-provider-bazaar, > maven-scm-provider-cvs, maven-scm-provider-git, maven-scm-provider-mercurial > (hg), maven-scm-provider-svn >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-532.diff > > > I've made an extension for Maven SCM for blame command. This extension > currently part of [Sonar SCM Activity > Plugin|http://docs.codehaus.org/display/SONAR/SCM+Activity+Plugin] and > supports Subversion (pure Java too), Git, CVS, Mercurial and Bazaar. For all > of these providers I made unit-tests. It would be nice to include these > command into Maven SCM. Source code can be found here: > http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/maven-scm-ext/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-542) Add blame command to Perforce provider
Add blame command to Perforce provider -- Key: SCM-542 URL: http://jira.codehaus.org/browse/SCM-542 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-perforce Reporter: Evgeny Mandrikov Attachments: SCM-542.diff Patch was tested - see SONARPLUGINS-457 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-542) Add blame command to Perforce provider
[ http://jira.codehaus.org/browse/SCM-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-542: - Attachment: SCM-542.diff > Add blame command to Perforce provider > -- > > Key: SCM-542 > URL: http://jira.codehaus.org/browse/SCM-542 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-perforce >Reporter: Evgeny Mandrikov > Attachments: SCM-542.diff > > > Patch was tested - see SONARPLUGINS-457 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-543) Add blame command to ClearCase provider
Add blame command to ClearCase provider --- Key: SCM-543 URL: http://jira.codehaus.org/browse/SCM-543 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-clearcase Reporter: Evgeny Mandrikov Patch was tested - see SONARPLUGINS-454 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-544) Add blame command to AccuRev provider
Add blame command to AccuRev provider - Key: SCM-544 URL: http://jira.codehaus.org/browse/SCM-544 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-accurev Reporter: Evgeny Mandrikov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-544: - Attachment: SCM-544.diff > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov > Attachments: SCM-544.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-545) Add blame command to TFS provider
Add blame command to TFS provider - Key: SCM-545 URL: http://jira.codehaus.org/browse/SCM-545 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provider-tfs Reporter: Evgeny Mandrikov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-544: - Attachment: SCM-544.diff Sorry, forget to add one thing - new patch attached. > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov > Attachments: SCM-544.diff, SCM-544.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-543) Add blame command to ClearCase provider
[ http://jira.codehaus.org/browse/SCM-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217216#action_217216 ] Evgeny Mandrikov commented on SCM-543: -- As I said in Twitter - on the way. > Add blame command to ClearCase provider > --- > > Key: SCM-543 > URL: http://jira.codehaus.org/browse/SCM-543 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-clearcase >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > > Patch was tested - see SONARPLUGINS-454 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-545) Add blame command to TFS provider
[ http://jira.codehaus.org/browse/SCM-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-545: - Attachment: SCM-545.diff > Add blame command to TFS provider > - > > Key: SCM-545 > URL: http://jira.codehaus.org/browse/SCM-545 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-tfs >Reporter: Evgeny Mandrikov > Attachments: SCM-545.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-543) Add blame command to ClearCase provider
[ http://jira.codehaus.org/browse/SCM-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-543: - Attachment: SCM-543.diff > Add blame command to ClearCase provider > --- > > Key: SCM-543 > URL: http://jira.codehaus.org/browse/SCM-543 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-clearcase >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Attachments: SCM-543.diff > > > Patch was tested - see SONARPLUGINS-454 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-543) Add blame command to ClearCase provider
[ http://jira.codehaus.org/browse/SCM-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217224#action_217224 ] Evgeny Mandrikov commented on SCM-543: -- Patch attached. > Add blame command to ClearCase provider > --- > > Key: SCM-543 > URL: http://jira.codehaus.org/browse/SCM-543 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-clearcase >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Attachments: SCM-543.diff > > > Patch was tested - see SONARPLUGINS-454 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217987#action_217987 ] Evgeny Mandrikov commented on SCM-544: -- Ok, I'll do it. > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-544.diff, SCM-544.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218068#action_218068 ] Evgeny Mandrikov commented on SCM-544: -- Olivier, one question: code from sandbox depends on maven-scm-providers version 1.3, where anything related to BlameCommand unavailable. Can I change parent version to 1.4-SNAPSHOT? > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-544.diff, SCM-544.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220408#action_220408 ] Evgeny Mandrikov commented on SCM-544: -- Yes, I can - where I can find changed version? > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-544.diff, SCM-544.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222383#action_222383 ] Evgeny Mandrikov edited comment on SCM-544 at 5/23/10 2:10 PM: --- Hi Olivier, Could you please also fix scope for maven-scm-test in maven-scm-providers/maven-scm-provider-accurev/pom.xml ? was (Author: godin): Hi Olivier, Could you please also fix scope for maven-scm-test in maven-scm-providers/maven-scm-provider-accurev/pom.xml > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-544-2.patch, SCM-544.diff, SCM-544.diff, > SCM-544.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-544) Add blame command to AccuRev provider
[ http://jira.codehaus.org/browse/SCM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222383#action_222383 ] Evgeny Mandrikov commented on SCM-544: -- Hi Olivier, Could you please also fix scope for maven-scm-test in maven-scm-providers/maven-scm-provider-accurev/pom.xml > Add blame command to AccuRev provider > - > > Key: SCM-544 > URL: http://jira.codehaus.org/browse/SCM-544 > Project: Maven SCM > Issue Type: New Feature > Components: maven-scm-provider-accurev >Reporter: Evgeny Mandrikov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: SCM-544-2.patch, SCM-544.diff, SCM-544.diff, > SCM-544.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-568) Exception No such command 'blame'
Exception No such command 'blame' - Key: SCM-568 URL: http://jira.codehaus.org/browse/SCM-568 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-cvs Affects Versions: 1.4 Reporter: Evgeny Mandrikov Looks like patch for SCM-532 was incomplete in case of CVS providers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SCM-568) Exception No such command 'blame'
[ http://jira.codehaus.org/browse/SCM-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated SCM-568: - Attachment: SCM-568.patch > Exception No such command 'blame' > - > > Key: SCM-568 > URL: http://jira.codehaus.org/browse/SCM-568 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-cvs >Affects Versions: 1.4 >Reporter: Evgeny Mandrikov > Attachments: SCM-568.patch > > > Looks like patch for SCM-532 was incomplete in case of CVS providers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-483) Update SCM Perforce Provider to use P4Java
[ http://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230943#action_230943 ] Evgeny Mandrikov commented on SCM-483: -- As I know p4java not available in central repo. But why not upload it? ;) > Update SCM Perforce Provider to use P4Java > -- > > Key: SCM-483 > URL: http://jira.codehaus.org/browse/SCM-483 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce >Affects Versions: 1.2 >Reporter: Tom Rodriguez > Fix For: future > > Attachments: maven-scm-perforce-p4java.jar > > > Perforce has developed a new Java Native API for access to perforce called > P4Java. You can access it here: > ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely > reworked API does not require that the p4 client be installed on the system. > The SCM Perforce Provider should be modified to use this new native java API > to eliminate the many issues involved with depending on the p4 executable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SCM-483) Update SCM Perforce Provider to use P4Java
[ http://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231469#action_231469 ] Evgeny Mandrikov commented on SCM-483: -- Hi Aaron, I've looked a bit on your patch and I think that this patch requires a lot of refactoring. > Update SCM Perforce Provider to use P4Java > -- > > Key: SCM-483 > URL: http://jira.codehaus.org/browse/SCM-483 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce >Affects Versions: 1.2 >Reporter: Tom Rodriguez > Fix For: future > > Attachments: maven-scm-perforce-p4java.jar > > > Perforce has developed a new Java Native API for access to perforce called > P4Java. You can access it here: > ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely > reworked API does not require that the p4 client be installed on the system. > The SCM Perforce Provider should be modified to use this new native java API > to eliminate the many issues involved with depending on the p4 executable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (SCM-483) Update SCM Perforce Provider to use P4Java
[ http://jira.codehaus.org/browse/SCM-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231469#action_231469 ] Evgeny Mandrikov edited comment on SCM-483 at 8/9/10 9:11 AM: -- Aaron, I've looked a bit on your patch and I think that this patch requires a lot of refactoring. Brian, Thank you for your effort. was (Author: godin): Hi Aaron, I've looked a bit on your patch and I think that this patch requires a lot of refactoring. > Update SCM Perforce Provider to use P4Java > -- > > Key: SCM-483 > URL: http://jira.codehaus.org/browse/SCM-483 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-perforce >Affects Versions: 1.2 >Reporter: Tom Rodriguez > Fix For: future > > Attachments: maven-scm-perforce-p4java.jar > > > Perforce has developed a new Java Native API for access to perforce called > P4Java. You can access it here: > ftp://ftp.perforce.com/perforce/r09.1/bin.java/p4java.zip. This completely > reworked API does not require that the p4 client be installed on the system. > The SCM Perforce Provider should be modified to use this new native java API > to eliminate the many issues involved with depending on the p4 executable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-244) Help mojo generates Javadoc, which is not accepted by JDK 8 doclint
Evgeny Mandrikov created MPLUGIN-244:
Summary: Help mojo generates Javadoc, which is not accepted by JDK
8 doclint
Key: MPLUGIN-244
URL: https://jira.codehaus.org/browse/MPLUGIN-244
Project: Maven 2.x Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 3.2
Reporter: Evgeny Mandrikov
Attachments: reproducer.zip
"mvn clean package" on [^reproducer.zip] leads to:
{noformat}
00:51:47 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.9:jar (default) on project
example: MavenReportException: Error while creating archive:
00:51:47 [ERROR] Exit code: 1 -
/tmp/help/reproducer/target/generated-sources/plugin/example/HelpMojo.java:24:
error: self-closing element not allowed
00:51:47 [ERROR] * Display help information on example.
{noformat}
--
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] Created: (MEAR-105) Unable to set some properties for jboss-app.xml
Unable to set some properties for jboss-app.xml
---
Key: MEAR-105
URL: http://jira.codehaus.org/browse/MEAR-105
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Affects Versions: 2.3.2
Environment: JBoss 5.0.0.GA, JBoss 5.0.1.GA
Reporter: Evgeny Mandrikov
Look at http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd
Missing:
* module-order
* security-domain
* unauthenticated-principal
So, for example:
{code:xml}
maven-ear-plugin
5
strict
java:/jaas/twist
guest
{code}
there is no effect. And generated jboss-app.xml looks like:
{code:xml}
http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd";>
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MEAR-105) Unable to set some properties for jboss-app.xml
[
http://jira.codehaus.org/browse/MEAR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Mandrikov updated MEAR-105:
--
Attachment: patch.diff
Patch attached, also patch modifies test (project-53).
> Unable to set some properties for jboss-app.xml
> ---
>
> Key: MEAR-105
> URL: http://jira.codehaus.org/browse/MEAR-105
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Affects Versions: 2.3.2
> Environment: JBoss 5.0.0.GA, JBoss 5.0.1.GA
>Reporter: Evgeny Mandrikov
> Attachments: patch.diff
>
>
> Look at http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd
> Missing:
> * module-order
> * security-domain
> * unauthenticated-principal
> So, for example:
> {code:xml}
>
> maven-ear-plugin
>
>
> 5
> strict
> java:/jaas/twist
> guest
>
>
>
> {code}
> there is no effect. And generated jboss-app.xml looks like:
> {code:xml}
>
> "-//JBoss//DTD Java EE Application 5.0//EN"
> "http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd";>
>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SUREFIRE-516) Definition of multiple Suite-Files not working
[
http://jira.codehaus.org/browse/SUREFIRE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172732#action_172732
]
Evgeny Mandrikov commented on SUREFIRE-516:
---
This can be done by using one suite file from another:
{code:xml|title=MainSuite.xml}
http://testng.org/testng-1.0.dtd"; >
>
{code}
> Definition of multiple Suite-Files not working
> --
>
> Key: SUREFIRE-516
> URL: http://jira.codehaus.org/browse/SUREFIRE-516
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
>Affects Versions: 2.4.2
> Environment: maven 2.0.9
>Reporter: Andreas Höhmann
>
>
>
> maven-surefire-plugin
>
>
> /src/test/resources/Testsuite1.xml
> /src/test/resources/Testsuite2.xml
> /src/test/resources/Testsuite3.xml
>
>
>
>
> Will raise the error
> [INFO] Surefire report directory:
> d:\ws_sid\spice-sid\sid-base\sid-base-knowledgebase\target\surefire-reports
> org.apache.maven.surefire.booter.SurefireExecutionException: Suite file
> d:\ws_sid\spice-sid\sid-base\sid-base-knowledgeb
> ase\src\test\resources\Testsuite1.xmld:\ws_sid\spice-sid\sid-base\sid-base-knowledgebase\src\test\resources\Testsuite2.xml
>
> is not a valid file; nested exception is
> org.apache.maven.surefire.testset.TestSetFailedException: Suite file d:
> \ws_sid\spice-sid\sid-base\sid-base-knowledgebase\src\test\resources\Testsuite1.xmld:\ws_sid\spice-sid\sid-base\sid-ba
> se-knowledgebase\src\test\resources\Testsuite2.xml is not a valid file
> org.apache.maven.surefire.testset.TestSetFailedException: Suite file
> d:\ws_sid\spice-sid\sid-base\sid-base-knowledgebase
> \src\test\resources\Testsuite1.xmld:\ws_sid\spice-sid\sid-base\sid-base-knowledgebase\src\test\resources\Testsuite2.xml
> is not a valid file
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:129)
> at
> org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
> Workaround (put a ',' behind every suiteXmlFile):
>
>
> maven-surefire-plugin
>
>
> /src/test/resources/Testsuite1.xml,
> /src/test/resources/Testsuite2.xml,
> /src/test/resources/Testsuite3.xml,
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-228) UnpackOptions filtered does not work
[ http://jira.codehaus.org/browse/MASSEMBLY-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Mandrikov updated MASSEMBLY-228: --- Attachment: bug.tar.gz Added example project. > UnpackOptions filtered does not work > > > Key: MASSEMBLY-228 > URL: http://jira.codehaus.org/browse/MASSEMBLY-228 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-1 > Environment: Windows XP with maven 2.0.7 >Reporter: Elid OR >Assignee: Petar Tahchiev > Fix For: 2.2 > > Attachments: bug.tar.gz > > > Here my configuration in my assembly descriptor file : > > > true > > true > > my-groupId:my-artifactId > > And this correctly unpack my dependencies but it does not filter the token in > it. > The token are put in a profile that a activate when build the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
