[jira] [Updated] (MSHARED-417) Infinite loop when loading self-referencing properties
[
https://issues.apache.org/jira/browse/MSHARED-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Belingueres updated MSHARED-417:
Attachment: MSHARED-417.patch
I've attached a patch that warns that a cycle has been found. Tested it with
current trunk version of maven-assembly-plugin (3.0.0-SNAPSHOT).
Please test it.
Regards,
Gabriel
> Infinite loop when loading self-referencing properties
> --
>
> Key: MSHARED-417
> URL: https://issues.apache.org/jira/browse/MSHARED-417
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-1.3
> Environment: Maven 3.2.5. Maven-filtering-1.3.
>Reporter: Paul Milliken
> Attachments: MSHARED-417.patch, MSHARED-417.zip
>
>
> I've recently encountered a situation in which maven-resources-plugin would
> hang indefinitely when using resource filtering. I've managed to track it
> down to the loadPropertyFile and getPropertyValue methods in PropertyUtils.
> getPropertyValue appears to have some protection against a property referring
> to itself. So, the following properties file loads fine:
> {code}
> test=${test}
> test2=${test2}
> {code}
> With the value of the "test" property ending up as "$\{test\}". However, if
> you load the following properties file:
> {code}
> test=${test2}
> test2=${test2}
> {code}
> then getPropertyValue seems to get stuck in a loop attempting to resolve the
> property.
> In our case, this was encountered as a result of a misconfiguration (our
> filters.properties is being generated based on a number of sources, and
> something was configured incorrectly). Causing the Maven process to hang
> indefinitely (while using 100% of a CPU core) isn't ideal behaviour.
> I have reproduced this in isolation by directly invoking
> {{PropertyUtils.loadPropertyFile(File, null)}} with the the above data as the
> input file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ARCHETYPE-507) create-from-project fails on Windows
Matt Benson created ARCHETYPE-507:
-
Summary: create-from-project fails on Windows
Key: ARCHETYPE-507
URL: https://issues.apache.org/jira/browse/ARCHETYPE-507
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Affects Versions: 2.4
Reporter: Matt Benson
When the {{FilesetArchetypeCreator}} attempts to invoke the created project, it
runs afoul of https://issues.apache.org/jira/browse/MSHARED-413 . Solution is
to upgrade the maven-invoker dependency to v2.2; this can be done locally in
the plugin configuration as a workaround.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MDEP-519) Dependency tree with description of each artefacts
[ https://issues.apache.org/jira/browse/MDEP-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410141#comment-15410141 ] Hervé Boutemy commented on MDEP-519: I think that on console, nothing is really usable: that's where html report is a better UI > Dependency tree with description of each artefacts > -- > > Key: MDEP-519 > URL: https://issues.apache.org/jira/browse/MDEP-519 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Affects Versions: 2.10 >Reporter: Eric Reboisson > Labels: newbie > > Hello, > I would like to generate a maven dependency tree with a description of each > artefacts. > For instance, in my dependencies, due to transitive dependency antlr is in my > libs, but (even if I know what is this librairies) I would like to generate a > kind of documentation. > If I take the example of antlr artefact I would like something like this : | > | | +- antlr:antlr:jar:2.7.7:compile "A framework for constructing > recognizers, compilers, and translators from grammatical descriptions > containing Java, C#, C++, or Python actions." > > The description is coming from > central.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-5910) Using both {{exists}} and {{missing}} in the same {{file}} element should lead to an exception
[
https://issues.apache.org/jira/browse/MNG-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410134#comment-15410134
]
Hervé Boutemy commented on MNG-5910:
you used Severity.ERROR: I suppose using Severity.WARNING should do the job,
even if I could not find any example
for the algorithm, avoid new Exception!
{code:java}if ( StringUtils.isNotEmpty( file.getExists() ) )
{
path = file.getExists();
missing = false;
if ( StringUtils.isNotEmpty( file.getMissing() ) )
{
problems.add( new ModelProblemCollectorRequest(
Severity.WARNING, Version.BASE )
.setMessage( "File activation for profile " +
profile.getId() + ": missing " + file.getMissing() + " assertion ignored since
exists assertion defined too, you should remove one" )
.setLocation( file.getLocation( "missing" ) ) );
}
}
else if ( StringUtils.isNotEmpty( file.getMissing() ) )
{code}
> Using both {{exists}} and {{missing}} in the same {{file}} element should
> lead to an exception
> --
>
> Key: MNG-5910
> URL: https://issues.apache.org/jira/browse/MNG-5910
> Project: Maven
> Issue Type: Bug
> Components: core, Profiles
>Affects Versions: 3.3.3
>Reporter: Konrad Windszus
>
> Currently it is not clear from the POM reference
> (https://maven.apache.org/pom.html#Activation), that the elements {{exists}}
> and {{missing}} below {{file}} are mutually exclusive, because only
> {{exists}} is considered if it is there (see also
> https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/FileProfileActivator.java#L91).
> Please make it clearer in the POM reference that not both of them should be
> used at the same time and also throw an exception during build time if that
> is the case (in the effective POM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5910) Using both {{exists}} and {{missing}} in the same {{file}} element should lead to an exception
[
https://issues.apache.org/jira/browse/MNG-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409831#comment-15409831
]
Rajiv Jain commented on MNG-5910:
-
Do you have any examples of warnings in the Apache Maven code? What should I
log as the warning message?
Are you saying that don’t check for the file/missing values? Can you please
elaborate?
> Using both {{exists}} and {{missing}} in the same {{file}} element should
> lead to an exception
> --
>
> Key: MNG-5910
> URL: https://issues.apache.org/jira/browse/MNG-5910
> Project: Maven
> Issue Type: Bug
> Components: core, Profiles
>Affects Versions: 3.3.3
>Reporter: Konrad Windszus
>
> Currently it is not clear from the POM reference
> (https://maven.apache.org/pom.html#Activation), that the elements {{exists}}
> and {{missing}} below {{file}} are mutually exclusive, because only
> {{exists}} is considered if it is there (see also
> https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/model/profile/activation/FileProfileActivator.java#L91).
> Please make it clearer in the POM reference that not both of them should be
> used at the same time and also throw an exception during build time if that
> is the case (in the effective POM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MDEP-519) Dependency tree with description of each artefacts
[ https://issues.apache.org/jira/browse/MDEP-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409823#comment-15409823 ] Rajiv Jain commented on MDEP-519: - I will take a look and get back to you. I think, as Robert mentions it might be better to display the first line only. What do you think? > Dependency tree with description of each artefacts > -- > > Key: MDEP-519 > URL: https://issues.apache.org/jira/browse/MDEP-519 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Affects Versions: 2.10 >Reporter: Eric Reboisson > Labels: newbie > > Hello, > I would like to generate a maven dependency tree with a description of each > artefacts. > For instance, in my dependencies, due to transitive dependency antlr is in my > libs, but (even if I know what is this librairies) I would like to generate a > kind of documentation. > If I take the example of antlr artefact I would like something like this : | > | | +- antlr:antlr:jar:2.7.7:compile "A framework for constructing > recognizers, compilers, and translators from grammatical descriptions > containing Java, C#, C++, or Python actions." > > The description is coming from > central.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEP-519) Dependency tree with description of each artefacts
[ https://issues.apache.org/jira/browse/MDEP-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409821#comment-15409821 ] Rajiv Jain commented on MDEP-519: - I will try that and get back to you. > Dependency tree with description of each artefacts > -- > > Key: MDEP-519 > URL: https://issues.apache.org/jira/browse/MDEP-519 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Affects Versions: 2.10 >Reporter: Eric Reboisson > Labels: newbie > > Hello, > I would like to generate a maven dependency tree with a description of each > artefacts. > For instance, in my dependencies, due to transitive dependency antlr is in my > libs, but (even if I know what is this librairies) I would like to generate a > kind of documentation. > If I take the example of antlr artefact I would like something like this : | > | | +- antlr:antlr:jar:2.7.7:compile "A framework for constructing > recognizers, compilers, and translators from grammatical descriptions > containing Java, C#, C++, or Python actions." > > The description is coming from > central.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MDEP-519) Dependency tree with description of each artefacts
[ https://issues.apache.org/jira/browse/MDEP-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409820#comment-15409820 ] Rajiv Jain commented on MDEP-519: - Hi Robert By parameters do you mean command line options? In addition, what do you mean by "and to break it after x characters"? Can you please elborate? > Dependency tree with description of each artefacts > -- > > Key: MDEP-519 > URL: https://issues.apache.org/jira/browse/MDEP-519 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree >Affects Versions: 2.10 >Reporter: Eric Reboisson > Labels: newbie > > Hello, > I would like to generate a maven dependency tree with a description of each > artefacts. > For instance, in my dependencies, due to transitive dependency antlr is in my > libs, but (even if I know what is this librairies) I would like to generate a > kind of documentation. > If I take the example of antlr artefact I would like something like this : | > | | +- antlr:antlr:jar:2.7.7:compile "A framework for constructing > recognizers, compilers, and translators from grammatical descriptions > containing Java, C#, C++, or Python actions." > > The description is coming from > central.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPMD-225) Create report even if no warnings have been found
[ https://issues.apache.org/jira/browse/MPMD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409784#comment-15409784 ] Johannes Wienke commented on MPMD-225: -- This looks good. A switched default would make more sense to me. Otherwise, people might question whether checks have worked at all. > Create report even if no warnings have been found > -- > > Key: MPMD-225 > URL: https://issues.apache.org/jira/browse/MPMD-225 > Project: Maven PMD Plugin > Issue Type: Wish >Reporter: Johannes Wienke > > Right now, no report for the site plugin is generated if no violations have > been found. This is sometimes quite confusing as this state cannot be > distinguished from "the plugin didn't work at all". Checkstyle for example > just generates an empty report in these cases, which is what I would also > like for the pmd plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHARED-417) Infinite loop when loading self-referencing properties
[
https://issues.apache.org/jira/browse/MSHARED-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409492#comment-15409492
]
Gabriel Belingueres commented on MSHARED-417:
-
I could work on a patch to detect this kind of cycles on properties files.
Should the plugin throw an exception or continue with a logged warning?
> Infinite loop when loading self-referencing properties
> --
>
> Key: MSHARED-417
> URL: https://issues.apache.org/jira/browse/MSHARED-417
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
>Affects Versions: maven-filtering-1.3
> Environment: Maven 3.2.5. Maven-filtering-1.3.
>Reporter: Paul Milliken
> Attachments: MSHARED-417.zip
>
>
> I've recently encountered a situation in which maven-resources-plugin would
> hang indefinitely when using resource filtering. I've managed to track it
> down to the loadPropertyFile and getPropertyValue methods in PropertyUtils.
> getPropertyValue appears to have some protection against a property referring
> to itself. So, the following properties file loads fine:
> {code}
> test=${test}
> test2=${test2}
> {code}
> With the value of the "test" property ending up as "$\{test\}". However, if
> you load the following properties file:
> {code}
> test=${test2}
> test2=${test2}
> {code}
> then getPropertyValue seems to get stuck in a loop attempting to resolve the
> property.
> In our case, this was encountered as a result of a misconfiguration (our
> filters.properties is being generated based on a number of sources, and
> something was configured incorrectly). Causing the Maven process to hang
> indefinitely (while using 100% of a CPU core) isn't ideal behaviour.
> I have reproduced this in isolation by directly invoking
> {{PropertyUtils.loadPropertyFile(File, null)}} with the the above data as the
> input file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://issues.apache.org/jira/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409476#comment-15409476 ] Hudson commented on MPMD-196: - SUCCESS: Integrated in maven-plugins #7079 (See [https://builds.apache.org/job/maven-plugins/7079/]) [MPMD-196] Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) (adangel: [http://svn.apache.org/viewvc/?view=rev=1755320]) * maven-pmd-plugin/src/test/java/org/apache/maven/plugin/pmd/AbstractPmdReportTest.java * maven-pmd-plugin/src/test/java/org/apache/maven/plugin/pmd/CpdReportTest.java * maven-pmd-plugin/src/test/java/org/apache/maven/plugin/pmd/PmdReportTest.java > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://issues.apache.org/jira/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Andreas Dangel >Priority: Minor > Fix For: 3.7 > > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHANGES-374) Allow OAuth authentication in Jira
Angel Cervera Claudio created MCHANGES-374: -- Summary: Allow OAuth authentication in Jira Key: MCHANGES-374 URL: https://issues.apache.org/jira/browse/MCHANGES-374 Project: Maven Changes Plugin Issue Type: New Feature Components: jira Reporter: Angel Cervera Claudio The only way to access to Jira is using User/Password. Usually, because security issues, is not an option in big companies so it is necessary to use other authentication systems, like tokens or OAuth. Jira implements OAuth, so this would be the best option to avoid hard coded passwords. Documentation: https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-oauth-authentication -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://issues.apache.org/jira/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409447#comment-15409447 ] Andreas Dangel commented on MPMD-196: - Fixed in [r1755320|http://svn.apache.org/viewvc?view=revision=1755320] > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://issues.apache.org/jira/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Andreas Dangel >Priority: Minor > Fix For: 3.7 > > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://issues.apache.org/jira/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel resolved MPMD-196. - Resolution: Fixed Fix Version/s: 3.7 > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://issues.apache.org/jira/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Andreas Dangel >Priority: Minor > Fix For: 3.7 > > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MPMD-213) The language parameter should not be read-only
[
https://issues.apache.org/jira/browse/MPMD-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Dangel reassigned MPMD-213:
---
Assignee: Andreas Dangel
> The language parameter should not be read-only
> --
>
> Key: MPMD-213
> URL: https://issues.apache.org/jira/browse/MPMD-213
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Dennis Lundberg
>Assignee: Andreas Dangel
>
> The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
> read-only. It should be possible to change it in case you have an artifact
> with a type of sources for which there is no artifact handler, i.e.
> javascript.
> The IT PMD-205-pmd-js-check shows this. It currently fails under Maven 2.2.1,
> but works under Maven 3 due to MNG-5001.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPMD-213) The language parameter should not be read-only
[
https://issues.apache.org/jira/browse/MPMD-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409442#comment-15409442
]
Andreas Dangel commented on MPMD-213:
-
Since [r1682450|http://svn.apache.org/viewvc?view=revision=1682450]
the language parameter isn't used at all. Instead, if the output file from the
`pmd` or `cpd` goal exists, the violations are examined.
There is a language parameter, but this one is for the `pmd`/`cpd` goals - and
this one is configurable.
[~denn...@apache.org] I believe, the language parameter in
`AbstractPmdViolationCheckMojo` can be removed completely. What do you think?
> The language parameter should not be read-only
> --
>
> Key: MPMD-213
> URL: https://issues.apache.org/jira/browse/MPMD-213
> Project: Maven PMD Plugin
> Issue Type: Bug
>Reporter: Dennis Lundberg
>
> The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
> read-only. It should be possible to change it in case you have an artifact
> with a type of sources for which there is no artifact handler, i.e.
> javascript.
> The IT PMD-205-pmd-js-check shows this. It currently fails under Maven 2.2.1,
> but works under Maven 3 due to MNG-5001.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPMD-225) Create report even if no warnings have been found
[ https://issues.apache.org/jira/browse/MPMD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409394#comment-15409394 ] Andreas Dangel commented on MPMD-225: - There is already a parameter: `skipEmptyReport` > skipEmptyReport: > Skip the PMD/CPD report generation if there are no violations or duplications > found. Defaults to true. > >Type: boolean >Since: 3.1 >Required: No >Default: true (from http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skipEmptyReport) [~languitar] Would this parameter solve your issue? Would it be better to have the default for this parameter to create the report, rather than skip the empty report? > Create report even if no warnings have been found > -- > > Key: MPMD-225 > URL: https://issues.apache.org/jira/browse/MPMD-225 > Project: Maven PMD Plugin > Issue Type: Wish >Reporter: Johannes Wienke > > Right now, no report for the site plugin is generated if no violations have > been found. This is sometimes quite confusing as this state cannot be > distinguished from "the plugin didn't work at all". Checkstyle for example > just generates an empty report in these cases, which is what I would also > like for the pmd plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MPMD-226) Require Java 7
Andreas Dangel created MPMD-226: --- Summary: Require Java 7 Key: MPMD-226 URL: https://issues.apache.org/jira/browse/MPMD-226 Project: Maven PMD Plugin Issue Type: Task Reporter: Andreas Dangel Assignee: Andreas Dangel Fix For: 3.7 PMD 5.4 and later requires Java 7, so we need to adjust the requirements in this plugin to reflect that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MPMD-196) Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT)
[ https://issues.apache.org/jira/browse/MPMD-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel reassigned MPMD-196: --- Assignee: Andreas Dangel > Do not rely in tests on toLowerCase but on toLowerCase(Locale.ROOT) > --- > > Key: MPMD-196 > URL: https://issues.apache.org/jira/browse/MPMD-196 > Project: Maven PMD Plugin > Issue Type: Task > Components: CPD, PMD >Affects Versions: 3.3 >Reporter: Michael Osipov >Assignee: Andreas Dangel >Priority: Minor > > See detailed explanation here: > http://blog.thetaphi.de/2012/07/default-locales-default-charsets-and.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPMD-220) Upgrade to PMD 5.5.1 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-220: Fix Version/s: 3.7 > Upgrade to PMD 5.5.1 (requires Java 7) > -- > > Key: MPMD-220 > URL: https://issues.apache.org/jira/browse/MPMD-220 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Mathieu BONIFACE >Assignee: Andreas Dangel > Fix For: 3.7 > > > As 5.4.1 is out and provide some interesting improvements and bugfixes, it > would be great for us to upgrade the maven plugin with this new version of > PMD. > Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi > Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) > *Update*: Latest version of PMD is currently 5.5.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MPMD-224) Update PMD to 5.4.2 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel closed MPMD-224. --- Resolution: Duplicate > Update PMD to 5.4.2 (requires Java 7) > - > > Key: MPMD-224 > URL: https://issues.apache.org/jira/browse/MPMD-224 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.6 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) > Maven home: E:\Java\apache-maven-3.3.9 > Java version: 1.8.0_91, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.8.0_91\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >Reporter: Gary Gregory >Assignee: Andreas Dangel > > Update PMD to 5.4.2 (requires Java 7) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPMD-220) Upgrade to PMD 5.5.1 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-220: Issue Type: Improvement (was: Task) > Upgrade to PMD 5.5.1 (requires Java 7) > -- > > Key: MPMD-220 > URL: https://issues.apache.org/jira/browse/MPMD-220 > Project: Maven PMD Plugin > Issue Type: Improvement >Reporter: Mathieu BONIFACE >Assignee: Andreas Dangel > > As 5.4.1 is out and provide some interesting improvements and bugfixes, it > would be great for us to upgrade the maven plugin with this new version of > PMD. > Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi > Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) > *Update*: Latest version of PMD is currently 5.5.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPMD-220) Upgrade to PMD 5.5.1 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-220: Description: As 5.4.1 is out and provide some interesting improvements and bugfixes, it would be great for us to upgrade the maven plugin with this new version of PMD. Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) *Update*: Latest version of PMD is currently 5.5.1. was: As 5.4.1 is out and provide some interesting improvements and bugfixes, it would be great for us to upgrade the maven plugin with this new version of PMD. Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) > Upgrade to PMD 5.5.1 (requires Java 7) > -- > > Key: MPMD-220 > URL: https://issues.apache.org/jira/browse/MPMD-220 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Mathieu BONIFACE >Assignee: Andreas Dangel > > As 5.4.1 is out and provide some interesting improvements and bugfixes, it > would be great for us to upgrade the maven plugin with this new version of > PMD. > Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi > Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) > *Update*: Latest version of PMD is currently 5.5.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MPMD-220) Upgrade to PMD 5.5.1 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel updated MPMD-220: Summary: Upgrade to PMD 5.5.1 (requires Java 7) (was: Upgrade to PMD 5.4.1) > Upgrade to PMD 5.5.1 (requires Java 7) > -- > > Key: MPMD-220 > URL: https://issues.apache.org/jira/browse/MPMD-220 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Mathieu BONIFACE >Assignee: Andreas Dangel > > As 5.4.1 is out and provide some interesting improvements and bugfixes, it > would be great for us to upgrade the maven plugin with this new version of > PMD. > Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi > Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MPMD-220) Upgrade to PMD 5.4.1
[ https://issues.apache.org/jira/browse/MPMD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel reassigned MPMD-220: --- Assignee: Andreas Dangel > Upgrade to PMD 5.4.1 > > > Key: MPMD-220 > URL: https://issues.apache.org/jira/browse/MPMD-220 > Project: Maven PMD Plugin > Issue Type: Task >Reporter: Mathieu BONIFACE >Assignee: Andreas Dangel > > As 5.4.1 is out and provide some interesting improvements and bugfixes, it > would be great for us to upgrade the maven plugin with this new version of > PMD. > Another important change is pmd > 5.4.0 requires Java >= 1.7.0 (see APi > Changes [here|http://sourceforge.net/projects/pmd/files/pmd/5.4.0/]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCHANGES-373) It is not possible to use "filter" parameter
[ https://issues.apache.org/jira/browse/MCHANGES-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angel Cervera Claudio updated MCHANGES-373: --- Priority: Critical (was: Major) > It is not possible to use "filter" parameter > > > Key: MCHANGES-373 > URL: https://issues.apache.org/jira/browse/MCHANGES-373 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.12 >Reporter: Angel Cervera Claudio >Priority: Critical > > "filter" parameter is always ignored. > The reason is that this parameter is not set: > RestJiraDownloader.java line 145: > new JqlQueryBuilder( log ).urlEncode( false ).project( jiraProject > ).fixVersion( getFixFor() ).fixVersionIds( resolvedFixVersionIds ).statusIds( > resolvedStatusIds ).priorityIds( resolvedPriorityIds ).resolutionIds( > resolvedResolutionIds ).components( resolvedComponentIds ).typeIds( > resolvedTypeIds ).sortColumnNames( sortColumnNames ).build(); > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHANGES-373) It is not possible to use "filter" parameter
Angel Cervera Claudio created MCHANGES-373: -- Summary: It is not possible to use "filter" parameter Key: MCHANGES-373 URL: https://issues.apache.org/jira/browse/MCHANGES-373 Project: Maven Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.12 Reporter: Angel Cervera Claudio "filter" parameter is always ignored. The reason is that this parameter is not set: RestJiraDownloader.java line 145: new JqlQueryBuilder( log ).urlEncode( false ).project( jiraProject ).fixVersion( getFixFor() ).fixVersionIds( resolvedFixVersionIds ).statusIds( resolvedStatusIds ).priorityIds( resolvedPriorityIds ).resolutionIds( resolvedResolutionIds ).components( resolvedComponentIds ).typeIds( resolvedTypeIds ).sortColumnNames( sortColumnNames ).build(); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MPMD-224) Update PMD to 5.4.2 (requires Java 7)
[ https://issues.apache.org/jira/browse/MPMD-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Dangel reassigned MPMD-224: --- Assignee: Andreas Dangel > Update PMD to 5.4.2 (requires Java 7) > - > > Key: MPMD-224 > URL: https://issues.apache.org/jira/browse/MPMD-224 > Project: Maven PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 3.6 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) > Maven home: E:\Java\apache-maven-3.3.9 > Java version: 1.8.0_91, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.8.0_91\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >Reporter: Gary Gregory >Assignee: Andreas Dangel > > Update PMD to 5.4.2 (requires Java 7) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHADE-234) support java 9 modules (jigsaw)
[ https://issues.apache.org/jira/browse/MSHADE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409038#comment-15409038 ] Robert Scholte commented on MSHADE-234: --- Concrete example: Logger.jar has 2 packages, com.foo.logger and com.foo.logger.internal, only the first one is exported. App.jar uses Logger.jar and is only allowed to use the classes of com.foo.logger, not com.foo.logger.internal. If we would shade it now, all classes of App will also get access to com.foo.logger.internal, since they are in the same jar. Okay, maybe not at compile time, but definitely at runtime. Hence, there's a request to be able to bundle everything in 1 jar, but to still respect all module statements. > support java 9 modules (jigsaw) > --- > > Key: MSHADE-234 > URL: https://issues.apache.org/jira/browse/MSHADE-234 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: sam rash > > Java 9 will begin in including the module-info.class file which has the > packages that are exported. It would be great if the shade plugin can detect > the new format, and for any packages that are moved, it updates the module > exports accordingly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
