[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without modifying any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649772#comment-16649772 ] ASF GitHub Bot commented on MENFORCER-142: -- robstoll commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-429721570 I would have use for this as well, when is 3.0.0-M3 released? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Specify enforcer rule in command line without modifying any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.0 > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] robstoll commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
robstoll commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-429721570 I would have use for this as well, when is 3.0.0-M3 released? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MNG-6489) Upgrade Maven Resolver to 1.3.0
[ https://issues.apache.org/jira/browse/MNG-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6489: --- Description: Release Notes - Maven Resolver - Version 1.3.0 Bug * MRESOLVER-45 - Git repo is gone/moved * MRESOLVER-50 - Source repository coordinates incorrect New Feature * MRESOLVER-46 - Add support InputStream/OutputStream transformers Improvement * MRESOLVER-31 - Use the Felix Bundle Plugin to generate OSGi metadata * MRESOLVER-35 - Move dependency collector and friends to subpackage in maven-resolver-impl * MRESOLVER-36 - SLFJ - remove LoggerFactory from dependency injection * MRESOLVER-42 - Use pre-compiled pattern in DefaultArtifact constructor * MRESOLVER-47 - Link to older Aether Wiki in Eclipse on front page * MRESOLVER-48 - Add default Travis CI configuration for Java 7, 8, 10 Task * MRESOLVER-44 - switch from Git-WIP to Gitbox > Upgrade Maven Resolver to 1.3.0 > --- > > Key: MNG-6489 > URL: https://issues.apache.org/jira/browse/MNG-6489 > Project: Maven > Issue Type: Dependency upgrade > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.5.4 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.6.0 > > > Release Notes - Maven Resolver - Version 1.3.0 > Bug > * MRESOLVER-45 - Git repo is gone/moved > * MRESOLVER-50 - Source repository coordinates incorrect > New Feature > * MRESOLVER-46 - Add support InputStream/OutputStream transformers > Improvement > * MRESOLVER-31 - Use the Felix Bundle Plugin to generate OSGi metadata > * MRESOLVER-35 - Move dependency collector and friends to subpackage in > maven-resolver-impl > * MRESOLVER-36 - SLFJ - remove LoggerFactory from dependency injection > * MRESOLVER-42 - Use pre-compiled pattern in DefaultArtifact constructor > * MRESOLVER-47 - Link to older Aether Wiki in Eclipse on front page > * MRESOLVER-48 - Add default Travis CI configuration for Java 7, 8, 10 > Task > * MRESOLVER-44 - switch from Git-WIP to Gitbox -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPMD-269) Display PMD version that is being used
[ https://issues.apache.org/jira/browse/MPMD-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MPMD-269: Description: Since you can upgrade the PMD version at runtime ([https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html|https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html)] ) it would be nice, if the actual version of PMD is output as INFO. Note: the version is already in the xml report. was: Since you can upgrade the PMD version at runtime ([https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html)], it would be nice, if the actual version of PMD is output as INFO. Note: the version is already in the xml report. > Display PMD version that is being used > -- > > Key: MPMD-269 > URL: https://issues.apache.org/jira/browse/MPMD-269 > Project: Maven PMD Plugin > Issue Type: New Feature > Components: CPD, PMD >Reporter: Andreas Dangel >Priority: Major > > Since you can upgrade the PMD version at runtime > ([https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html|https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html)] > ) it would be nice, if the actual version of PMD is output as INFO. > > Note: the version is already in the xml report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1580) org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
[ https://issues.apache.org/jira/browse/SUREFIRE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649697#comment-16649697 ] Aviral Jain commented on SUREFIRE-1580: --- [~tibor17] I tried to find the Dump logs but unable to get it, could you please guide me to find the same. > org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM > terminated without properly saying goodbye. VM crash or System.exit called? > --- > > Key: SUREFIRE-1580 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1580 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.22.0 > Environment: Windows 10 >Reporter: Aviral Jain >Priority: Major > Labels: windows > Original Estimate: 72h > Remaining Estimate: 72h > > Hi,I have been following SUREFIRE-1479 but it did't help, I am using System > with below config . > *Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; > 2018-06-18T00:03:14+05:30)* > *Maven home: C:\installations\apache-maven-3.5.4\bin\..* > *Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: C:\Program > Files\Java\jdk1.8.0_171\jre* > *Default locale: en_IN, platform encoding: Cp1252* > *OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"* > > +I Have updated Surefire plugin to 2.22.0 , but still getting the same error > intermittently , could you please suggest something. Detailed error is shown > below:+ > [ERROR] Process Exit Code: 0 > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The > forked VM terminated without properly saying goodbye. VM crash or System.exit > called? > [ERROR] Command was cmd.exe /X /C ""C:\Program > Files\Java\jdk1.8.0_171\jre\bin\java" > -javaagent:C:\\Users\\KGNM8758\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.1\\org.jacoco.agent-0.8.1-runtime.jar=destfile=C:\\Users\\KGNM8758\\Documents\\workspace-sts\\aqp\\grp-adapter\\grp-adapter-dao\\target > jacoco.exec -jar > C:\Users\KGNM8758\AppData\Local\Temp\surefire7645910913045597760\surefirebooter5430497550588506328.jar > C:\Users\KGNM8758\AppData\Local\Temp\surefire7645910913045597760 > 2018-10-03T11-17-35_122-jvmRun1 surefire7524786931499094532tmp > surefire_0864055822511437653tmp" > [ERROR] Process Exit Code: 0 > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278) > [ERROR] at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1194) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1022) > [ERROR] at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:868) > [ERROR] at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) > [ERROR] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > [ERROR] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) > [ERROR] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) > [ERROR] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > [ERROR] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > [ERROR] at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56) > [ERROR] at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > [ERROR] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305) > [ERROR] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192) > [ERROR] at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105) > [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:954) > [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:192) > [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [ERROR] at > sun.reflect.
[jira] [Updated] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1584: --- Labels: junit5 (was: ) > Rerun Failing Tests with JUnit 5 > > > Key: SUREFIRE-1584 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1584 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Tic Tac >Priority: Major > Labels: junit5 > > The very useful feature for integration tests ¨[Rerun Failing > Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨ > is currently only supported for the very outdated JUnit 4. > The documentation says: ¨This feature is supported only for JUnit 4.x.¨ > Can you please support this feature for JUnit 5.3 or later? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1584) Rerun Failing Tests with JUnit 5
[ https://issues.apache.org/jira/browse/SUREFIRE-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649496#comment-16649496 ] Tibor Digana commented on SUREFIRE-1584: [~sormu...@gmx.de] Do you think this feature can be supported? > Rerun Failing Tests with JUnit 5 > > > Key: SUREFIRE-1584 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1584 > Project: Maven Surefire > Issue Type: New Feature > Components: JUnit 5.x support, Maven Surefire Report Plugin >Affects Versions: 2.22.0 >Reporter: Tic Tac >Priority: Major > > The very useful feature for integration tests ¨[Rerun Failing > Tests|https://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html]¨ > is currently only supported for the very outdated JUnit 4. > The documentation says: ¨This feature is supported only for JUnit 4.x.¨ > Can you please support this feature for JUnit 5.3 or later? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names
[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649494#comment-16649494 ] Tibor Digana commented on SUREFIRE-1546: [~OKrutova] [~sor] This week we released a new version 2.22.1 and now we are busy with oss activities in Maven and JUnit5. It's truth that we have a code for this feature in a branch but we are in progress with coding it and making code review. We need to meet on Slack and continue. > JUnit 5 runner does not honor JUnit 5 display names > --- > > Key: SUREFIRE-1546 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1546 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 5.x support >Affects Versions: 2.22.0 >Reporter: Romain Manni-Bucau >Assignee: Christian Stein >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M1 > > > JUnit 5 runner should respect the test @DisplayName instead of displaying the > classname if any is defined. Seems last release doesn't support that feature > of JUnit 5 making the console output and reports not the expected ones. > > Origin: https://github.com/junit-team/junit5/issues/990 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-273) Dependency jar with rules fails only with SNAPSHOT version
[
https://issues.apache.org/jira/browse/MPMD-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649492#comment-16649492
]
Lee Meador commented on MPMD-273:
-
There is no section
> Dependency jar with rules fails only with SNAPSHOT version
> --
>
> Key: MPMD-273
> URL: https://issues.apache.org/jira/browse/MPMD-273
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.10.0
> Environment: Jenkins scripted build job calls Maven running on RHEL 7
> Linux build agents controlled by Jenkins 2.73. Java 8.
>Reporter: Lee Meador
>Priority: Major
>
> One build job creates a coding-standards jar containing PMD rulesets and I
> have run that build with and without SNAPSHOT for version 0.0.2. If I go to
> my Nexus GUI and search, I see the 0.0.2 version and about 8 SNAPSHOT
> versions with different dates and times. 0.0.2 is in the releases repo and
> 0.0.2-SNAPSHOT(s) are in the snapshots repo.
> I have settings.xml set to point to our the public Nexus 3 repository which
> proxies to Maven Central and several other repos both open source and
> internal to our company. The releases repo is included in public. The
> snapshot repo is not included in public, this proxy repo.
> This is the mirrorOf tag in settings.xml.
> {{ !nexus-snapshots,*}}
> For another build job, I have a tag in the pom pointing to our
> snapshot repo with snapshot enabled and releases NOT enabled. This tag is
> there to give it an id that works with the mirroring:
> {{ nexus-snapshots}}
> Other snapshot versions of things needed when compiling the code are found by
> maven.
> I configure the maven pmd plugin thusly:
> {quote}{{}}
> {{ org.apache.maven.plugins}}
> {{ maven-pmd-plugin}}
> {{ }}
> {{ }}
> {{ }}
> {{ check}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ utf-8}}
> {{ 100}}
> {{ 1.8}}
> {{ 3}}
> {{ true}}
> {{ }}
> {{ pmd-config2.xml}}
> {{ }}
> {{ }}
> {{ }}
> {{ }}
> {{ com.aa.crewtech.tools}}
> {{ coding-standards}}
> {{ ${coding-standards.version}}}
> {{ }}
> {{ }}
> {{ }}{quote}
> If I run my build and the property coding-standards.version has the value
> 0.0.2 everything works.
> If coding-standards.version has the value 0.0.2-SNAPSHOT it fails with this
> error:
> _ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd (pmd) on project
> SqlTool: Execution pmd of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0:pmd failed: Plugin
> org.apache.maven.plugins:maven-pmd-plugin:3.10.0 or one of its dependencies
> could not be resolved: Could not find artifact
> com.my.company:coding-standards:jar:0.0.2-SNAPSHOT in nexus
> ([https://nexusread.mycompany.com/repository/public/|https://nexusread.aa.com/repository/OT-public/])
> -> [Help 1]_
> All these builds actually run in my Jenkins with all the code under source
> control and its all repeatable. SNAPSHOT version for the ruleset jar fails.
> Non-SNAPSHOT version works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MNG-6491) Upgrade commons-lang3 to 3.8.1
[ https://issues.apache.org/jira/browse/MNG-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6491. -- Resolution: Fixed Assignee: Hervé Boutemy dependency upgraded: the build now works with JDK11 removing commons-lang3 dependency can be done in the future (need another issue), to avoid adding 490kB library to Maven binary, while just using a few methods: test code can still use the dependency as test scope > Upgrade commons-lang3 to 3.8.1 > -- > > Key: MNG-6491 > URL: https://issues.apache.org/jira/browse/MNG-6491 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Hervé Boutemy >Priority: Trivial > Fix For: 3.6.0 > > > Upgrade to latest version compatible with Java 11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6491) Upgrade commons-lang3 to 3.8.1
[ https://issues.apache.org/jira/browse/MNG-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6491: --- Fix Version/s: (was: 3.6.0-candidate) 3.6.0 > Upgrade commons-lang3 to 3.8.1 > -- > > Key: MNG-6491 > URL: https://issues.apache.org/jira/browse/MNG-6491 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.0 > > > Upgrade to latest version compatible with Java 11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6491) Upgrade commons-lang3 to 3.8.1
[ https://issues.apache.org/jira/browse/MNG-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649446#comment-16649446 ] Hervé Boutemy commented on MNG-6491: while digging the issue, it's not really "latest version compatible with Java 11" but "a newer version which is Java 10 compatible (version 3.5 has an issue under Java 10: LANG-1365)" but the issue under Java 10 does not affect Maven: it is only in test code (which uses the affected isJavaVersionAtLeast API)... but let's just upgrade from 3.5 to 3.8.1: IIUC, that won't change Maven prerequisites, and Maven build will finally not fail any more under Java 11 (= in the end, the expected benefit as I understand it now) > Upgrade commons-lang3 to 3.8.1 > -- > > Key: MNG-6491 > URL: https://issues.apache.org/jira/browse/MNG-6491 > Project: Maven > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Trivial > Fix For: 3.6.0-candidate > > > Upgrade to latest version compatible with Java 11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-272) Support ignoreAnnotations options for CPD
[
https://issues.apache.org/jira/browse/MPMD-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649363#comment-16649363
]
Hudson commented on MPMD-272:
-
Build unstable in Jenkins: Maven TLP » maven-pmd-plugin » master #58
See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/58/
> Support ignoreAnnotations options for CPD
> -
>
> Key: MPMD-272
> URL: https://issues.apache.org/jira/browse/MPMD-272
> Project: Maven PMD Plugin
> Issue Type: New Feature
> Components: CPD
>Reporter: Andreas Dangel
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Major
> Fix For: 3.11.0
>
>
> CPD for Java supports the option `ignoreAnnotations`:
> {quote}
> --ignore-annotations: Ignore language annotations when comparing text
> {quote}
> https://pmd.github.io/pmd-6.8.0/pmd_userdocs_cpd.html#cli-options
> We support already `ignoreLiterals` and `ignoreIdentifiers`.
> See also
> https://stackoverflow.com/questions/52441537/how-can-i-ignore-annotations-when-using-maven-cpd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPMD-272) Support ignoreAnnotations options for CPD
[
https://issues.apache.org/jira/browse/MPMD-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MPMD-272.
---
Resolution: Fixed
> Support ignoreAnnotations options for CPD
> -
>
> Key: MPMD-272
> URL: https://issues.apache.org/jira/browse/MPMD-272
> Project: Maven PMD Plugin
> Issue Type: New Feature
> Components: CPD
>Reporter: Andreas Dangel
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Major
> Fix For: 3.11.0
>
>
> CPD for Java supports the option `ignoreAnnotations`:
> {quote}
> --ignore-annotations: Ignore language annotations when comparing text
> {quote}
> https://pmd.github.io/pmd-6.8.0/pmd_userdocs_cpd.html#cli-options
> We support already `ignoreLiterals` and `ignoreIdentifiers`.
> See also
> https://stackoverflow.com/questions/52441537/how-can-i-ignore-annotations-when-using-maven-cpd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-272) Support ignoreAnnotations options for CPD
[
https://issues.apache.org/jira/browse/MPMD-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) updated MPMD-272:
Fix Version/s: 3.11.0
> Support ignoreAnnotations options for CPD
> -
>
> Key: MPMD-272
> URL: https://issues.apache.org/jira/browse/MPMD-272
> Project: Maven PMD Plugin
> Issue Type: New Feature
> Components: CPD
>Reporter: Andreas Dangel
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Major
> Fix For: 3.11.0
>
>
> CPD for Java supports the option `ignoreAnnotations`:
> {quote}
> --ignore-annotations: Ignore language annotations when comparing text
> {quote}
> https://pmd.github.io/pmd-6.8.0/pmd_userdocs_cpd.html#cli-options
> We support already `ignoreLiterals` and `ignoreIdentifiers`.
> See also
> https://stackoverflow.com/questions/52441537/how-can-i-ignore-annotations-when-using-maven-cpd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MPMD-272) Support ignoreAnnotations options for CPD
[
https://issues.apache.org/jira/browse/MPMD-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) reassigned MPMD-272:
---
Assignee: Olivier Lamy (*$^¨%`£)
> Support ignoreAnnotations options for CPD
> -
>
> Key: MPMD-272
> URL: https://issues.apache.org/jira/browse/MPMD-272
> Project: Maven PMD Plugin
> Issue Type: New Feature
> Components: CPD
>Reporter: Andreas Dangel
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Major
> Fix For: 3.11.0
>
>
> CPD for Java supports the option `ignoreAnnotations`:
> {quote}
> --ignore-annotations: Ignore language annotations when comparing text
> {quote}
> https://pmd.github.io/pmd-6.8.0/pmd_userdocs_cpd.html#cli-options
> We support already `ignoreLiterals` and `ignoreIdentifiers`.
> See also
> https://stackoverflow.com/questions/52441537/how-can-i-ignore-annotations-when-using-maven-cpd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
