[jira] [Updated] (MSITE-453) Add new lifecycle bindings for "maven-skin" packaging
[ https://issues.apache.org/jira/browse/MSITE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSITE-453: Summary: Add new lifecycle bindings for "maven-skin" packaging (was: Add new lifecylce mapping "maven-skin") > Add new lifecycle bindings for "maven-skin" packaging > - > > Key: MSITE-453 > URL: https://issues.apache.org/jira/browse/MSITE-453 > Project: Maven Site Plugin > Issue Type: New Feature >Reporter: Benjamin Bentmann >Priority: Minor > Fix For: backlog > > Attachments: new-lifecycle-mappings.patch > > > Currently, creating a custom skin for Maven is done by a project with > packaging "jar". The attached patch intents to introduce an individual > lifecycle mapping named "maven-skin" for this purpose. > Why that? I consider the re-usage of the "jar" packaging an abuse for the > case of building a Maven skin. On the one hand, the "jar" packaging does too > much. Skins usually do not get compiled or unit-tested, do they? Since any > unused plugin invocation is an unnecessary risk of a build failure (sorry to > say), I would appreciate a lifecycle mapping that is not overdressed. On the > other hand, I could image that skins required some additional processing some > day like a check whether all required images are present in the skin or > whether the CSS references unknown IDs/names. Having a distinct lifecylcle > mapping in the Maven Core would allow for a central definition of the build > steps instead of requiring all users to extend the "jar" packaging. > Especially for the first reason, i.e. having a packaging that does not more > than required, the patch also defines a "resources" packaging. Such a > packaging is intended for JARs that just contain resources one wants to share > with other projects like rulesets for PMD, Checkstyle, etc. The lifecylcle > mappings "resources" and "maven-skin" are identiical (now) but I consider it > a bad practice to merge different use-cases just because they happen to be > equal by coindicence. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-257.
-
Resolution: Fixed
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
>
> [https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
>
> [https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
> Pmd allow to skip warning is "-nocahe" is defined.
>
> [https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
> Detected:
> {code:java}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
> no WARNING 'This analysis could be faster ...' when *analysisCache=false*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-257:
Component/s: PMD
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
>
> [https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
>
> [https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
> Pmd allow to skip warning is "-nocahe" is defined.
>
> [https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
> Detected:
> {code:java}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
> no WARNING 'This analysis could be faster ...' when *analysisCache=false*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-257.
---
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
>
> [https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
>
> [https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
> Pmd allow to skip warning is "-nocahe" is defined.
>
> [https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
> Detected:
> {code:java}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
> no WARNING 'This analysis could be faster ...' when *analysisCache=false*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-252) Upgrade parent to 31
[ https://issues.apache.org/jira/browse/MPMD-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-252: Description: Release notes for 31: [https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12335846&styleName=Text] Issues: [https://issues.apache.org/jira/projects/MPOM/versions/12335846] > Upgrade parent to 31 > > > Key: MPMD-252 > URL: https://issues.apache.org/jira/browse/MPMD-252 > Project: Maven PMD Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.10.0 > > > Release notes for 31: > [https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12335846&styleName=Text] > Issues: [https://issues.apache.org/jira/projects/MPOM/versions/12335846] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456818#comment-16456818
]
Hudson commented on MPMD-257:
-
Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #27
See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/27/
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
>
> [https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
>
> [https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
> Pmd allow to skip warning is "-nocahe" is defined.
>
> [https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
> Detected:
> {code:java}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
> no WARNING 'This analysis could be faster ...' when *analysisCache=false*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (MPMD-261) Upgrade to PMD 6.2.0
[ https://issues.apache.org/jira/browse/MPMD-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-261. - Resolution: Fixed > Upgrade to PMD 6.2.0 > > > Key: MPMD-261 > URL: https://issues.apache.org/jira/browse/MPMD-261 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MPMD-261) Upgrade to PMD 6.2.0
[ https://issues.apache.org/jira/browse/MPMD-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-261. --- > Upgrade to PMD 6.2.0 > > > Key: MPMD-261 > URL: https://issues.apache.org/jira/browse/MPMD-261 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-257:
Description:
in plugn where is property
[https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
that suppose to enable/disable cache
but it is used only to allow set for cache location:
[https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
Pmd allow to skip warning is "-nocahe" is defined.
[https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
Detected:
{code:java}
$ mvn pmd:pmd -Dpmd.analysisCache=false
...
[WARNING] This analysis could be faster, please consider using Incremental
Analysis:
https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
..
{code}
Expected: no WARNING in output
no WARNING 'This analysis could be faster ...' when *analysisCache=false*
was:
in plugn where is property
https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache
that suppose to enable/disable cache
but it is used only to allow set for cache location:
https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678
Pmd allow to skip warning is "-nocahe" is defined.
https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300
Detected:
{code}
$ mvn pmd:pmd -Dpmd.analysisCache=false
...
[WARNING] This analysis could be faster, please consider using Incremental
Analysis:
https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
..
{code}
Expected: no WARNING in output
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
>
> [https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache]
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
>
> [https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678]
> Pmd allow to skip warning is "-nocahe" is defined.
>
> [https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300]
> Detected:
> {code:java}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
> no WARNING 'This analysis could be faster ...' when *analysisCache=false*
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPMD-257) Allow to disable analysisCache completely, avoid warnings
[
https://issues.apache.org/jira/browse/MPMD-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel updated MPMD-257:
Summary: Allow to disable analysisCache completely, avoid warnings (was:
Allow skip WARNING 'This analysis could be faster ...' by analysisCache=false)
> Allow to disable analysisCache completely, avoid warnings
> -
>
> Key: MPMD-257
> URL: https://issues.apache.org/jira/browse/MPMD-257
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Roman Ivanov
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
>
> in plugn where is property
> https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#analysisCache
> that suppose to enable/disable cache
> but it is used only to allow set for cache location:
> https://github.com/apache/maven-pmd-plugin/blob/89687854bc1c965f26adbc78410f75e631f66088/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java#L678
> Pmd allow to skip warning is "-nocahe" is defined.
> https://github.com/pmd/pmd/blob/451815bf0a790805a6a38c1c8bfe798f2a5f04bd/pmd-core/src/main/java/net/sourceforge/pmd/PMD.java#L300
> Detected:
> {code}
> $ mvn pmd:pmd -Dpmd.analysisCache=false
> ...
> [WARNING] This analysis could be faster, please consider using Incremental
> Analysis:
> https://pmd.github.io/pmd-6.1.0/pmd_userdocs_getting_started.html#incremental-analysis
> ..
> {code}
> Expected: no WARNING in output
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456793#comment-16456793
]
Goldstein Lyor commented on MPMD-258:
-
Your point is well taken and indeed once per module is tolerable - I will wait
for 3.10 to eliminate all unsolicited logging...
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod3 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod3 ---
> [INFO] Deleting /home
[jira] [Commented] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456785#comment-16456785
]
Andreas Dangel commented on MPMD-258:
-
Yes, but you'll get the output now only once per module/pmd run. With
`-Dpmd.showPmdLog=false` PMD is logging on its own and not through maven.
With this fix, you'll still get the output, but only once, e.g.:
{noformat}
...
[INFO] --- maven-pmd-plugin:3.10.0-SNAPSHOT:pmd (default-cli) @
MPMD-258-multiple-executions-mod2 ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO] Analysis cache invalidated, rulesets changed.
[INFO] Analysis cache invalidated, execution classpath changed.
[INFO] Analysis cache updated
[INFO]
[INFO] Reactor Summary:
...{noformat}
Is this still an issue then?
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysi
[jira] [Commented] (MPMD-261) Upgrade to PMD 6.2.0
[ https://issues.apache.org/jira/browse/MPMD-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456779#comment-16456779 ] Hudson commented on MPMD-261: - Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #26 See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/26/ > Upgrade to PMD 6.2.0 > > > Key: MPMD-261 > URL: https://issues.apache.org/jira/browse/MPMD-261 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: CPD, PMD >Affects Versions: 3.9.0 >Reporter: Andreas Dangel >Assignee: Andreas Dangel >Priority: Major > Fix For: 3.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456771#comment-16456771
]
Goldstein Lyor commented on MPMD-258:
-
Using {{-pmd.showPmdLog=false}} alleviates the issue but does not eliminate it
- still getting:
{quote}
Apr 27, 2018 8:12:05 PM net.sourceforge.pmd.cache.AbstractAnalysisCache
checkValidity
INFO: Analysis cache invalidated, rulesets changed.
Apr 27, 2018 8:12:05 PM net.sourceforge.pmd.cache.AbstractAnalysisCache
checkValidity
INFO: Analysis cache invalidated, execution classpath changed.
Apr 27, 2018 8:12:24 PM net.sourceforge.pmd.cache.FileAnalysisCache persist
INFO: Analysis cache updated
{quote}
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INF
[jira] [Commented] (MPMD-255) Handle missing analysisCacheLocation file
[
https://issues.apache.org/jira/browse/MPMD-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456762#comment-16456762
]
Andreas Dangel commented on MPMD-255:
-
This will require PMD 6.3.0.
> Handle missing analysisCacheLocation file
> -
>
> Key: MPMD-255
> URL: https://issues.apache.org/jira/browse/MPMD-255
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
>Reporter: Matt Nelson
>Priority: Major
>
> When the {{analysisCacheLocation}} file is missing the error is not clear it
> is the reason for the failure. Can a more descriptive message be added? Or
> log a warning and proceed to build without the cache.
> {noformat}
> Caused by: java.io.FileNotFoundException: my-project\target\classes (The
> system cannot find the file specified)
> at java.io.FileInputStream.open0 (Native Method)
> at java.io.FileInputStream.open (FileInputStream.java:195)
> at java.io.FileInputStream. (FileInputStream.java:138)
> at java.io.FileInputStream. (FileInputStream.java:93)
> at sun.net.www.protocol.file.FileURLConnection.connect
> (FileURLConnection.java:90)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream
> (FileURLConnection.java:188)
> at java.net.URL.openStream (URL.java:1045)
> at net.sourceforge.pmd.cache.AbstractAnalysisCache.computeClassPathHash
> (AbstractAnalysisCache.java:182)
> at net.sourceforge.pmd.cache.AbstractAnalysisCache.checkValidity
> (AbstractAnalysisCache.java:113)
> at net.sourceforge.pmd.processor.AbstractPMDProcessor.processFiles
> (AbstractPMDProcessor.java:105)
> at net.sourceforge.pmd.PMD.processFiles (PMD.java:311)
> at org.apache.maven.plugins.pmd.PmdReport.processFilesWithPMD
> (PmdReport.java:503)
> at org.apache.maven.plugins.pmd.PmdReport.executePmd (PmdReport.java:432)
> at org.apache.maven.plugins.pmd.PmdReport.executePmdWithClassloader
> (PmdReport.java:331)
> at org.apache.maven.plugins.pmd.PmdReport.canGenerateReport
> (PmdReport.java:305)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPMD-260) Seeing lots of (benign) analysis cache related messages during plugin execution
[
https://issues.apache.org/jira/browse/MPMD-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-260.
---
Resolution: Duplicate
> Seeing lots of (benign) analysis cache related messages during plugin
> execution
> ---
>
> Key: MPMD-260
> URL: https://issues.apache.org/jira/browse/MPMD-260
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Goldstein Lyor
>Priority: Major
>
> The number of the messages seems to be related to the number of dependencies
> the compiled module has - i.e., the "deeper" the module the more messages are
> issued. At the very least IMO these messages should be at DEBUG level rather
> than INFO since they clutter the output.
> {noformat}
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (pmd) @ c-application-dal-object ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456745#comment-16456745
]
Hudson commented on MPMD-258:
-
Build succeeded in Jenkins: Maven TLP » maven-pmd-plugin » master #25
See https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/25/
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod3 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod3 ---
> [INFO] Deleting
[jira] [Resolved] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel resolved MPMD-258.
-
Resolution: Fixed
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod3 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod3 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod3/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod3 ---
> [INFO] Using 'UTF-8' encoding to
[jira] [Closed] (MPMD-258) PMD output multiplies with every module in multi module projects
[
https://issues.apache.org/jira/browse/MPMD-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel closed MPMD-258.
---
> PMD output multiplies with every module in multi module projects
>
>
> Key: MPMD-258
> URL: https://issues.apache.org/jira/browse/MPMD-258
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.9.0
>Reporter: Michael
>Assignee: Andreas Dangel
>Priority: Major
> Fix For: 3.10.0
>
> Attachments: pmd.zip
>
>
> I noticed in a project with serval modules that the pmd output seems to get
> multiplied with every module when invoking pmd:pmd in the parent project.
> Specifically, in my case, it seems the output gets three repetitions per
> module (normal output in first module, every line repeats 4 times in second,
> 7 times in third, and so on)
> I attached a simple demo project, which should demonstrate this problem. The
> output I get from invoking "mvn clean compile pmd:pmd" in the parent project
> follows.
> I am using maven version 3.5.0 with oracle java 1.8.0_121 and the pmd plugin
> 3.9.0, on Linux (Debian Testing)
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] hello
> [INFO] mod1
> [INFO] mod2
> [INFO] mod3
> [INFO] mod4
> [INFO] mod5
> [INFO] mod6
> [INFO] mod7
> [INFO] mod8
> [INFO] mod9
> [INFO] mod10
> [INFO]
> [INFO]
>
> [INFO] Building hello 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hello ---
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ hello ---
> [INFO]
> [INFO]
>
> [INFO] Building mod1 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod1 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod1/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod1 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod1 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod1/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod1 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod2 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod2 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod2/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod2 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ mod2 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/mst/workspace/DAP/hello/mod2/target/classes
> [INFO]
> [INFO] --- maven-pmd-plugin:3.9.0:pmd (default-cli) @ mod2 ---
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, rulesets changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache invalidated, execution classpath changed.
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO] Analysis cache updated
> [INFO]
> [INFO]
>
> [INFO] Building mod3 0.2.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mod3 ---
> [INFO] Deleting /home/mst/workspace/DAP/hello/mod3/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ mod3 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
[jira] [Created] (MWAR-415) ${maven.build.timestamp} is not working in filtered webResources
Leonid Rozenblyum created MWAR-415:
--
Summary: ${maven.build.timestamp} is not working in filtered
webResources
Key: MWAR-415
URL: https://issues.apache.org/jira/browse/MWAR-415
Project: Maven WAR Plugin
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Leonid Rozenblyum
It may be related to https://issues.apache.org/jira/browse/MRESOURCES-99
When a webResource, with filtering enabled contains property
${maven.build.timestamp}, it's not replaced by the timestamp.
The workaround is to remove definitions of webResource and configure the
resources on level (and making sure that
maven-resource-plugin version is >= 3.0.0)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MPIR-366) Drop Maven 2 support
[ https://issues.apache.org/jira/browse/MPIR-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MPIR-366. --- Resolution: Fixed Fix Version/s: 3.0 Fixed in [dc02297532a268ec3e419f9c90faca0feea632c8|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=dc02297532a268ec3e419f9c90faca0feea632c8] > Drop Maven 2 support > > > Key: MPIR-366 > URL: https://issues.apache.org/jira/browse/MPIR-366 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6399) Lift JDK minimum to JDK 8
[ https://issues.apache.org/jira/browse/MNG-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456135#comment-16456135 ] Robert Scholte commented on MNG-6399: - I agree with [~michael-o], upgrading to JDK8 should be combined with features that require it. Maybe there are some issues that can only be solved by this, but I'd like to see those blocked issues being bound to this issue. > Lift JDK minimum to JDK 8 > - > > Key: MNG-6399 > URL: https://issues.apache.org/jira/browse/MNG-6399 > Project: Maven > Issue Type: Task >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Priority: Critical > Fix For: 3.6.0 > > > I would like to lift the minimum of Maven Core to JDK 8 (I think it's time).. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
